From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:35495) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RQd5h-0003Pn-UT for qemu-devel@nongnu.org; Wed, 16 Nov 2011 05:51:43 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1RQd5d-0005m1-L8 for qemu-devel@nongnu.org; Wed, 16 Nov 2011 05:51:41 -0500 Received: from mx1.redhat.com ([209.132.183.28]:45290) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RQd5d-0005lv-E7 for qemu-devel@nongnu.org; Wed, 16 Nov 2011 05:51:37 -0500 Date: Wed, 16 Nov 2011 12:51:32 +0200 From: Gleb Natapov Message-ID: <20111116105132.GI3225@redhat.com> References: <4EC38CF2.7000707@linux.vnet.ibm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline Content-Transfer-Encoding: quoted-printable In-Reply-To: Subject: Re: [Qemu-devel] Windows 7 shutdown causes BSOD List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Stefan Hajnoczi Cc: hkran , Michael Tokarev , qemu-devel , "Mars.Cao" On Wed, Nov 16, 2011 at 10:48:15AM +0000, Stefan Hajnoczi wrote: > On Wed, Nov 16, 2011 at 10:14 AM, hkran wrote: > > On 11/15/2011 09:17 PM, Stefan Hajnoczi wrote: > >> > >> On Fri, Nov 4, 2011 at 11:25 AM, Stefan Hajnoczi > >> =9Awrote: > >>> > >>> On Fri, Nov 4, 2011 at 10:48 AM, Stefan Hajnoczi > >>> =9Awrote: > >>>> > >>>> Windows 7 32-bit guest blue screens when I shut it down properly with > >>>> Start | Shut Down. =9AThe blue screen is only displayed for a split > >>>> second before the guest reboots so I am not able to easily tell what > >>>> it says. =9AMy guess is that Windows is triple-faulting or soft > >>>> rebooting - note that I told Windows to shut down, not reboot. > >>>> > >>>> This issue happens on qemu.git/master (and Debian kvm 0.14.1+dfsg-3). > >>>> Here is the QEMU command-line: > >>>> > >>>> x86_64-softmmu/qemu-system-x86_64 -L pc-bios -cpu qemu32 -enable-kvm > >>>> -m 1024 -rtc base=3Dlocaltime -drive > >>>> file=3Dwin7.img,if=3Dnone,id=3Ddrive-ide0-0-0,format=3Draw -device > >>>> ide-drive,bus=3Dide.0,unit=3D0,drive=3Ddrive-ide0-0-0,id=3Dide0-0-0,= bootindex=3D1 > >>>> > >>>> Questions: > >>>> > >>>> Is anyone else experiencing this? > >>>> > >>>> Is anyone fixing this? > >>>> > >>>> If not I will play with it. =9ADisabling ACPI might reveal the sourc= e of > >>>> the problem. =9AIf that turns up nothing I will try to get the BSOD = or > >>>> WinDbg output. > >>> > >>> Thanks to Andreas Faerber and Michael Tokarev I found out the > >>> automatic reboot can be disabled in Windows. =9AHere is the BSOD > >>> information: > >>> > >>> IRQL_NOT_LESS_OR_EQUAL > >>> STOP: 0x0000000A (0x00000000,0x000000FF,0x00000001,0x828B7220) > >> > >> This decodes to: > >> "Windows or a kernel-mode driver accessed paged memory at > >> DISPATCH_LEVEL or above." > >> > >> Memory referenced: 0x00000000 > >> IRQL: 0xff > >> Read/write: Write (1) > >> Address which referenced memory: 0x828B7220 > >> > >> http://msdn.microsoft.com/en-us/library/ff560129%28v=3DVS.85%29.aspx > >> > >> Looks like a NULL pointer reference or maybe a deliberate "we should > >> never get here" failure. > >> > >> Stefan > >> > > I can reproduce this bug in my environment and found out that it has > > something with the type of "CPU". > > I tried the command line args as the same as Stefan's and definitely ca= sue > > the BSOD. > > If i change the "-cpu qemu32" to "-cpu qemu64" or "-cpu core2duo" or > > nothing. it will shutdown as expected, that means something? >=20 > Thanks for sharing. The guest is definitely sees a differed CPUID and > can therefore take different code paths. I'm not sure what > specifically could have changed. >=20 Try adding/removing individual cpuid bits. -- Gleb.