From mboxrd@z Thu Jan 1 00:00:00 1970 From: Michael Tokarev Subject: Re: Booting/installing WindowsNT Date: Sun, 02 May 2010 20:44:35 +0400 Message-ID: <4BDDABF3.3040304@msgid.tls.msk.ru> References: <4BDB44C2.7090204@msgid.tls.msk.ru> <4BDB4E58.50805@msgid.tls.msk.ru> <4BDD4E32.2080503@redhat.com> <4BDDA455.8090001@msgid.tls.msk.ru> <4BDDAB03.4030206@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: KVM list To: Avi Kivity Return-path: Received: from isrv.corpit.ru ([81.13.33.159]:57259 "EHLO isrv.corpit.ru" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757293Ab0EBQog (ORCPT ); Sun, 2 May 2010 12:44:36 -0400 In-Reply-To: <4BDDAB03.4030206@redhat.com> Sender: kvm-owner@vger.kernel.org List-ID: 02.05.2010 20:40, Avi Kivity wrote: > On 05/02/2010 07:12 PM, Michael Tokarev wrote: >> >> >> After installing, winNT does not boot without -cpu host, >> with exactly the same diagnostics as before (0x0000003E). >> But: After installing service pack 6, it boots just fine >> with any -cpu, including the default qemu64. >> >> With qemu-kvm-0.11.4 it all just works without any >> additional options. >> >> I asked the other person with this issue (see debian bug, >> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=575439 ) >> to try -cpu host, but for him it didn't help. I suspect >> (but don't know for sure) he's running it on Intel CPU. > > Ok. Please try the following: > > qemu-0.12 with 0.11's bios. I tried that as one of first options. I can't get it to boot at all, kvm displays the sdl window with black background and it stays black, no even bios messages are shown. Thanks! /mjt > compare the cpuid flags from 0.11 and 0.12, mix and match until 0.12 works. >