All of lore.kernel.org
 help / color / mirror / Atom feed
From: Constantine Kousoulos <wuwei@freemail.gr>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] qemu-system-x86_64 bugs
Date: Fri, 29 Jun 2007 16:27:50 +0300	[thread overview]
Message-ID: <468508D6.8060902@freemail.gr> (raw)

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.

                 reply	other threads:[~2007-06-29 13:27 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=468508D6.8060902@freemail.gr \
    --to=wuwei@freemail.gr \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.