All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jun'ichi Nomura" <j-nomura@ce.jp.nec.com>
To: kvm@vger.kernel.org, Paolo Bonzini <pbonzini@redhat.com>,
	Gleb Natapov <gleb@redhat.com>
Subject: Re: regression in v3.9? a guest stuck in BIOS if emulate_invalid_guest_state=Y
Date: Fri, 10 May 2013 11:51:57 +0900	[thread overview]
Message-ID: <518C60CD.3030206@ce.jp.nec.com> (raw)
In-Reply-To: <5188CF8B.8040809@ce.jp.nec.com>

On 05/07/13 18:55, Jun'ichi Nomura wrote:
> 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?

With the following patches on top of v3.9, the problem goes away.
Thank you!

  Gleb Natapov (1):
      KVM: VMX: fix halt emulation while emulating invalid guest sate

  Paolo Bonzini (3):
      KVM: emulator: emulate AAM
      KVM: emulator: emulate XLAT
      KVM: emulator: emulate SALC

-- 
Jun'ichi Nomura, NEC Corporation


      parent reply	other threads:[~2013-05-10  2:52 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
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 [this message]

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=518C60CD.3030206@ce.jp.nec.com \
    --to=j-nomura@ce.jp.nec.com \
    --cc=gleb@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=pbonzini@redhat.com \
    /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.