From: Laszlo Ersek <lersek@redhat.com>
To: Duane Voth <duanev@gmail.com>
Cc: Bug 1180970 <1180970@bugs.launchpad.net>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [Bug 1180970] [NEW] qemu: fatal: Trying to execute code outside RAM or ROM; worked in 1.4.0, fails in 1.4.92
Date: Fri, 17 May 2013 00:44:32 +0200 [thread overview]
Message-ID: <51956150.2010603@redhat.com> (raw)
In-Reply-To: <CABpPS=ps1n6M-+UG9=zN_c3AGv+EJ9Jp9uazrQ7X++r7urLGjw@mail.gmail.com>
On 05/17/13 00:32, Duane Voth wrote:
> Ha, I thought kvm was on by default. Apparently not, qemu -enable-kvm
> avoids this issue.
>
> Yes, 0x0000000100000000 with RIP=00000000ffffffe4 is quite suspicious,
> especially after the splash screen has been displayed. Off in the weeds
> comes to mind - so I'm guessing corrupted or incorrectly mapped guest
> memory?
>
> The git tree is where? (I just grabbed the tarball)
Instructions are on the same wiki page, http://wiki.qemu.org/Download
Laszlo
next prev parent reply other threads:[~2013-05-16 22:42 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-16 19:58 [Qemu-devel] [Bug 1180970] [NEW] qemu: fatal: Trying to execute code outside RAM or ROM; worked in 1.4.0, fails in 1.4.92 Duane Voth
2013-05-16 20:01 ` [Qemu-devel] [Bug 1180970] " Duane Voth
2013-05-16 21:46 ` [Qemu-devel] [Bug 1180970] [NEW] " Laszlo Ersek
2013-05-16 22:32 ` Duane Voth
2013-05-16 22:44 ` Laszlo Ersek [this message]
2013-05-17 10:20 ` Paolo Bonzini
2013-05-17 15:35 ` [Qemu-devel] [Bug 1180970] " Launchpad Bug Tracker
2013-05-17 15:39 ` Marco Trevisan (Treviño)
2013-05-17 20:03 ` Duane Voth
2013-05-21 18:16 ` Duane Voth
2013-05-24 21:37 ` Laszlo Ersek
2013-05-24 21:49 ` Laszlo Ersek
2013-05-29 19:05 ` Duane Voth
2016-09-28 14:28 ` T. Huth
2016-09-28 14:59 ` Duane Voth
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=51956150.2010603@redhat.com \
--to=lersek@redhat.com \
--cc=1180970@bugs.launchpad.net \
--cc=duanev@gmail.com \
--cc=qemu-devel@nongnu.org \
/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.