* [Qemu-devel] [Bug 1657538] [NEW] qemu 2.7.x 2.8 softmmu dont work on BE machine
@ 2017-01-18 17:51 luigiburdo
2017-01-20 11:39 ` [Qemu-devel] [Bug 1657538] " Thomas Huth
` (8 more replies)
0 siblings, 9 replies; 10+ messages in thread
From: luigiburdo @ 2017-01-18 17:51 UTC (permalink / raw)
To: qemu-devel
Public bug reported:
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
** Affects: qemu
Importance: Undecided
Status: New
--
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
^ permalink raw reply [flat|nested] 10+ messages in thread
* [Qemu-devel] [Bug 1657538] Re: qemu 2.7.x 2.8 softmmu dont work on BE machine
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 ` Thomas Huth
2017-01-20 11:41 ` Thomas Huth
` (7 subsequent siblings)
8 siblings, 0 replies; 10+ messages in thread
From: Thomas Huth @ 2017-01-20 11:39 UTC (permalink / raw)
To: qemu-devel
I can not reproduce this issue. QEMU 2.8 works fine here on a POWER8 big
endian host (running RHEL7). Can you still run older versions of QEMU
that used to work for you in the past, to check whether it is QEMU or
whether it is Ubuntu 16.10 that is causing the trouble here? Could you
please also post the full output of the "configure" run on your system?
--
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
^ permalink raw reply [flat|nested] 10+ messages in thread
* [Qemu-devel] [Bug 1657538] Re: qemu 2.7.x 2.8 softmmu dont work on BE machine
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
2017-01-20 15:22 ` luigiburdo
` (6 subsequent siblings)
8 siblings, 0 replies; 10+ messages in thread
From: Thomas Huth @ 2017-01-20 11:41 UTC (permalink / raw)
To: qemu-devel
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
^ permalink raw reply [flat|nested] 10+ messages in thread
* [Qemu-devel] [Bug 1657538] Re: qemu 2.7.x 2.8 softmmu dont work on BE machine
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
@ 2017-01-20 15:22 ` luigiburdo
2017-01-20 15:53 ` luigiburdo
` (5 subsequent siblings)
8 siblings, 0 replies; 10+ messages in thread
From: luigiburdo @ 2017-01-20 15:22 UTC (permalink / raw)
To: qemu-devel
Hi Thomas,
here the configure .. i made a clean one just with the target for have fastest build
will report soon the result with the nographic just the time of build
src/qemu$ ./configure --target-list=i386-softmmu,ppc-softmmu,ppc64-softmmu
Install prefix /usr/local
BIOS directory /usr/local/share/qemu
binary directory /usr/local/bin
library directory /usr/local/lib
module directory /usr/local/lib/qemu
libexec directory /usr/local/libexec
include directory /usr/local/include
config directory /usr/local/etc
local state directory /usr/local/var
Manual directory /usr/local/share/man
ELF interp prefix /usr/gnemul/qemu-%M
Source path /home/amigaone/src/qemu
C compiler cc
Host C compiler cc
C++ compiler c++
Objective-C compiler clang
ARFLAGS rv
CFLAGS -O2 -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2 -g
QEMU_CFLAGS -I/usr/include/pixman-1 -Werror -DHAS_LIBSSH2_SFTP_FSYNC -pthread -I/usr/include/glib-2.0 -I/usr/lib/powerpc-linux-gnu/glib-2.0/include -D_GNU_SOURCE -I/usr/include/ncursesw -m32 -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -Wstrict-prototypes -Wredundant-decls -Wall -Wundef -Wwrite-strings -Wmissing-prototypes -fno-strict-aliasing -fno-common -fwrapv -Wendif-labels -Wno-shift-negative-value -Wmissing-include-dirs -Wempty-body -Wnested-externs -Wformat-security -Wformat-y2k -Winit-self -Wignored-qualifiers -Wold-style-declaration -Wold-style-definition -Wtype-limits -fstack-protector-strong -I/usr/local/include/libpng12 -I/usr/local/include/cacard -I/usr/include/nss -I/usr/include/nspr -I/usr/include/libusb-1.0
LDFLAGS -Wl,--warn-common -m32 -g
make make
install install
python python -B
smbd /usr/sbin/smbd
module support no
host CPU ppc
host big endian yes
target list i386-softmmu ppc-softmmu ppc64-softmmu
tcg debug enabled no
gprof enabled no
sparse enabled no
strip binaries yes
profiler no
static build no
pixman system
SDL support yes (1.2.15)
GTK support yes (2.24.30)
GTK GL support no
VTE support no
TLS priority NORMAL
GNUTLS support no
GNUTLS rnd no
libgcrypt yes
libgcrypt kdf yes
nettle no
nettle kdf no
libtasn1 no
curses support yes
virgl support yes
curl support yes
mingw32 support no
Audio drivers oss
Block whitelist (rw)
Block whitelist (ro)
VirtFS support yes
VNC support yes
VNC SASL support yes
VNC JPEG support yes
VNC PNG support yes
xen support no
brlapi support yes
bluez support yes
Documentation yes
PIE no
vde support no
netmap support no
Linux AIO support yes
ATTR/XATTR support yes
Install blobs yes
KVM support yes
COLO support yes
RDMA support yes
TCG interpreter no
fdt support yes
preadv support yes
fdatasync yes
madvise yes
posix_madvise yes
libcap-ng support yes
vhost-net support yes
vhost-scsi support yes
vhost-vsock support yes
Trace backends log
spice support no
rbd support yes
xfsctl support yes
smartcard support yes
libusb yes
usb net redir yes
OpenGL support yes
OpenGL dmabufs yes
libiscsi support yes
libnfs support yes
build guest agent yes
QGA VSS support no
QGA w32 disk info no
QGA MSI support no
seccomp support yes
coroutine backend ucontext
coroutine pool yes
debug stack usage no
GlusterFS support no
Archipelago support no
gcov gcov
gcov enabled no
TPM support yes
libssh2 support yes
TPM passthrough no
QOM debugging yes
lzo support yes
snappy support yes
bzip2 support yes
NUMA host support yes
tcmalloc support no
jemalloc support no
avx2 optimization no
replication support yes
--
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
^ permalink raw reply [flat|nested] 10+ messages in thread
* [Qemu-devel] [Bug 1657538] Re: qemu 2.7.x 2.8 softmmu dont work on BE machine
2017-01-18 17:51 [Qemu-devel] [Bug 1657538] [NEW] qemu 2.7.x 2.8 softmmu dont work on BE machine luigiburdo
` (2 preceding siblings ...)
2017-01-20 15:22 ` luigiburdo
@ 2017-01-20 15:53 ` luigiburdo
2017-02-08 14:30 ` Cameron Kaiser
` (4 subsequent siblings)
8 siblings, 0 replies; 10+ messages in thread
From: luigiburdo @ 2017-01-20 15:53 UTC (permalink / raw)
To: qemu-devel
i386-softmmu:
./qemu-system-i386 -nographic
qemu-system-i386: Trying to execute code outside RAM or ROM at 0x000a0000
This usually means one of the following happened: and so and so
./qemu-system-ppc -nographic
nothing happen ... no exit on console .
on 2.6.2 i have:
qemu-system-ppc -nographic
>> =============================================================
>> OpenBIOS 1.1 [Apr 18 2016 08:20]
>> Configuration device id QEMU version 1 machine id 2
>> CPUs: 1
>> Memory: 128M
>> UUID: 00000000-0000-0000-0000-000000000000
>> CPU type PowerPC,750
milliseconds isn't unique.
Welcome to OpenBIOS v1.1 built on Apr 18 2016 08:20
Trying hd:,\\:tbxi...
Trying hd:,\ppc\bootinfo.txt...
Trying hd:,%BOOT...
note the 2.6.2 work, before on 2.6.1 i had the same issue of 2.7 and 2.8
--
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
^ permalink raw reply [flat|nested] 10+ messages in thread
* [Qemu-devel] [Bug 1657538] Re: qemu 2.7.x 2.8 softmmu dont work on BE machine
2017-01-18 17:51 [Qemu-devel] [Bug 1657538] [NEW] qemu 2.7.x 2.8 softmmu dont work on BE machine luigiburdo
` (3 preceding siblings ...)
2017-01-20 15:53 ` luigiburdo
@ 2017-02-08 14:30 ` Cameron Kaiser
2017-02-08 15:19 ` luigiburdo
` (3 subsequent siblings)
8 siblings, 0 replies; 10+ messages in thread
From: Cameron Kaiser @ 2017-02-08 14:30 UTC (permalink / raw)
To: qemu-devel
I can reproduce the same problem on 2.7.0 on a PowerPC G5 for the x86,
x86_64 and ppc softmmu targets (minus the Gtk problem, since I use this
ported to Cocoa). As with Luigi this seems to be a regression from
2.6.2. There is no change with -nographic.
See also: https://bugzilla.redhat.com/show_bug.cgi?id=1332449
The commenter indicates several BE issues were detected. I have not yet
heard from him regarding his patches or whether they were upstreamed
here.
** Bug watch added: Red Hat Bugzilla #1332449
https://bugzilla.redhat.com/show_bug.cgi?id=1332449
--
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
^ permalink raw reply [flat|nested] 10+ messages in thread
* [Qemu-devel] [Bug 1657538] Re: qemu 2.7.x 2.8 softmmu dont work on BE machine
2017-01-18 17:51 [Qemu-devel] [Bug 1657538] [NEW] qemu 2.7.x 2.8 softmmu dont work on BE machine luigiburdo
` (4 preceding siblings ...)
2017-02-08 14:30 ` Cameron Kaiser
@ 2017-02-08 15:19 ` luigiburdo
2020-02-11 14:11 ` Thomas Huth
` (2 subsequent siblings)
8 siblings, 0 replies; 10+ messages in thread
From: luigiburdo @ 2017-02-08 15:19 UTC (permalink / raw)
To: qemu-devel
Oh my gosh the great Cameron Kaiser :)
--
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
^ permalink raw reply [flat|nested] 10+ messages in thread
* [Bug 1657538] Re: qemu 2.7.x 2.8 softmmu dont work on BE machine
2017-01-18 17:51 [Qemu-devel] [Bug 1657538] [NEW] qemu 2.7.x 2.8 softmmu dont work on BE machine luigiburdo
` (5 preceding siblings ...)
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
8 siblings, 0 replies; 10+ messages in thread
From: Thomas Huth @ 2020-02-11 14:11 UTC (permalink / raw)
To: qemu-devel
Looking through old bug tickets ... can you still reproduce the issue
with the latest version of QEMU (v4.2) and a more recent Linux
distribution?
** Changed in: qemu
Status: New => Incomplete
--
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:
Incomplete
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
^ permalink raw reply [flat|nested] 10+ messages in thread
* [Bug 1657538] Re: qemu 2.7.x 2.8 softmmu dont work on BE machine
2017-01-18 17:51 [Qemu-devel] [Bug 1657538] [NEW] qemu 2.7.x 2.8 softmmu dont work on BE machine luigiburdo
` (6 preceding siblings ...)
2020-02-11 14:11 ` Thomas Huth
@ 2020-05-12 10:06 ` Thomas Huth
2020-05-13 4:17 ` Launchpad Bug Tracker
8 siblings, 0 replies; 10+ messages in thread
From: Thomas Huth @ 2020-05-12 10:06 UTC (permalink / raw)
To: qemu-devel
** Bug watch removed: Red Hat Bugzilla #1332449
https://bugzilla.redhat.com/show_bug.cgi?id=1332449
--
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:
Incomplete
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
^ permalink raw reply [flat|nested] 10+ messages in thread
* [Bug 1657538] Re: qemu 2.7.x 2.8 softmmu dont work on BE machine
2017-01-18 17:51 [Qemu-devel] [Bug 1657538] [NEW] qemu 2.7.x 2.8 softmmu dont work on BE machine luigiburdo
` (7 preceding siblings ...)
2020-05-12 10:06 ` Thomas Huth
@ 2020-05-13 4:17 ` Launchpad Bug Tracker
8 siblings, 0 replies; 10+ messages in thread
From: Launchpad Bug Tracker @ 2020-05-13 4:17 UTC (permalink / raw)
To: qemu-devel
[Expired for QEMU because there has been no activity for 60 days.]
** Changed in: qemu
Status: Incomplete => Expired
--
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:
Expired
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
^ permalink raw reply [flat|nested] 10+ messages in thread
end of thread, other threads:[~2020-05-13 4:26 UTC | newest]
Thread overview: 10+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
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
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
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.