From: Thomas Huth <1657538@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [Bug 1657538] Re: qemu 2.7.x 2.8 softmmu dont work on BE machine
Date: Fri, 20 Jan 2017 11:41:53 -0000 [thread overview]
Message-ID: <20170120114153.13992.41485.malone@soybean.canonical.com> (raw)
In-Reply-To: 20170118175149.27340.89188.malonedeb@chaenomeles.canonical.com
Something else to try: Could you please check whether you get any output
when you run "qemu-system-ppc -nographic" on your system? So we can make
sure that it is not related to GTK or something similar...
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1657538
Title:
qemu 2.7.x 2.8 softmmu dont work on BE machine
Status in QEMU:
New
Bug description:
Build on Be machine qemu 2.7.1 and 2.8 in pure softmmu (tgc) dont work on big endian hardware .
tested with ppc-softmmu,i386-softmmu,arm-softmmu same result:
with :
./qemu-system-i386
Gtk-Message: Failed to load module "overlay-scrollbar"
qemu-system-i386: Trying to execute code outside RAM or ROM at 0x000a0000
This usually means one of the following happened:
(1) You told QEMU to execute a kernel for the wrong machine type, and it crashed on startup (eg trying to run a raspberry pi kernel on a versatilepb QEMU machine)
(2) You didn't give QEMU a kernel or BIOS filename at all, and QEMU executed a ROM full of no-op instructions until it fell off the end
(3) Your guest kernel has a bug and crashed by jumping off into nowhere
This is almost always one of the first two, so check your command line and that you are using the right type of kernel for this machine.
If you think option (3) is likely then you can try debugging your guest with the -d debug options; in particular -d guest_errors will cause the log to include a dump of the guest register state at this point.
Execution cannot continue; stopping here.
I try to add the -L option with ../pc-bios/bios.bin
and have the same result.
note the ppc-softmmu and ppc64-softmmu work in kvm mode only emulated
mode have issue.
tested on my hardware a Qriq P5040 and G5 4x970MP with Ubuntu Mate 16.10
thanks
Luigi
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1657538/+subscriptions
next prev parent reply other threads:[~2017-01-20 11:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-18 17:51 [Qemu-devel] [Bug 1657538] [NEW] qemu 2.7.x 2.8 softmmu dont work on BE machine luigiburdo
2017-01-20 11:39 ` [Qemu-devel] [Bug 1657538] " Thomas Huth
2017-01-20 11:41 ` Thomas Huth [this message]
2017-01-20 15:22 ` luigiburdo
2017-01-20 15:53 ` luigiburdo
2017-02-08 14:30 ` Cameron Kaiser
2017-02-08 15:19 ` luigiburdo
2020-02-11 14:11 ` Thomas Huth
2020-05-12 10:06 ` Thomas Huth
2020-05-13 4:17 ` Launchpad Bug Tracker
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=20170120114153.13992.41485.malone@soybean.canonical.com \
--to=1657538@bugs.launchpad.net \
--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.