Bug#1081847: qemu-armel: can't run busybox:armel on riscv64

[Simon McVittie]

Package: qemu-user
Version: 1:9.0.2+ds-2
Severity: normal
User: debian-***@lists.debian.org
Usertags: riscv64
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 riscv64, the result indicates that the qemu-armel in qemu-user:riscv64

648s qemu-armel: /usr/bin/busybox: Unable to find a guest_base to satisfy all guest address mapping requirements
648s 00000000-ffffffff

I don't know whether this is specific to busybox, or whether the qemu-armel
in qemu-user:riscv64 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/2598

Post by Simon McVittie
On riscv64, the result indicates that the qemu-armel in qemu-user:riscv64

648s qemu-armel: /usr/bin/busybox: Unable to find a guest_base to satisfy all guest address mapping requirements
648s 00000000-ffffffff

Seems to be another upstream issue, - 32bit targets fails this
way on riscv64.

/mjt