listhelper-moderate
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Qemu-devel post from address@hidden requires approval


From: qemu-devel-owner
Subject: Qemu-devel post from address@hidden requires approval
Date: Fri, 29 Jun 2007 09:27:29 -0400

As list administrator, your authorization is requested for the
following mailing list posting:

    List:    address@hidden
    From:    address@hidden
    Subject: qemu-system-x86_64 bugs
    Reason:  Post by non-member to a members-only list

At your convenience, visit:

    http://lists.nongnu.org/mailman/admindb/qemu-devel
        
to approve or deny the request.
--- Begin Message --- Subject: qemu-system-x86_64 bugs Date: Fri, 29 Jun 2007 16:27:50 +0300 User-agent: Mozilla-Thunderbird 2.0.0.4 (X11/20070621)
Hello,

I have qemu-0.9.0 (installed via deb package) on debian-amd64 unstable
on a turion64 hp notebook.

I have detected the following bugs when using the command
"qemu-system-x86_64 -hda /dev/hda":

1) I use grub-0.97 to boot my system. Qemu (meaning the above command)
always boots the same image although it may have changed between two
uses of qemu. For example, if i use qemu and grub has the following
options at boot time

Linux
MyOS1
MyOS2

i choose MyOS1 the first time. I close qemu, modify and rebuild MyOS1,
then call qemu again. When i choose MyOS1, qemu will run the os image it
run the first time and not the new image. This will repeat until i
reboot my system.

2) When i use the monitor, qemu refuses to print 64-bit registers rax,
rbx, rsp, etc. The command "info registers" does not show any of the
above registers. The command "p $rax" produces the message "unknown
register". In addition, it doesn't print either the 32-bit registers
eax. ebx, esp, etc when using the command "info registers". However it
does print the previously mentioned regs when the command "p $e**" is
used. Regs e** seem to represent regs r** because the former can
"contain" 64-bit values. In one of my test kernels, i did a "movq
$0xffffffffff, %rdi" and from within qemu "p $edi" produced 0xffffffffff.

Constantine


PS I'm not registered to this list so please cc me to your replies.




--- End Message ---
--- Begin Message --- Subject: confirm 303cb297a4280004d1f317c16e9e80aacd448d28
If you reply to this message, keeping the Subject: header intact,
Mailman will discard the held message.  Do this if the message is
spam.  If you reply to this message and include an Approved: header
with the list password in it, the message will be approved for posting
to the list.  The Approved: header can also appear in the first line
of the body of the reply.

--- End Message ---

reply via email to

[Prev in Thread] Current Thread [Next in Thread]