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

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

[Michael Tokarev]

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".

Note that it is when upgrading from -72 to 0.12.  But the
second person on the bug page also tried to reinstall the
OS, and that failed as well, now with a different error
message.

I'll try to find an nt4 cdrom here to try it, but I can't
promise anything....

Thanks!

/mjt

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

[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".
>
> Note that it is when upgrading from -72 to 0.12. But the
> second person on the bug page also tried to reinstall the
> OS, and that failed as well, now with a different error
> message.
>
> I'll try to find an nt4 cdrom here to try it, but I can't
> promise anything....

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

> Thanks!
>
> /mjt

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

[Thomas Mueller]

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".
>>
>> Note that it is when upgrading from -72 to 0.12. But the second person
>> on the bug page also tried to reinstall the OS, and that failed as
>> well, now with a different error message.
>>
>> I'll try to find an nt4 cdrom here to try it, but I can't promise
>> anything....
> 
> 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 
file=winnt.raw,if=ide,boot=on" ?

- Thomas

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

[Michael Tokarev]

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

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

[Gleb Natapov]

On Sat, May 01, 2010 at 09:30:03PM +0400, Michael Tokarev wrote:
> >file=winnt.raw,if=ide,boot=on" ?
> 
> Um, that's equivalent, no?
> 
boot=on is not needed and does more harm than good with ide interface.

--
			Gleb.

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

[Avi Kivity]

On 04/30/2010 11:06 PM, 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".
>
> Note that it is when upgrading from -72 to 0.12.  But the
> second person on the bug page also tried to reinstall the
> OS, and that failed as well, now with a different error
> message.
>

What about 0.11?  Does it work?

-- 
Do not meddle in the internals of kernels, for they are subtle and quick to panic.

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

[Michael Tokarev]

02.05.2010 10:06, Avi Kivity wrote:
> On 04/30/2010 11:06 PM, 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".
>>
>> Note that it is when upgrading from -72 to 0.12  [...]
>
> What about 0.11? Does it work?

After finding the cause of the other problem (in the thread
"Booting/Installing Windows NT", all thanks going to Andre
Przywara), I can proceed with this issue finally.

I tried installing winNT here on old kvm and upgrading kvm.
So far I can say that if winNT were installed with kvm-72
and later, it boots just fine in kvm-0.12.

So I don't know what the problem is in this case.  Maybe
it is becauese the OP installed his winNT guest before
kvm-72 and now in 0.12 the guest is not able to find its
filesystem anymore, or maybe it's because there was some
bug fixed in service pack 1 (which I used here) that makes
the problem go away - I dunno.

But having in mind how picky winNT was for the hardware
changes, I don't think it's worth the effort to debug
this problem further - winNT is really ancient system,
and having upgrade path for kvm from some ancient
development snapshot to current version isn't that
important, IMHO.  Yes, a few people will be hit by this
issue, which is a sad thing, but seriously, we've more
interesting things to do ;)

Thanks!

/mjt