From: Gerd Hoffmann <kraxel@redhat.com>
To: Marcel Apfelbaum <marcel.a@redhat.com>
Cc: Hu Tao <hutao@cn.fujitsu.com>,
Anthony Liguori <aliguori@us.ibm.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
qemu-devel@nongnu.org, Markus Armbruster <armbru@redhat.com>
Subject: Re: [Qemu-devel] pvpanic device should not be automatically included as an internal device
Date: Thu, 01 Aug 2013 16:18:28 +0200 [thread overview]
Message-ID: <51FA6E34.5000404@redhat.com> (raw)
In-Reply-To: <1375362537.4891.28.camel@localhost.localdomain>
On 08/01/13 15:08, Marcel Apfelbaum wrote:
> Hi,
>
> The problem with pvpanic being an internal device is that VMs running
> operating systems without a driver for this device will have problems
> when qemu will be upgraded (from qemu without this pvpanic).
>
> The outcome may be, for example: in Windows(let's say XP) the Device manager
> will open a "new device" wizard and the device will appear as an unrecognized device.
Only happens when also changing the machine type on upgrade as it is
turned off on old machine types.
But, yes, pvpanic will show up as "Unknown device" without driver and
with the funky yellow exclamation mark in device manager in windows
guests. Newer windows versions don't kick the "new device" wizard. But
still I have my doubts that it is a good idea to add it unconditionally ...
cheers,
Gerd
next prev parent reply other threads:[~2013-08-01 15:56 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-01 13:08 [Qemu-devel] pvpanic device should not be automatically included as an internal device Marcel Apfelbaum
2013-08-01 13:32 ` Michael S. Tsirkin
2013-08-01 16:39 ` Marcel Apfelbaum
2013-08-01 14:18 ` Gerd Hoffmann [this message]
2013-08-01 16:26 ` Eric Blake
2013-08-01 16:31 ` Michael S. Tsirkin
2013-08-01 16:41 ` Marcel Apfelbaum
2013-08-01 22:23 ` Paolo Bonzini
2013-08-01 22:42 ` Eric Blake
2013-08-02 8:31 ` Paolo Bonzini
2013-08-02 9:24 ` Daniel P. Berrange
2013-08-02 7:04 ` [Qemu-devel] [PATCH for-1.6 1/2] don't create pvpanic device by default Hu Tao
2013-08-02 8:27 ` Paolo Bonzini
2013-08-11 10:33 ` Michael S. Tsirkin
2013-08-11 14:45 ` Andreas Färber
2013-08-11 15:12 ` Michael S. Tsirkin
2013-08-11 15:16 ` Marcel Apfelbaum
2013-08-02 7:04 ` [Qemu-devel] [PATCH for-1.6 2/2] pvpanic: make pvpanic known to user Hu Tao
2013-08-02 12:20 ` Andreas Färber
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=51FA6E34.5000404@redhat.com \
--to=kraxel@redhat.com \
--cc=aliguori@us.ibm.com \
--cc=armbru@redhat.com \
--cc=hutao@cn.fujitsu.com \
--cc=marcel.a@redhat.com \
--cc=mst@redhat.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).