From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Jun'ichi Nomura" 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 Message-ID: <518C60CD.3030206@ce.jp.nec.com> References: <5188CF8B.8040809@ce.jp.nec.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-2022-JP Content-Transfer-Encoding: 7bit To: kvm@vger.kernel.org, Paolo Bonzini , Gleb Natapov Return-path: Received: from TYO202.gate.nec.co.jp ([210.143.35.52]:43295 "EHLO tyo202.gate.nec.co.jp" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755562Ab3EJCw0 (ORCPT ); Thu, 9 May 2013 22:52:26 -0400 In-Reply-To: <5188CF8B.8040809@ce.jp.nec.com> Sender: kvm-owner@vger.kernel.org List-ID: 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