Public bug reported: This is somewhat similar but different from https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1887606
The following bug does not occur with the upstream version qemu-5.1.0-rc3 built from it source code. How to reproduce (as root) on amd64 host running Ubuntu: apt-get install -t groovy qemu-user-static (the Ubuntu package version is 1:5.0-5ubuntu4) mmdebstrap --components="main restricted universe multiverse" --variant=standard --architectures=armhf focal /var/lib/machines/armhf- focal http://ports.ubuntu.com/ubuntu-ports/ systemd-nspawn -D /var/lib/machines/armhf-focal -b # 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. Afain, with qemu-5.1.0-rc3, the container starts fine. ** Affects: qemu (Ubuntu) Importance: Undecided Status: New ** Tags: groovy -- 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