From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: WinXP virtual crashes on 0.12.1.2 but not 0.12.1.1 Date: Mon, 25 Jan 2010 17:27:43 +0200 Message-ID: <4B5DB86F.202@redhat.com> 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> <4B5DB5A8.4000108@siriusit.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: kvm@vger.kernel.org To: Mark Cave-Ayland Return-path: Received: from mx1.redhat.com ([209.132.183.28]:42195 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753881Ab0AYP1y (ORCPT ); Mon, 25 Jan 2010 10:27:54 -0500 In-Reply-To: <4B5DB5A8.4000108@siriusit.co.uk> Sender: kvm-owner@vger.kernel.org List-ID: On 01/25/2010 05:15 PM, Mark Cave-Ayland wrote: >>> 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. Well, there was a regression, but it was in 0.12.1.1. There were two bugs involved, a serious one (that caused the cpuid to show up as AMD) hiding the less serious one (that causes processor.sys to BSOD). > > 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. I'd like to find out why processor.sys fails, but the .1->.2 change isn't any help unfortunately. It looks like here too there are two bugs involved: one in kvm which doesn't act like processor.sys expects it, and one in processor.sys which causes it to UNLOAD_ITSELF_WITHOUT_CANCELLING_PENDING_OPERATIONS. You might try running with kvm trace enabled and look at msr and cpuid accesses just prior to the crash. -- error compiling committee.c: too many arguments to function