Re: Booting/installing WindowsNT

[Michael Tokarev <mjt@tls.msk.ru>]

02.05.2010 14:04, Avi Kivity wrote:
> On 05/01/2010 12:40 AM, Michael Tokarev wrote:
>> 01.05.2010 00:59, Michael Tokarev wrote:
>>> Apparently with current kvm stable (0.12.3)
>>> Windows NT 4.0 does not install anymore.
>>>
>>> With default -cpu, it boots, displays the
>>> "Inspecting your hardware configuration"
>>> message and BSODs with "STOP: 0x0000003E"
>>> error as shown here:
>>> http://www.corpit.ru/mjt/winnt4_1.gif
>>> With -cpu pentium the situation is a
>>> >bit< better, it displays:
>>>
>>> Microsoft (R) Windows NT (TM) Version 4.0 (Build 1381).
>>> 1 System Processor [512 MB Memory] Multiprocessor Kernel
>>>
>>> and stops there with 100% CPU usage, never
>>> going any further.
>>>
>>> Kvm command line is trivial, with -hda
>>> and -cdrom and -vga std (with -vga cirrus
>>> it displays garbage here). The only parameters
>>> of interest are:
>>>
>>> -no-acpi - this one has no visible effect
>>> -cpu pentium - tried that with some change
>>> but no success anyway.
>>
>> I were able to boot and install it just fine
>> using -cpu host (without -no-acpi or any
>> other option).
>>
>> Microsoft(R) Windows NT(R) version 4.0 (Build 1381: Service Pack 1)
>> (C) 1981-1996
>>
>> where my host cpu is Athlon X2-64 4850e (2 cores).
>>
>> I tried a few other -cpu values, but no luck - it
>> either BSODs with 0x3E error, or stops after first
>> kernel message.
>
> Interesting. Can you try -cpu host with the family/model/vendor etc used
> by -cpu qemu64?

Here we go.

cpuinfo from kvm default cpu:
processor	: 0
vendor_id	: AuthenticAMD
cpu family	: 6
model		: 2
model name	: QEMU Virtual CPU version 0.12.3
stepping	: 3
cpu MHz		: 2500.000
cache size	: 512 KB
fpu		: yes
fpu_exception	: yes
cpuid level	: 4
wp		: yes
flags		: fpu de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 syscall nx lm up pni cx16 hypervisor lahf_lm
bogomips	: 5002.33
TLB size	: 1024 4K pages
clflush size	: 64
cache_alignment	: 64
address sizes	: 40 bits physical, 48 bits virtual
power management:


cpuinfo from host:

processor	: 0
vendor_id	: AuthenticAMD
cpu family	: 15
model		: 107
model name	: AMD Athlon(tm) Dual Core Processor 4850e
stepping	: 2
cpu MHz		: 1000.000
cache size	: 512 KB
physical id	: 0
siblings	: 2
core id		: 0
cpu cores	: 2
apicid		: 0
initial apicid	: 0
fpu		: yes
fpu_exception	: yes
cpuid level	: 1
wp		: yes
flags		: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt rdtscp lm 3dnowext 3dnow rep_good extd_apicid pni cx16 lahf_lm cmp_legacy svm extapic cr8_legacy 3dnowprefetch lbrv
bogomips	: 1003.48
TLB size	: 1024 4K pages
clflush size	: 64
cache_alignment	: 64
address sizes	: 40 bits physical, 48 bits virtual
power management: ts fid vid ttp tm stc 100mhzsteps


running with -cpu host,vendor=AuthenticAMD,model=2,family=6 :

processor	: 0
vendor_id	: AuthenticAMD
cpu family	: 6
model		: 2
model name	: AMD Athlon(tm) Dual Core Processor 4850e
stepping	: 2
cpu MHz		: 2500.000
cache size	: 512 KB
fpu		: yes
fpu_exception	: yes
cpuid level	: 1
wp		: yes
flags		: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 syscall nx mmxext fxsr_opt lm up pni cx16 hypervisor lahf_lm cmp_legacy cr8_legacy 3dnowprefetch
bogomips	: 4401.33
TLB size	: 1024 4K pages
clflush size	: 64
cache_alignment	: 64
address sizes	: 40 bits physical, 48 bits virtual
power management:

WindowsNT works, just like with -cpu host.

There are a few more data points.

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.

Thanks!

/mjt