[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Qemu-devel] pvpanic device should not be automatically included as an i
From: |
Marcel Apfelbaum |
Subject: |
[Qemu-devel] pvpanic device should not be automatically included as an internal device |
Date: |
Thu, 01 Aug 2013 16:08:57 +0300 |
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.
Now what will happen on a cluster with hundreds of such VMs? If that cluster
has a health
monitoring service it may show all the VMs in a "not healthy" state.
My point is that a device that requires a driver that is not "inbox", should not
be present by default.
One possible solution is to add it manually with -device from command line.
Any thoughts?
Marcel
- [Qemu-devel] pvpanic device should not be automatically included as an internal device,
Marcel Apfelbaum <=
- Re: [Qemu-devel] pvpanic device should not be automatically included as an internal device, Gerd Hoffmann, 2013/08/01
- Re: [Qemu-devel] pvpanic device should not be automatically included as an internal device, Eric Blake, 2013/08/01
- Re: [Qemu-devel] pvpanic device should not be automatically included as an internal device, Paolo Bonzini, 2013/08/01
- Re: [Qemu-devel] pvpanic device should not be automatically included as an internal device, Eric Blake, 2013/08/01
- Re: [Qemu-devel] pvpanic device should not be automatically included as an internal device, Paolo Bonzini, 2013/08/02
- Re: [Qemu-devel] pvpanic device should not be automatically included as an internal device, Daniel P. Berrange, 2013/08/02
Re: [Qemu-devel] pvpanic device should not be automatically included as an internal device, Michael S. Tsirkin, 2013/08/01