public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Michael Tokarev <mjt@tls.msk.ru>
Cc: KVM list <kvm@vger.kernel.org>
Subject: Re: Booting/installing WindowsNT
Date: Sun, 02 May 2010 13:04:34 +0300	[thread overview]
Message-ID: <4BDD4E32.2080503@redhat.com> (raw)
In-Reply-To: <4BDB4E58.50805@msgid.tls.msk.ru>

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?


-- 
error compiling committee.c: too many arguments to function


  reply	other threads:[~2010-05-02 10:04 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-30 20:59 Booting/installing WindowsNT Michael Tokarev
2010-04-30 21:40 ` Michael Tokarev
2010-05-02 10:04   ` Avi Kivity [this message]
2010-05-02 16:12     ` Michael Tokarev
2010-05-02 16:40       ` Avi Kivity
2010-05-02 16:44         ` Michael Tokarev
2010-05-03  8:24       ` Andre Przywara
2010-05-03  8:48         ` Avi Kivity
2010-05-03  9:28           ` Andre Przywara
2010-05-03 17:03             ` Michael Tokarev
2010-05-04  9:06               ` Avi Kivity
2010-05-04 12:08                 ` Andre Przywara
2010-05-04 12:40                   ` Michael Tokarev
2010-05-04 15:27                     ` Andre Przywara
2010-05-04 16:23                       ` Avi Kivity
2010-05-05  4:35                         ` Michael Tokarev
2010-05-05  8:32                         ` Andre Przywara
2010-05-05  8:41                           ` Avi Kivity
2010-05-05  8:53                             ` Andre Przywara
2010-05-05  8:51                           ` Michael Tokarev
2010-05-05  8:59                             ` Avi Kivity
2010-05-05 10:18                             ` Andre Przywara
2010-05-05 11:35                               ` Avi Kivity
2010-05-03 16:54         ` 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=4BDD4E32.2080503@redhat.com \
    --to=avi@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=mjt@tls.msk.ru \
    /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