public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Michael Tokarev <mjt@tls.msk.ru>
To: Andre Przywara <andre.przywara@amd.com>
Cc: Avi Kivity <avi@redhat.com>, KVM list <kvm@vger.kernel.org>
Subject: Re: Booting/installing WindowsNT
Date: Tue, 04 May 2010 16:40:31 +0400	[thread overview]
Message-ID: <4BE015BF.2010401@msgid.tls.msk.ru> (raw)
In-Reply-To: <4BE00E2A.2010901@amd.com>

Andre Przywara wrote:
[]
> I managed to get a NT4 CD and can acknowledge the issues you see. I am
> about to debug this now.
> With -cpu host (on a AMD K8, similar to Michael's) I get to the point
> Michael mentioned:
>  Microsoft (R) Windows NT (TM) Version 4.0 (Build 1381).
>  1 System Processor [512 MB Memory]  Multiprocessor Kernel
> Then it _seems_ to hang, checking for getting beyond a certain TSC value
> in a tight loop.
> (rdtsc; cmp %edx, %edi; ja @rdtsc; jb bailout; cmp %eax, %ebx; ja
> @rdtsdc; bailout:)
> But after some time (when I got back from the monitor, but also without
> going into) I could proceed with the installation.
> Michael, can you confirm this?

I've seen 3 variants here so far:

1.  normal installation.  It stops for a while after that kernel
  message you mentioned.  For several secodns, mabye even 20
  seconds.  And after a while it continues.  During all this
  time the guest cpu usage is 100% like you describe (a tight
  loop).  This is what I call "working" - I never bothered to
  think if that tight loop/pause is normal or not.  This is
  what happens for me with -cpu host.

2. with -cpu pentium it also displays that kernel message but
  stops here without any cpu usage whatsoever.  I waited for
  some 40 minutes at one point (I just forgot I started it but
  later on noticed there's a QEMU window floating around with
  that NT kernel message on it and nothing happening).

3.  In all other cases so far it BSoDs with STOP 0x3E error
  right before displaying that kernel message.

So.. I'm not sure if it's confirmation or not :)

Thanks!

/mjt

  reply	other threads:[~2010-05-04 12:40 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
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 [this message]
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=4BE015BF.2010401@msgid.tls.msk.ru \
    --to=mjt@tls.msk.ru \
    --cc=andre.przywara@amd.com \
    --cc=avi@redhat.com \
    --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