All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Tokarev <mjt@tls.msk.ru>
To: KVM list <kvm@vger.kernel.org>
Subject: winXP "Standard PC" HAL and qemu-kvm >= 0.15
Date: Mon, 05 Dec 2011 13:21:10 +0400	[thread overview]
Message-ID: <4EDC8D06.20308@msgid.tls.msk.ru> (raw)

As it turned out, a windowsXP machine does not work in
qemu-kvm >= 0.15 (it loses network and USB entirely)
if it is using "Standard PC" HAL.  In 0.14 it worked
fine, but not in 0.14 (I haven't tried any in-between
versions yet).

There are several HAL types available in winXP: these
are "Uniprocessor PC with MPS" (or Multiprocessor),
also two ACPI types, and "Standard PC".  All the other
HAL types appears to work fine, but not "Standard PC".

I haven't debugged further yet, -- because it were
not easy to find out what was causing the regression
and how to reproduce it, and also because I don't think
it is the right HAL for qemu-kvm guest anyway.

So, if anybody have some thoughts about this issue,
and especially if you know a way to switch winXP HAL
type to some ACPI variant without reinstalling, please
speak up.. ;)

Debian bugreport for a reference: http://bugs.debian.org/647312

Reproducer: install a winXP guest on kvm with -no-acpi so
it chooses an "Uniprocessor with MPS" HAL.  Switch it to
"Standard PC" in device manager, reboot -- in 0.15+ it does
not work anymore, while in 0.14 it continues to work fine.

Thank you!

/mjt

             reply	other threads:[~2011-12-05  9:21 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-05  9:21 Michael Tokarev [this message]
2011-12-05 13:28 ` winXP "Standard PC" HAL and qemu-kvm >= 0.15 Avi Kivity
2011-12-05 20:19   ` Michael Tokarev
2011-12-06 10:32     ` Avi Kivity
2011-12-06 11:02       ` Michael Tokarev
2011-12-06 12:27         ` Michael S. Tsirkin
2011-12-06 12:27           ` [Qemu-devel] " Michael S. Tsirkin
2011-12-06 14:45           ` Michael Tokarev
2011-12-06 14:45             ` [Qemu-devel] " Michael Tokarev
2011-12-06 16:29             ` Michael Tokarev
2011-12-06 16:29               ` Michael Tokarev
2011-12-06 16:38               ` Jan Kiszka
2011-12-06 16:38                 ` [Qemu-devel] " Jan Kiszka
2011-12-06 16:57                 ` Michael Tokarev
2011-12-06 16:57                   ` [Qemu-devel] " Michael Tokarev
2011-12-06 17:45                   ` Jan Kiszka
2011-12-06 17:45                     ` [Qemu-devel] " Jan Kiszka
2011-12-06 18:13                   ` Michael Tokarev
2011-12-06 18:13                     ` [Qemu-devel] " Michael Tokarev
2011-12-06 18:21                     ` Jan Kiszka
2011-12-06 18:21                       ` [Qemu-devel] " Jan Kiszka
2011-12-06 18:45                       ` Michael Tokarev
2011-12-06 18:45                         ` [Qemu-devel] " Michael Tokarev
2011-12-06 19:38                         ` Michael Tokarev
2011-12-06 19:38                           ` [Qemu-devel] " Michael Tokarev
2011-12-06 20:58                           ` Jan Kiszka
2011-12-06 20:58                             ` [Qemu-devel] " Jan Kiszka
2011-12-06 21:12                             ` Jan Kiszka
2011-12-06 21:12                               ` [Qemu-devel] " Jan Kiszka
2011-12-07  7:11                               ` Michael Tokarev
2011-12-07  9:02                       ` Kevin Wolf
2011-12-07  9:02                         ` [Qemu-devel] " Kevin Wolf
2011-12-07  9:31                         ` Michael Tokarev
2011-12-07  9:31                           ` Michael Tokarev

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=4EDC8D06.20308@msgid.tls.msk.ru \
    --to=mjt@tls.msk.ru \
    --cc=kvm@vger.kernel.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.