From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:34670) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Ufzxo-0005YI-My for qemu-devel@nongnu.org; Fri, 24 May 2013 17:55:58 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Ufzxe-00024y-OS for qemu-devel@nongnu.org; Fri, 24 May 2013 17:55:52 -0400 Received: from indium.canonical.com ([91.189.90.7]:59227) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Ufzxe-00024o-J3 for qemu-devel@nongnu.org; Fri, 24 May 2013 17:55:42 -0400 Received: from loganberry.canonical.com ([91.189.90.37]) by indium.canonical.com with esmtp (Exim 4.71 #1 (Debian)) id 1Ufzxd-0003G3-HI for ; Fri, 24 May 2013 21:55:41 +0000 Received: from loganberry.canonical.com (localhost [127.0.0.1]) by loganberry.canonical.com (Postfix) with ESMTP id 8199E2E807F for ; Fri, 24 May 2013 21:55:41 +0000 (UTC) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Date: Fri, 24 May 2013 21:49:18 -0000 From: Laszlo Ersek <1180970@bugs.launchpad.net> Sender: bounces@canonical.com References: <20130516195843.983.69688.malonedeb@soybean.canonical.com> Message-Id: <20130524214918.7396.56903.malone@chaenomeles.canonical.com> Errors-To: bounces@canonical.com Subject: [Qemu-devel] [Bug 1180970] Re: qemu: fatal: Trying to execute code outside RAM or ROM; worked in 1.4.0, fails in 1.4.92 Reply-To: Bug 1180970 <1180970@bugs.launchpad.net> List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org Proposed patch: http://thread.gmane.org/gmane.comp.emulators.qemu/213023 -- = You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1180970 Title: qemu: fatal: Trying to execute code outside RAM or ROM; worked in 1.4.0, fails in 1.4.92 Status in QEMU: In Progress Bug description: I'm using qemu to run and debug the EDK2 uEFI environment. OVMF is being built out of the EDK2 tree I've checked out (r14367). (Reproducing all this could be tedious so I am available for debugging/testing.) qemu 1.4.0 was able to execute this guest environment with no trouble, qemu 1.4.92 however issues an error message and aborts. The command line I use to start qemu is: $ /usr/local/bin/qemu-system-x86_64 -m 1024 -bios OVMF.fd -monitor stdio 1.4.92 gives the following register dump: QEMU 1.4.92 monitor - type 'help' for more information (qemu) qemu: fatal: Trying to execute code outside RAM or ROM at 0x000000= 0100000000 RAX=3D000000003e084da8 RBX=3D000000003e084868 RCX=3D0000000000000000 RDX= =3D000000003e084f00 RSI=3D0000000000000001 RDI=3D000000003e085000 RBP=3D000000003e084708 RSP= =3D000000003fac8510 R8 =3D0000000000000000 R9 =3D000000003e14c3e3 R10=3D0000000000000033 R11= =3D00000000000000d3 R12=3D000000003e0848a0 R13=3D0000000000000000 R14=3D0000000000000000 R15= =3D0000000000000000 RIP=3D00000000ffffffe4 RFL=3D00000046 [---Z-P-] CPL=3D0 II=3D0 A20=3D1 SM= M=3D0 HLT=3D0 ES =3D0008 0000000000000000 ffffffff 00cf9300 DPL=3D0 DS [-WA] CS =3D0028 0000000000000000 ffffffff 00af9b00 DPL=3D0 CS64 [-RA] SS =3D0008 0000000000000000 ffffffff 00cf9300 DPL=3D0 DS [-WA] DS =3D0008 0000000000000000 ffffffff 00cf9300 DPL=3D0 DS [-WA] FS =3D0008 0000000000000000 ffffffff 00cf9300 DPL=3D0 DS [-WA] GS =3D0008 0000000000000000 ffffffff 00cf9300 DPL=3D0 DS [-WA] LDT=3D0000 0000000000000000 0000ffff 00008200 DPL=3D0 LDT TR =3D0000 0000000000000000 0000ffff 00008b00 DPL=3D0 TSS64-busy GDT=3D 000000003fa50e98 0000003f IDT=3D 000000003f9d6e20 00000fff CR0=3D80000033 CR2=3D0000000000000000 CR3=3D000000003fa67000 CR4=3D000006= 68 ... = Questions: 1) Is this problem relevant? (is full backward compatability to be suppo= rted?) 2) Are there new guest execution controls in 1.4.9x that might cause this? 3) If #2, can they be disabled by a qemu command line switch? 4) If not #2, in what qemu source file specifically can I find the logic = causing the abort? (help me help you :) 5) If guest memory is corrupted or improperly mapped, how can I keep qemu= alive to examime/dump guest memory? To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1180970/+subscriptions