From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?UTF-8?B?QW5kcsOpIFdlaWRlbWFubg==?= Subject: Re: Windows7 crashes inside the VM when starting a certain program Date: Fri, 29 Jul 2011 09:20:35 +0200 Message-ID: <4E325F43.4050701@web.de> References: <4E154370.5090101@web.de> <4E2E50A0.3040706@web.de> <20110726100809.GK4404@redhat.com> <4E2E9DA8.7040503@web.de> <20110727085627.GO4404@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: QUOTED-PRINTABLE Cc: kvm@vger.kernel.org To: Gleb Natapov Return-path: Received: from fmmailgate01.web.de ([217.72.192.221]:33692 "EHLO fmmailgate01.web.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754717Ab1G2HUn (ORCPT ); Fri, 29 Jul 2011 03:20:43 -0400 In-Reply-To: <20110727085627.GO4404@redhat.com> Sender: kvm-owner@vger.kernel.org List-ID: On 27.07.2011 10:56, Gleb Natapov wrote: > On Tue, Jul 26, 2011 at 12:57:44PM +0200, Andr=C3=A9 Weidemann wrote: >> Hi, >> >> On 26.07.2011 12:08, Gleb Natapov wrote: >>> On Tue, Jul 26, 2011 at 07:29:04AM +0200, Andr=C3=A9 Weidemann wrot= e: >>>> On 07.07.2011 07:26, Andr=C3=A9 Weidemann wrote: >>>>> Hi, >>>>> I am running Windows7 x64 in a VM which crashes after starting a = certain >>>>> game. Actually there are two games both from the same company, th= at make >>>>> the VM crash after starting them. >>>>> Windows crashes right after starting the game. With the 1st game = the >>>>> screen goes black as usual and the cursor keeps spinning for 3-5 = seconds >>>>> until Windows crashes. With the second game I get to 3D the login >>>>> screen. The game then crashes after logging in. >>>>> Windows displays this error message on the first crash: >>>>> http://pastebin.com/kMzk9Jif >>>>> Windows then finishes writing the crash dump and restarts. >>>>> I can reproduce Windows crashing every time I start the game whil= e the >>>>> VM keeps running without any problems. >>>>> When Windows reboots after the first crash and the game is starte= d >>>>> again, the message on the following blue screen changes slightly = and >>>>> stays the same(except for the addresses) for every following cras= h: >>>>> http://pastebin.com/jVtBc4ZH >>>>> >>>>> I first thought that this might be related to a certain feature i= n 3D >>>>> acceleration being used, but Futuremark 3DMark Vantage or 3DMark = 11 run >>>>> without any problems. They run a bit choppy on some occasions, bu= t do >>>>> that without crashing Windows7 or the VM. >>>>> >>>>> How can I proceed to investigate what is going wrong? >>>> >>>> I did some testing and found out that Windows7 does not crash >>>> anymore when changing "-cpu host" to "-cpu Nehalem". After doing s= o, >>> What is your host cpu (cat /proc/cpuinfo)? >> >> The server is currently running on 2 out of 8 cores with kernel boot >> parameter "maxcpus=3D2". >> >> flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr >> pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm >> pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good >> xtopology nonstop_tsc aperfmperf pni dtes64 monitor ds_cpl vmx est >> tm2 ssse3 cx16 xtpr pdcm sse4_1 sse4_2 popcnt lahf_lm ida tpr_shadow >> vnmi flexpriority ept vpid > Flags that are present on -cpu host but not -cpu Nehalem (excluding v= mx > related flags): > > vme dts acpi ss ht tm pbe rdtscp constant_tsc arch_perfmon pebs bts r= ep_good > xtopology nonstop_tsc aperfmperf dtes64 monitor ds_cpl est tm2 xtpr p= dcm ida > > Some of them may be synthetic and some of them may be filtered by KVM= =2E > > Can you try to run "-cpu host,-vme,-dts..." (specifying all of those > flags with -). Drop those that qemu does not recognize. See if result > will be the same as with -cpu Nehalem. If yes, then try to find out w= ith > flag make the difference. I started the VM with all flags that differ between the two CPUs. After= =20 removing the ones qemu-kvm did not recognize, I started the VM again=20 with the following line: -cpu=20 host,-vme,-acpi,-ss,-ht,-tm,-pbe,-rdtscp,-dtes64,-monitor,-ds_cpl,-est,= -tm2,-xtpr,-pdcm=20 \ Running the program under Windows7 inside the VM, caused Windows to=20 crash again with a BSoD. The disassembly of the address fffff8000288320c shows the following: http://pastebin.com/7yzTYJSG Andr=C3=A9