All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andre Przywara <andre.przywara@amd.com>
To: Michael Tokarev <mjt@tls.msk.ru>
Cc: Avi Kivity <avi@redhat.com>, KVM list <kvm@vger.kernel.org>
Subject: Re: Booting/installing WindowsNT
Date: Tue, 4 May 2010 17:27:19 +0200	[thread overview]
Message-ID: <4BE03CD7.8090105@amd.com> (raw)
In-Reply-To: <4BE015BF.2010401@msgid.tls.msk.ru>

Michael Tokarev wrote:
  > 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.
OK, I see that, too.

> 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).
Agreed. It stucks in a sti;hlt;ret, obviously waiting in vain for an 
interrupt. Interestingly it works with -smp 2. Will further investigate.

> 3.  In all other cases so far it BSoDs with STOP 0x3E error
>   right before displaying that kernel message.
MSDN talks about a mulitprocessor configuration error:
http://msdn.microsoft.com/en-us/library/ms819006.aspx
I suspected the offline CPUs in the mptable that confuse NT. But -smp 
1,maxcpus=1 does not make a difference. I will try to dig deeper in this 
area.

> So.. I'm not sure if it's confirmation or not :)
I take this as one. Thanks for the clarification.

Regards,
Andre.

-- 
Andre Przywara
AMD-Operating System Research Center (OSRC), Dresden, Germany
Tel: +49 351 488-3567-12


  reply	other threads:[~2010-05-04 15:27 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
2010-05-04 15:27                     ` Andre Przywara [this message]
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=4BE03CD7.8090105@amd.com \
    --to=andre.przywara@amd.com \
    --cc=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.