Minor update, I found that I made a mistake with the value in STAR. I
loaded 0x18 into the top 16 bits, so the bug is not that SS is 0x20
(which I thought to be wrong but was my own mistake). Why does it set
CS=0x2b from that value & run?
--
sysret sets invalid ss
https://bugs.launchpad.net/bugs/
On Fri, Sep 3, 2010 at 1:11 PM, Mark Cave-Ayland
wrote:
> Artyom Tarasenko wrote:
>
>> Does any gdb version work with current qemu-system-sparc64 ?
>>
>> I tried 7.1 and 6.8 with --target=sparc64-linux and --target=sparc64
>> And result seems to be pretty much the same:
>>
>> GNU gdb 6.8
>> Copyri
On Thu, Aug 26, 2010 at 09:44:32AM -0700, Venkateswararao Jujjuri (JV) wrote:
> Bruno Cesar Ribas wrote:
> > Hi,
> >
> [snip]
> This quick test is with QEMU patches that are on mailing lists but not merged
> into mainline.
> Being said that, I don't think they really affect this.
is there any wor
Hi,
I'm trying to test 2 GB (and eventually larger) BARs with ivshmem and
I get an error in the guest that it is able to find a mem resource for
a BAR larger than 1GB. I'm using 64-bit BARs.
when running with 6GB of RAM and a 1GB BAR for ivshmem, it finds a
resource (and searches beyond 32-bit v
Public bug reported:
I'm developing an OS. I use only sysret to enter user space. When an
interrupt occurred, it would GPF on iretq'ing from it. On investigating,
the cs on the stack is 0x2b (valid and correct). The ss on the stack is
0x20, which has a rpl of 0 which is incorrect. iretq checks tha
In case anyone is interested, I've pushed an updated version for the static
instrumentation:
https://projects.gso.ac.upc.edu/projects/qemu-instrument/
git clone https://code.gso.ac.upc.edu/git/qemu-instrument/
Changes:
* Instruction-based backdoors produce an immediate exit to th
Am 02.09.2010 15:11, schrieb Bernhard Kohl:
> I use a legacy OS which depends on some optional SCSI commands.
> In fact this implementation does nothing special, but provides minimum
> support for the following commands:
>
> REZERO UNIT
> WRITE AND VERIFY(10)
> WRITE AND VERIFY(12)
> WRITE AND VER
On Fri, Sep 3, 2010 at 4:06 PM, Kevin Wolf wrote:
> Am 03.09.2010 13:55, schrieb Stefan Hajnoczi:
>> The blkverify block driver makes investigating image format data
>> corruption much easier. A raw image initialized with the same contents
>> as the test image (e.g. qcow2 file) must be provided.
Am 03.09.2010 13:55, schrieb Stefan Hajnoczi:
> The blkverify block driver makes investigating image format data
> corruption much easier. A raw image initialized with the same contents
> as the test image (e.g. qcow2 file) must be provided. The raw image
> mirrors read/write operations and is us
Am 03.09.2010 14:57, schrieb Jonathan A. Kollasch:
> Fill in word 64 of IDENTIFY data to indicate support for PIO modes 3 and 4.
> This allows NetBSD guests to use UltraDMA modes instead of just PIO mode 0.
>
> Signed-off-by: Jonathan A. Kollasch
Thanks, applied to the block branch.
Kevin
On Fri, Sep 3, 2010 at 2:57 AM, Vasiliy G Tolstov wrote:
> Hello. Can somebody provide minimal example code that using
> virtio-serial to communicate with guest os? (work on guest side and
> hypervisor side)
Hi Vasiliy,
There are basic examples here:
http://fedoraproject.org/wiki/Features/Virti
Alex Williamson wrote:
> Incorporated feedback. txburst= and txtimer= are now "x-" prefixed
> developer options. I added a tx= option, because I do want there to
> be a supported way to switch between TX strategies. This also drops
> the magic value of txtimer= 1 or 0 (setting default timeout o
Fill in word 64 of IDENTIFY data to indicate support for PIO modes 3 and 4.
This allows NetBSD guests to use UltraDMA modes instead of just PIO mode 0.
Signed-off-by: Jonathan A. Kollasch
---
hw/ide/core.c |4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/hw/ide/core.c
Am 03.09.2010 01:38, schrieb Jonathan A. Kollasch:
> Fill in word 64 of IDENTIFY data to indicate support for PIO modes 3 and 4.
> This allows NetBSD guests to use UltraDMA modes instead of just PIO mode 0.
The Signed-off-by line is missing.
> ---
> hw/ide/core.c |5 +++--
> 1 files changed,
The blkverify block driver makes investigating image format data
corruption much easier. A raw image initialized with the same contents
as the test image (e.g. qcow2 file) must be provided. The raw image
mirrors read/write operations and is used to verify that data read from
the test image is cor
On Thu, Aug 26, 2010 at 05:15:35PM +0200, Arnd Bergmann wrote:
> On Wednesday 25 August 2010, Hollis Blanchard wrote:
> > > We only recently fixed the kernel to have this warning in types.h, which
> > > triggers more often than kernel.h, where it used to be before. In 2.6.35
> > > and before, you c
Hello. Can somebody provide minimal example code that using
virtio-serial to communicate with guest os? (work on guest side and
hypervisor side)
--
Vasiliy G Tolstov
Selfip.Ru
Artyom Tarasenko wrote:
Does any gdb version work with current qemu-system-sparc64 ?
I tried 7.1 and 6.8 with --target=sparc64-linux and --target=sparc64
And result seems to be pretty much the same:
GNU gdb 6.8
Copyright (C) 2008 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3
Am 27.07.2010 20:25, schrieb Anthony Liguori:
> On 07/27/2010 12:43 PM, Anthony PERARD wrote:
>> Anthony Liguori wrote:
>>> On 07/27/2010 12:01 PM, Anthony PERARD wrote:
Anthony Liguori wrote:
> CVE-2008-2004 described a vulnerability in QEMU whereas a malicious
> user could
> tri
19 matches
Mail list logo
