From mboxrd@z Thu Jan 1 00:00:00 1970 From: Michael Tokarev Subject: Re: Booting/installing WindowsNT Date: Wed, 05 May 2010 12:51:54 +0400 Message-ID: <4BE131AA.8040506@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> <4BDE882F.5000009@amd.com> <4BDE8DF4.8070604@redhat.com> <4BDE9757.8090809@amd.com> <4BDF01CA.80505@msgid.tls.msk.ru> <4BDFE3A7.2050706@redhat.com> <4BE00E2A.2010901@amd.com> <4BE015BF.2010401@msgid.tls.msk.ru> <4BE03CD7.8090105@amd.com> <4BE049F5.4000500@redhat.com> <4BE12D1E.5000602@amd.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Avi Kivity , KVM list To: Andre Przywara Return-path: Received: from isrv.corpit.ru ([81.13.33.159]:37031 "EHLO isrv.corpit.ru" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932375Ab0EEIvz (ORCPT ); Wed, 5 May 2010 04:51:55 -0400 In-Reply-To: <4BE12D1E.5000602@amd.com> Sender: kvm-owner@vger.kernel.org List-ID: 05.05.2010 12:32, Andre Przywara wrote: > Avi Kivity wrote: >> On 05/04/2010 06:27 PM, Andre Przywara wrote: >>> >>>> 3. In all other cases so far it BSoDs with STOP 0x3E error >>>> right before displaying that kernel message. >>> MSDN talks about a mulitprocessor configuration error: >>> http://msdn.microsoft.com/en-us/library/ms819006.aspx >>> I suspected the offline CPUs in the mptable that confuse NT. But -smp >>> 1,maxcpus=1 does not make a difference. I will try to dig deeper in >>> this area. > OK, I tackled this down. It is the max CPUID level that differs. > In the AMD CPUID guide leafs 0000_0002 till 0000_0004 are reserved, the > CPU that Michael and I used (K8RevF) actually have a max leaf of 1 here. > Default qemu64 has a max leaf of 4. > So by saying -cpu qemu64,level=1 (or 2 or 3) it works for me. > Modern OS only read leaf 4 on Intel systems, it seems that NT4 is > missing this. Confirmed, with -cpu qemu64,level=[123] it works for me as well. Note again that after service pack 6 (I haven't tried other SPs), the problem goes away entirely -- winNT SP6 works with the default kvm cpu just fine. Thanks! /mjt