On 08/02/2013 09:04 AM, Hu Tao wrote:
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. 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.
Reported-by: Marcel Apfelbaum <marce...@redhat.com>
Signed-off-by: Hu Tao <hu...@cn.fujitsu.com>
NACK,
this is premature. It is fundamentally a firmware problem.
We have time to apply an even smaller patch that doesn't set has_pvpanic
to true, and delay the whole feature to 1.7, if we do not fix the
firmware in the next two weeks.
Paolo
