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: Tue, 05 Jan 2010 19:15:20 +0200 Message-ID: <4B4373A8.8050807@redhat.com> References: <4B43643F.8090303@siriusit.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; 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]:19367 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754903Ab0AERPa (ORCPT ); Tue, 5 Jan 2010 12:15:30 -0500 In-Reply-To: <4B43643F.8090303@siriusit.co.uk> Sender: kvm-owner@vger.kernel.org List-ID: On 01/05/2010 06:09 PM, Mark Cave-Ayland wrote: > Hi all, > > I think I'm experiencing a regression with the new qemu-kvm-0.12.1.2 > release compared to qemu-kvm-0.12.1.1 with a WinXP guest on Linux. > > I can boot my WinXP guest without a problem under qemu-kvm-0.12.1.1, > however under qemu-kvm-0.12.1.2 a couple of seconds after reaching the > login screen, the WinXP guest goes BSOD with the following error: > DRIVER_UNLOADED_WITHOUT_CANCELING_PENDING_OPERATIONS. > > I've confirmed by switching between the two installations several > times that the error consistently occurs with qemu-kvm-0.12.1.2 but > not qemu-kvm-0.12.1.1. Is this a known issue? This is on an x86_64 > Debian Lenny host with a 2.6.32.2 kernel on Intel. It's not a known issue. What's your command line? What's your host cpu type? -- error compiling committee.c: too many arguments to function