#781775 qemu-x86_64-static segfaults on Raspberry Pi when starting debian wheezy guest

#781775#5
Date:
2015-04-02 20:25:43 UTC
From:
To:
I've got debian wheezy (7.5) for x86_64 installed on an internal disk
(installed with debootstrap), and a Raspberry Pi running debian wheezy
(7.8) with the x86_64 disk, in an external enclosure, connected to one
of the RPi USB ports. I'm trying to run the x86_64 system in a VM from
the RPi using qemu and chroot, but it dies with a "Segmentation fault"
error:

# chroot /mnt
qemu: uncaught target signal 11 (Segmentation fault) - core dumped
Segmentation fault
#

I've tried running other programs from the x86_64 disk, sometimes with
success (eg <code>yes</code> works as expected, but <code>bash</bash>
crashes with the same error. I've tried other shells, with the same
result. The configuration files are unchanged from installation in
both host and guest systems; I can send them if required.

I've included keystrokes captured by a "script" session, which
includes details of how I tried to start the VM, and what was mounted
and how, and how much memory (physical and swap) are available, and
the installed versions of relevant software (including bash).

I suspected that the error could be with bash, but other shells fail
with the same error; it doesn't seem to be a memory issue, because the
"free" command says there's still at least 80MB free, and swap hasn't
been used at all.

If you need any more information, please let me know.

Danny Mitchell

#781775#10
Date:
2015-04-02 22:16:11 UTC
From:
To:
02.04.2015 23:25, Danny Mitchell wrote:

This is the same as #703825 (http://bugs.debian.org/703825) which boils
down to, as Peter Maydell puts it, «That is just the usual "x86 linux-user
isn't really supported"».  It is a general issue, not related to platform.

More, qemu-user completely lacks multi-threaded support, and almost all
current executables use multi-threaded primitives in one way or another.

Thanks,

/mjt

#781775#15
Date:
2025-08-12 12:02:10 UTC
From:
To:
Version: 1:10.0.0+ds-1

This issue has been fixed completely in 10.0 version, by removing
64bit guest on 32bit host support.

I guess this particular issue has been fixed for real too, long time
ago, since qemu-x86_64 was used on other 32bit platforms before, but
now it's history anyway.

Closing this bug report now.

Thanks,

/mjt