From: Gleb Natapov <gleb@redhat.com>
To: Michael Tokarev <mjt@tls.msk.ru>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] current qemu git does not work with win7 guest
Date: Mon, 7 May 2012 11:06:51 +0300 [thread overview]
Message-ID: <20120507080651.GH15960@redhat.com> (raw)
In-Reply-To: <4FA7816B.8090107@msgid.tls.msk.ru>
On Mon, May 07, 2012 at 12:01:47PM +0400, Michael Tokarev wrote:
> On 07.05.2012 11:45, Gleb Natapov wrote:
> > On Mon, May 07, 2012 at 10:06:58AM +0400, Michael Tokarev wrote:
> >> On 06.05.2012 23:03, Michael Tokarev wrote:
> >>> This is just a heads-up. I tried building current
> >>> qemu git today and running a win7 guest in it. Neither
> >>> already installed guest (which finds new hardware and
> >>> want to reboot) nor freshly installed win7 boots:
> >>> it boots for the first time, next it installs drivers,
> >>> but on reboot it BSODs with
> >>>
> >>> STOP: 0x0000005C (0x000000000000010B, 0x0000000000000003,
> >>> 0x000000000000000, 0x000000000000000)
> >>>
> >>> which is - according to ms docs - some HAL initialization
> >>> error, maybe related to ACPI.
> >>>
> >>> But apparently subsequent boots works. The freshly installed
> >>> win7 asked me something (even suggested to run safe mode
> >>> or something like that), I told it to boot normally and it
> >>> booted, and - seemingly - works since that.
> >>>
> >>> Still, this first-reboot-stop-0x0000005c is something I
> >>> have never seen from qemu or kvm before, even very old
> >>> versions worked fine.
> >>
> >> And the previously installed guest never reboots in currrent
> >> git version, always giving the 0x5c STOP code after first
> >> boot. This is aint good at all, as existing guests does
> >> not work anymore..... :(
> >>
>
> >>> P.S. I used 32bit version of qemu userspace and 32bit
> >>> version of win7 guest (so far), with 1G guest ram and
> >>> -cpu host, from AthlonII host cpu, and with -smp 1.
>
> > Can you verify that issue also exist in 64 bit version? What about
> > qemu-kvm?
>
> I'm trying. But the problem is that right now I'm swamped
> with other work. So far win7 x64 appears to work, it
> reboots without showing this "stop" thing or other issues,
> even with 32bit qemu userspace.
>
Sorry, didn't make myself clear. I mean 32bit version of host
kernel/qemu just to rule 32bitness out.
> Hmm. I've seen something has been mentioned about seabios and
> borken 32 bit winXP guest due to some 64bit patch, just today...
> Lemme check...
>
The patch is not in any released version as far as I see. Are you using
Seabios upstream?
--
Gleb.
next prev parent reply other threads:[~2012-05-07 8:07 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-06 19:03 [Qemu-devel] current qemu git does not work with win7 guest Michael Tokarev
2012-05-07 6:06 ` Michael Tokarev
2012-05-07 7:45 ` Gleb Natapov
2012-05-07 8:01 ` Michael Tokarev
2012-05-07 8:06 ` Gleb Natapov [this message]
2012-05-07 8:37 ` Michael Tokarev
2012-05-07 9:54 ` Michael Tokarev
2012-05-07 10:16 ` Gleb Natapov
2012-05-07 10:26 ` Michael Tokarev
2012-05-07 13:51 ` Michael Tokarev
2012-05-07 14:18 ` Jan Kiszka
2012-05-07 14:35 ` Michael Tokarev
2012-05-07 14:40 ` Jan Kiszka
2012-05-07 14:45 ` Michael Tokarev
2012-05-07 15:32 ` Jan Kiszka
2012-05-07 17:48 ` Michael Tokarev
2012-05-07 18:07 ` Jan Kiszka
2012-05-07 18:21 ` Michael Tokarev
2012-05-07 16:06 ` Avi Kivity
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=20120507080651.GH15960@redhat.com \
--to=gleb@redhat.com \
--cc=mjt@tls.msk.ru \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).