Control: reassign -1 qemu-user-static 1:5.0-5 Control: notforwarded -1 Dear Maintainers of qemu-user-static,
I originally submitted the below cited report to the Debian systemd package. Michael told me to report this to the upstream. Then I was told that I should report this to qemu by the upstream at https://github.com/systemd/systemd/issues/16359#issuecomment-654322002 So I reassign this to the Debian qemu-user-static package. As far as I see, for the amd64 Debian Bullseye host, arm64, ppc64 (big endian) work fine as guest systemd-nspawn containers. armel armhf and powerpc failed to work as guest systemd-nspawn containers. All of the above guests use Debian Bullseye. In addition, Debian buster mips (32-bit big endian) works fine as a guest. Best regards, Ryutaroh Matsumoto From: Michael Biebl <bi...@debian.org> Subject: Re: Bug#964289: systemd-container: armhf countainer cannot be started on amd64 host Date: Sun, 5 Jul 2020 09:59:10 +0200 > Am 05.07.20 um 07:48 schrieb Ryutaroh Matsumoto: >> Package: systemd-container >> Version: 245.6-1 >> Severity: normal >> >> Dear Maintainer, >> >> I installed >> # dpkg-query -W | grep qemu-user-static >> qemu-user-static 1:5.0-5 >> >> Then I built a root directory as >> >> # mmdebstrap --components="main contrib non-free" --architectures=armhf >> --variant=important bullseye /var/lib/machines/armhf-bullseye >> >> Then >> # systemd-nspawn -D /var/lib/machines/armhf-bullseye -a >> works fine. >> >> But I got the following error and could not start the container... >> # systemd-nspawn -D /var/lib/machines/armhf-bullseye -b >> Spawning container armhf-bullseye on /var/lib/machines/armhf-bullseye. >> Press ^] three times within 1s to kill container. >> systemd 245.6-1 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 Debian GNU/Linux bullseye/sid! >> >> Set hostname to <armhf-bullseye>. >> Failed to enqueue loopback interface start request: Operation not supported >> Caught <SEGV>, core dump failed (child 3, code=killed, status=11/SEGV). >> Exiting PID 1... >> Container armhf-bullseye failed with error code 255. >> >> Best regards, Ryutaroh Matsumoto >> > > Hm, I'm not sure if this is supported and supposed to work. > But you can ask upstream. > > Regards, > Michael > >