From mboxrd@z Thu Jan 1 00:00:00 1970 From: Gleb Natapov 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 Message-ID: <20130507120611.GM12349@redhat.com> References: <5188CF8B.8040809@ce.jp.nec.com> <20130507103520.GL12349@redhat.com> <5188DFF7.1090808@ce.jp.nec.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: kvm@vger.kernel.org To: "Jun'ichi Nomura" Return-path: Received: from mx1.redhat.com ([209.132.183.28]:25555 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757811Ab3EGMGP (ORCPT ); Tue, 7 May 2013 08:06:15 -0400 Content-Disposition: inline In-Reply-To: <5188DFF7.1090808@ce.jp.nec.com> Sender: kvm-owner@vger.kernel.org List-ID: 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.