From: Gleb Natapov <gleb@redhat.com>
To: "Jun'ichi Nomura" <j-nomura@ce.jp.nec.com>
Cc: kvm@vger.kernel.org
Subject: Re: regression in v3.9? a guest stuck in BIOS if emulate_invalid_guest_state=Y
Date: Tue, 7 May 2013 15:06:11 +0300 [thread overview]
Message-ID: <20130507120611.GM12349@redhat.com> (raw)
In-Reply-To: <5188DFF7.1090808@ce.jp.nec.com>
On Tue, May 07, 2013 at 08:05:27PM +0900, Jun'ichi Nomura wrote:
> On 05/07/13 19:35, Gleb Natapov wrote:
> > On Tue, May 07, 2013 at 06:55:23PM +0900, Jun'ichi Nomura wrote:
> >> Hello,
> >>
> >> With v3.9 kernel and Nehalem CPU (i.e. unrestricted_guest=N),
> >> a guest stuck during boot (seemingly in BIOS).
> >> When setting emulate_invalid_guest_state=0, it does boot.
> >> (With v3.8 kernel and older, the guest used to boot fine by default.)
> >>
> >> The userspace is qemu-kvm of RHEL6.
> >> It seems the guest boots up fine with upstream qemu 1.4.1.
> >>
> >> Is this a kernel bug? Or is the userspace just too old to run on v3.9?
> >>
> >>
> > It should work. What seabios version are you using?
>
> It's seabios-0.6.1.2-26.el6.
> (and qemu-kvm-0.12.1.2-2.355.el6)
>
Works for me, but it looks like in your case the bios is in option rom.
What are you booting from? What's the qemu command line?
What is the output of "virsh qemu-monitor-command vm12 --hmp x/i $pc"
when it hangs?
--
Gleb.
next prev parent reply other threads:[~2013-05-07 12:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-07 9:55 regression in v3.9? a guest stuck in BIOS if emulate_invalid_guest_state=Y Jun'ichi Nomura
2013-05-07 10:35 ` Gleb Natapov
2013-05-07 11:05 ` Jun'ichi Nomura
2013-05-07 12:06 ` Gleb Natapov [this message]
2013-05-07 14:46 ` Paolo Bonzini
2013-05-07 15:04 ` Gleb Natapov
2013-05-07 16:11 ` Paolo Bonzini
2013-05-08 3:22 ` Jun'ichi Nomura
2013-05-08 7:34 ` Jun'ichi Nomura
2013-05-08 8:29 ` Paolo Bonzini
2013-05-10 2:51 ` Jun'ichi Nomura
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=20130507120611.GM12349@redhat.com \
--to=gleb@redhat.com \
--cc=j-nomura@ce.jp.nec.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