From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mark Cave-Ayland Subject: Re: WinXP virtual crashes on 0.12.1.2 but not 0.12.1.1 Date: Mon, 25 Jan 2010 15:15:52 +0000 Message-ID: <4B5DB5A8.4000108@siriusit.co.uk> References: <4B43643F.8090303@siriusit.co.uk> <4B4373A8.8050807@redhat.com> <4B44731A.4020405@siriusit.co.uk> <4B448513.6070505@redhat.com> <4B448715.9000602@siriusit.co.uk> <4B4489F5.4000409@redhat.com> <4B44B018.90003@siriusit.co.uk> <4B45A05A.5020304@redhat.com> <4B45AFA1.6090008@siriusit.co.uk> <4B5BF98A.5040408@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: kvm@vger.kernel.org To: Avi Kivity Return-path: Received: from ra.siriusit.co.uk ([217.207.197.130]:37756 "EHLO ra.siriusit.co.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751988Ab0AYPQK (ORCPT ); Mon, 25 Jan 2010 10:16:10 -0500 In-Reply-To: <4B5BF98A.5040408@redhat.com> Sender: kvm-owner@vger.kernel.org List-ID: 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