From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:42428) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VEeFf-0001E5-Du for qemu-devel@nongnu.org; Wed, 28 Aug 2013 07:49:36 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1VEeFa-0002xb-7V for qemu-devel@nongnu.org; Wed, 28 Aug 2013 07:49:31 -0400 Received: from cantor2.suse.de ([195.135.220.15]:40646 helo=mx2.suse.de) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VEeFZ-0002xX-Uc for qemu-devel@nongnu.org; Wed, 28 Aug 2013 07:49:26 -0400 Message-ID: <521DE3C0.4030603@suse.de> Date: Wed, 28 Aug 2013 13:49:20 +0200 From: =?ISO-8859-1?Q?Andreas_F=E4rber?= MIME-Version: 1.0 References: <20130828103552.GC2038@GaryOffice.site> <521DE2EB.9050404@redhat.com> In-Reply-To: <521DE2EB.9050404@redhat.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Subject: Re: [Qemu-devel] [edk2] OVMF hung on qemu 1.6.0 with KVM List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Laszlo Ersek Cc: Jordan Justen , edk2-devel@lists.sourceforge.net, "qemu-devel@nongnu.org" , Alexander Graf , Gary Ching-Pang Lin , Ludwig Nussel Am 28.08.2013 13:45, schrieb Laszlo Ersek: > (qemu-devel CC'd) >=20 > On 08/28/13 12:35, Gary Ching-Pang Lin wrote: >> Hi, >> >> I recently updated qemu to 1.6.0 and found OVMF just showed a blank >> screen when kvm was enabled. I tried to dump OVMF log with the >> following commond but nothing was stored in debug.log. >> >> qemu-system-x86_64 -s -enable-kvm -bios OVMF.fd -debugcon file:debug.l= og -global isa-debugcon.iobase=3D0x402 >> >> The kvm trace was recorded with "trace-cmd record -b 20000 -e kvm" >> and uploaded to the following link: >> https://docs.google.com/file/d/0B9hbtlc_aK_gcGh2TDZLUVlzWWc/edit?usp=3D= sharing >> >> I found a similar case with kernel < 3.9, but I already upgraded linux >> kernel to 3.10.5, so this may be another bug. >=20 > Well, the usual first response in cases like this is... >=20 > Can you bisect qemu? :) We had a similar report: https://bugzilla.novell.com/show_bug.cgi?id=3D835895 git-bisect said: 235e8982ad393e5611cb892df54881c872eea9e1 is the first bad commit commit 235e8982ad393e5611cb892df54881c872eea9e1 Author: Jordan Justen Date: Wed May 29 01:27:26 2013 -0700 kvm: support using KVM_MEM_READONLY flag for regions For readonly memory regions and rom devices in romd_mode, we make use of the KVM_MEM_READONLY. A slot that uses KVM_MEM_READONLY can be read from and code can execute from the region, but writes will exit to qemu. For rom devices with !romd_mode, we force the slot to be removed so reads or writes to the region will exit to qemu. (Note that a memory region in this state is not executable within kvm.) v7: * Update for readable =3D> romd_mode rename (5f9a5ea1) Signed-off-by: Jordan Justen Reviewed-by: Xiao Guangrong (v4) Reviewed-by: Paolo Bonzini (v5) Message-id: 1369816047-16384-4-git-send-email-jordan.l.justen@intel.c= om Signed-off-by: Anthony Liguori Any hints or patches welcome. :) Regards, Andreas --=20 SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 N=FCrnberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imend=F6rffer; HRB 16746 AG N=FCrnbe= rg