Your message dated Wed, 9 Oct 2024 21:59:16 +0300
with message-id <[email protected]>
and subject line Re: Bug#1081847: qemu-armel: can't run busybox:armel on riscv64
has caused the Debian Bug report #1081847,
regarding qemu-armel: can't run busybox:armel on riscv64
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1081847: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1081847
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: qemu-user
Version: 1:9.0.2+ds-2
Severity: normal
User: [email protected]
Usertags: riscv64
X-Debbugs-Cc: [email protected]
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
can't run busybox:armel:
> 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
--- End Message ---
--- Begin Message ---
On 15.09.2024 17:55, Simon McVittie wrote:
Package: qemu-user
Version: 1:9.0.2+ds-2
Severity: normal
User: [email protected]
Usertags: riscv64
X-Debbugs-Cc: [email protected]
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
can't run busybox:armel:
648s qemu-armel: /usr/bin/busybox: Unable to find a guest_base to satisfy all
guest address mapping requirements
648s 00000000-ffffffff
This turned out to be a bug in riscv64 kernel.
Fixed in 6.10.11-1.
https://git.kernel.org/pub/scm/linux/kernel/git/stable/stable-queue.git/tree/releases/6.10.10/riscv-mm-do-not-restrict-mmap-address-based-on-hint.patch
/mjt
--- End Message ---
