Package: qemu-user-static Version: 1:2.4+dfsg-2 Severity: wishlist Dear Maintainer,
I recently discovered systemd-nspawn and machinectl. After working through various bugs (try to use at least systemd 226 on the host) I started playing with emulated builds, but a full boot didn't work. Note that calling systemd-nspawn *without* -b does produce a working shell. # cd /var/lib/machines # arch=arm64 # qemu-debootstrap --arch=$arch jessie jessie_$arch < snip lots of output> # systemd-nspawn -bD jessie_$arch Spawning container jessie_arm64 on /var/lib/machines/jessie_arm64. Press ^] three times within 1s to kill container. Failed to create directory /var/lib/machines/jessie_arm64/sys/fs/selinux: Read-only file system Failed to create directory /var/lib/machines/jessie_arm64/sys/fs/selinux: Read-only file system /etc/localtime is not a symlink, not updating container timezone. qemu: Unsupported syscall: 264 qemu: Unsupported syscall: 264 qemu: Unsupported syscall: 264 qemu: Unsupported syscall: 264 qemu: Unsupported syscall: 264 qemu: Unsupported syscall: 264 qemu: Unsupported syscall: 264 qemu: Unsupported syscall: 264 qemu: Unsupported syscall: 264 qemu: Unsupported syscall: 264 qemu: Unsupported syscall: 264 qemu: Unsupported syscall: 264 qemu: Unsupported syscall: 264 qemu: Unsupported syscall: 264 qemu: Unsupported syscall: 264 qemu: Unsupported syscall: 264 qemu: Unsupported syscall: 264 qemu: Unsupported syscall: 264 qemu: Unsupported syscall: 264 systemd 215 running in system mode. (+PAM +AUDIT +SELINUX +IMA +SYSVINIT +LIBCRYPTSETUP +GCRYPT +ACL +XZ -SECCOMP -APPARMOR) Detected virtualization 'systemd-nspawn'. Detected architecture 'arm64'. Welcome to Debian GNU/Linux 8 (jessie)! Set hostname to <jessie-arm64>. qemu: Unsupported syscall: 74 Failed to allocate manager object: Function not implemented ^]^] Container jessie_arm64 terminated by signal KILL. Looking at the arm64 syscall list, 264 is sys_name_to_handle_at and 74 is sys_signalfd4. The same bug occurs with arm64, armel, armhf, mips, mipsel, ppc64el, s390s (though the syscall numbers vary of course). I did not test amd64 or i386 because my host is amd64 and I'm not aware of any way to force qemu emulation on the native architecture. It is possible that there are additional unimplemented syscalls that do not get called until after the above succeed. -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (600, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386, powerpc, arm64, armhf Kernel: Linux 4.1.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) qemu-user-static depends on no packages. Versions of packages qemu-user-static recommends: ii binfmt-support 2.1.5-1 Versions of packages qemu-user-static suggests: ii sudo 1.8.12-1 -- no debconf information
