Quoting Johannes Schauer Marin Rodrigues (2022-05-16 16:49:12) > Then reboot the thing just to be sure and then run: > > $ mmdebstrap --arch=arm64 --variant=apt unstable /dev/null > ... > I: extracting archives... > done > I: installing essential packages... > done > qemu: uncaught target signal 11 (Segmentation fault) - core dumped > E: run_chroot failed: E: env --unset=APT_CONFIG --unset=TMPDIR > /usr/sbin/chrod > W: listening on child socket failed: > I: removing tempdir /tmp/mmdebstrap.nBUnpBBsox... > E: mmdebstrap failed to run > root@hostname:/home/user# dpkg -l | grep qemu > ii qemu-guest-agent 1:7.0+dfsg-7 > amd64 t > ii qemu-user-static 1:7.0+dfsg-7 > amd64 ) > > Now you have a reproducer that installed qemu-user-static on a real system > and not a chroot and we observe the same effect.
oh and just to make sure that this is not an mmdebstrap thing we can also use
debootstrap on our freshly installed system and observe the same problem:
root@hostname:/home/user# debootstrap --foreign --arch arm64 unstable
debian-unstable
...
I: Extracting libsmartcols1...
I: Extracting libuuid1...
I: Extracting mount...
I: Extracting util-linux...
I: Extracting util-linux-extra...
I: Extracting libxxhash0...
I: Extracting liblzma5...
I: Extracting zlib1g...
root@hostname:/home/user# chroot debian-unstable
qemu: uncaught target signal 11 (Segmentation fault) - core dumped
Segmentation fault
root@hostname:/home/user#
So now you have a reproducer where we don't even do anything special anymore.
We use debian-installer to create the Debian system and we use debootstrap to
trigger the problem.
Thanks!
cheers, josch
signature.asc
Description: signature
