From: Andre Przywara <andre.przywara@amd.com>
To: Avi Kivity <avi@redhat.com>
Cc: Michael Tokarev <mjt@tls.msk.ru>, KVM list <kvm@vger.kernel.org>
Subject: Re: Booting/installing WindowsNT
Date: Tue, 4 May 2010 14:08:10 +0200 [thread overview]
Message-ID: <4BE00E2A.2010901@amd.com> (raw)
In-Reply-To: <4BDFE3A7.2050706@redhat.com>
Avi Kivity wrote:
> On 05/03/2010 08:03 PM, Michael Tokarev wrote:
>>> Michael, can you try to use -cpu host,-vme and see if that makes a
>>> difference?
>>
>>
>> With -cpu host,-vme winNT boots just fine as with just -cpu host.
>>
>> I also tried with -cpu qemu64 and kvm64, with +vme and -vme (4
>> combinations in total) - in all cases winNT crashes with the
>> same 0x0000003E error. So it appears that vme makes no
>> difference.
>
> Please try again the model/vendor/family. I suggest using x86info on
> both to see what the differences are, using -cpu host with overrides to
> make it equivalent to qemu64 (and verifying it fails), then removing the
> overrides one by one until it works.
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 will now try to get behind the STOP 3E error.
Regards,
Andre.
--
Andre Przywara
AMD-Operating System Research Center (OSRC), Dresden, Germany
Tel: +49 351 448-3567-12
next prev parent reply other threads:[~2010-05-04 12:11 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 [this message]
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=4BE00E2A.2010901@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox