On 01/07/2010 11:55 AM, Mark Cave-Ayland wrote:
Avi Kivity wrote:
I think the issue is probably similar to that explained in the
article above; with a new processor reported to the guest, the
internal processor driver tries to upload some kind of microcode to
the new device which fails and causes the guest to fall over. Can we
teach KVM to silently discard these kinds of updates?
Can you try loading kvm.ko with the ignore_msrs module parameter set?
Hi Avi,
I've just done a quick test re-enabling processor.sys on my WinXP
guest and then did the following:
virsh stop winxp
rmmod kvm_intel
rmmod kvm
modprobe kvm ignore_msrs=1
modprobe kvm_intel
virsh start winxp
Unfortunately it still crashes with the same
"DRIVER_UNLOADED_WITHOUT_CANCELING_PENDING_OPERATIONS" BSOD :(
Well, don't do that then. Is there any specific functionality in
processor.sys that you're missing?
--
Do not meddle in the internals of kernels, for they are subtle and quick to panic.
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
