Re: WinXP virtual crashes on 0.12.1.2 but not 0.12.1.1

[Mark Cave-Ayland <mark.cave-ayland@siriusit.co.uk>]

Avi Kivity wrote:

>> 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?

No, not at all. My only concern was that the VM had been running 
absolutely fine under older KVM and VirtualBox until the upgrade from 
0.12.1.1 to 0.12.1.2 which made me think there had been a regression 
somewhere along the line.

I appreciate from tracking both qemu and kvm mailing lists that there is 
currently a lot of rapid development occuring across both QEMU and KVM, 
and hence sometimes things can break. It would be interesting to find 
out exactly *why* this doesn't work in KVM and so I can provide 
debugging assistance if you can point me in the right direction.

At the moment, I'm just happy that I can run the VM under KVM even with 
the processor.sys driver disabled. At least by bringing up the problem 
and solution on this mailing list thread then the solution is documented 
for other people who find themselves in the same situation.


ATB,

Mark.

-- 
Mark Cave-Ayland - Senior Technical Architect
PostgreSQL - PostGIS
Sirius Corporation plc - control through freedom
http://www.siriusit.co.uk
t: +44 870 608 0063

Sirius Labs: http://www.siriusit.co.uk/labs