Bug#1081849: qemu-i386: can't run busybox:i386 on ppc64el: Segmentation fault

[Simon McVittie]

Package: qemu-user
Version: 1:9.0.2+ds-2+b1
Severity: normal
User: debian-***@lists.debian.org
Usertags: ppc64el
X-Debbugs-Cc: debian-***@lists.debian.org

The new cross-exe-wrapper package in src:architecture-properties runs
binaries from a foreign architecture, either directly or via qemu-user.
Its autopkgtest uses busybox from each release architecture (specifically
the `busybox true` and `busybox echo` applets) as a smoke-test to see
whether this works as intended.

On ppc64el, the result indicates that the qemu-i386 in qemu-user:ppc64el

137s qemu: uncaught target signal 11 (Segmentation fault) - core dumped

I don't know whether this is specific to busybox, or whether the qemu-i386
in qemu-user:ppc64el doesn't work more generally.

architecture-properties (>= 0.2.2) works around this by skipping its
self-test on architecture pairs where qemu-$arch doesn't run successfully.

smcv

[Michael Tokarev]

Control: forwarded -1 https://gitlab.com/qemu-project/qemu/-/issues/2597

Post by Simon McVittie
Package: qemu-user
Version: 1:9.0.2+ds-2+b1
Severity: normal
Usertags: ppc64el
The new cross-exe-wrapper package in src:architecture-properties runs
binaries from a foreign architecture, either directly or via qemu-user.
Its autopkgtest uses busybox from each release architecture (specifically
the `busybox true` and `busybox echo` applets) as a smoke-test to see
whether this works as intended.
On ppc64el, the result indicates that the qemu-i386 in qemu-user:ppc64el

137s qemu: uncaught target signal 11 (Segmentation fault) - core dumped

This is an upstream issue, introduced between 8.2 and 9.0.

For fun, it is not an issue anymore for debian, since it only happens when
the qemu binary is linked dynamically, and since 9.1 version, I dropped
dynamically linked version. So it doesn't occur on debian anymore.

So I guess this bug report can be closed now.

/mjt