Re: What changed since kvm-72 resulting in winNT to fail to boot (STOP 0x0000001E) ?

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

01.05.2010 15:58, Thomas Mueller wrote:
> Am Sat, 01 May 2010 00:36:51 +0400 schrieb Michael Tokarev:
>
>> 01.05.2010 00:06, Michael Tokarev wrote:
>>> I've a bugreport handy, see
>>> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=575439 about the
>>> apparent problem booting winNT 4 in kvm 0.12. At least 2 people were
>>> hit by this issue. In short, when booting winNT 4.0, it BSODs with
>>> error code 0x0000001E, which means "inaccessible boot device".
[]
>> I found an old winNT-4.0 install CD-Rom and tried that.  But it stops
>> right at "Inspecting your hardware configuration" stage, with the error:
>> "STOP: 0x0000003E" (BSOD).  According to MS --
>> http://msdn.microsoft.com/en-us/library/ms819006.aspx -- this means
>> "multiprocessor configuration is not supported. For example, not all
>> processors are at the same level or of the same type. There might also
>> be mismatched coprocessor support." Obviously I'm running it with -smp
>> 1, here's the complete kvm command line:
>>    kvm -hda winNT.raw -m 512 -cdrom Win_NT_4_Enterprise.iso -localtime
>>    -vga std
>> (with default vga - cirrus - it displays garbage)
>>
>> And the complete BSOD:
>>     http://www.corpit.ru/mjt/winnt4_1.gif
>
> what about setting "-cpu<cputype>" to a singlecore type (get list with "-
> cpu ?"), things like "-no-acpi" and instead of "-hda" "-drive

I tried numerous -cpu things, since that's something that
at least has some effect.  Outlined in another thread.
Basically, -cpu host (on my amd athlon x2-64) let it to
install.  All other -cpu variations I tried didn't help.
I mentioned -no-acpi, it has no effect.

> file=winnt.raw,if=ide,boot=on" ?

Um, that's equivalent, no?

Thanks!

/mjt