Hmm, I can recreate the issue myself. So I thought - yeah onto bisect ! But I fail to get a self built /usr/bin/qemu-arm-static into this. I wanted to see if 5.1 from git would work and then bisect from there. But no matter what I try it keeps breaking on the same error.
/me starts to wonder where in the chain of KVM host, qemu-arm-static in the guest, systemd-nspawn in the guest that binary really would need to be. At least $ sudo apt remove qemu-user-static $ sudo systemd-nspawn -D /var/lib/machines/armhf-focal -M armhf-focal -b Spawning container armhf-focal on /var/lib/machines/armhf-focal. Press ^] three times within 1s to kill container. execv(/usr/lib/systemd/systemd, /lib/systemd/systemd, /sbin/init) failed: Exec format error Container armhf-focal failed with error code 1. So the qemu-static binfmt is used as I'd have assumed. Init is systemd which is: $ sudo file /var/lib/machines/armhf-focal/lib/systemd/systemd /var/lib/machines/armhf-focal/lib/systemd/systemd: ELF 32-bit LSB shared object, ARM, EABI5 version 1 (SYSV), dynamically linked, interpreter /lib/ld-linux-armhf.so.3, BuildID[sha1]=3ca7712fe69ab99bb55585c35af762a2491fc856, for GNU/Linux 3.2.0, stripped But even if I delete ALL /usr/bin/qemu* binaries it still does the same. $ sudo systemd-nspawn -D /var/lib/machines/armhf-focal -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 <groovy>. Caught <SEGV>, dumped core as pid 3. Exiting PID 1... Container armhf-focal failed with error code 255. The target in /var/lib/machines/armhf-focal/ only has core dumps of qemu_systemd and bash completions. It can't come from there either. I beg your pardon for not being a nspawn+mmbootstrap expert but WTH where would I need to place my new qemu binary that I need to test ? @Rafael - if you see where I'm blocking my own insight please feel free to speak up and let me know :-) -- 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
