Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.bugs.dist > #1212998
| From | Simon McVittie <smcv@debian.org> |
|---|---|
| Newsgroups | linux.debian.bugs.dist |
| Subject | Bug#1081847: qemu-armel: can't run busybox:armel on riscv64 |
| Date | 2024-09-15 17:00 +0200 |
| Message-ID | <JmYTf-crW4-5@gated-at.bofh.it> (permalink) |
| Organization | linux.* mail to news gateway |
Package: qemu-user
Version: 1:9.0.2+ds-2
Severity: normal
User: debian-riscv@lists.debian.org
Usertags: riscv64
X-Debbugs-Cc: debian-riscv@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
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
Back to linux.debian.bugs.dist | Previous | Next — Next in thread | Find similar | Unroll thread
Bug#1081847: qemu-armel: can't run busybox:armel on riscv64 Simon McVittie <smcv@debian.org> - 2024-09-15 17:00 +0200 Bug#1081847: qemu-armel: can't run busybox:armel on riscv64 Michael Tokarev <mjt@tls.msk.ru> - 2024-09-27 11:50 +0200
csiph-web