@paelzer, I got below. This seems to mean that #LP1887606 is fixed in 1:4.2-3ubuntu6.4~ppa1 while #LP1890881 remains.
By the way, debian Bullseye 1:5.1+dfsg-0exp1 worked fine as far as I see. Preparing to unpack .../qemu-user-static_1%3a4.2-3ubuntu6.4~ppa1_amd64.deb ... Unpacking qemu-user-static (1:4.2-3ubuntu6.4~ppa1) over (1:4.2-3ubuntu6.3) ... Setting up qemu-user-static (1:4.2-3ubuntu6.4~ppa1) ... Processing triggers for man-db (2.9.1-1) ... root@ryutaroh-CFSZ6-1L:/home/ryutaroh# systemctl restart binfmt-support root@ryutaroh-CFSZ6-1L:/home/ryutaroh# systemd-nspawn -M armhf-focal -b Spawning container armhf-focal on /var/lib/machines/armhf-focal. Press ^] three times within 1s to kill container. systemd 245.4-4ubuntu3 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD +IDN2 -IDN +PCRE2 default-hierarchy=hybrid) Detected virtualization systemd-nspawn. Detected architecture arm. Welcome to Ubuntu 20.04 LTS! Set hostname to <armhf-focal>. Caught <SEGV>, dumped core as pid 3. Exiting PID 1... Container armhf-focal failed with error code 255. root@ryutaroh-CFSZ6-1L:/home/ryutaroh# -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890881 Title: qemu-user-static 1:5.0-5ubuntu4 in groovy does not start armhf container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1890881/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs