From: Michael Tokarev <mjt@tls.msk.ru>
To: KVM list <kvm@vger.kernel.org>
Subject: Re: What changed since kvm-72 resulting in winNT to fail to boot (STOP 0x0000001E) ?
Date: Sat, 01 May 2010 00:36:51 +0400 [thread overview]
Message-ID: <4BDB3F63.60900@msgid.tls.msk.ru> (raw)
In-Reply-To: <4BDB3847.60107@msgid.tls.msk.ru>
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
next prev parent reply other threads:[~2010-04-30 20:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-30 20:06 What changed since kvm-72 resulting in winNT to fail to boot (STOP 0x0000001E) ? Michael Tokarev
2010-04-30 20:36 ` Michael Tokarev [this message]
2010-05-01 11:58 ` Thomas Mueller
2010-05-01 17:30 ` Michael Tokarev
2010-05-02 5:27 ` Gleb Natapov
2010-05-02 6:06 ` Avi Kivity
2010-05-05 10:05 ` Michael Tokarev
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4BDB3F63.60900@msgid.tls.msk.ru \
--to=mjt@tls.msk.ru \
--cc=kvm@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox