Public bug reported:
Qemu seems to be missing syscalls 370 and 355 when running qemu usermode
arm. These are used by systemd or some similar new package. This can be
detected by creating an debian sid armhf with qemu debootstrap. When the
system is launched with "systemd-nspawn -bD sid-arm" this happens
(newest git as of today):
pawning container sid-arm on /home/jpakkane/qemutest/sid-arm.
Press ^] three times within 1s to kill container.
Failed to create directory /home/jpakkane/qemutest/sid-arm//sys/fs/selinux:
Read-only file system
Failed to create directory /home/jpakkane/qemutest/sid-arm//sys/fs/selinux:
Read-only file system
/etc/localtime is not a symlink, not updating container timezone.
qemu: Unsupported syscall: 370
qemu: Unsupported syscall: 370
qemu: Unsupported syscall: 370
qemu: Unsupported syscall: 370
qemu: Unsupported syscall: 370
qemu: Unsupported syscall: 370
qemu: Unsupported syscall: 370
qemu: Unsupported syscall: 370
qemu: Unsupported syscall: 370
qemu: Unsupported syscall: 370
qemu: Unsupported syscall: 370
qemu: Unsupported syscall: 384
qemu: Unsupported syscall: 370
qemu: Unsupported syscall: 370
qemu: Unsupported syscall: 370
qemu: Unsupported syscall: 370
qemu: Unsupported syscall: 370
qemu: Unsupported syscall: 370
qemu: Unsupported syscall: 370
qemu: Unsupported syscall: 370
qemu: Unsupported syscall: 370
systemd 221 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK
+SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT -GNUTLS +ACL +XZ -LZ4 +SECCOMP +BLKID
-ELFUTILS +KMOD -IDN)
Detected virtualization systemd-nspawn.
Detected architecture arm.
Welcome to Debian GNU/Linux stretch/sid!
Set hostname to <manos>.
qemu: Unsupported syscall: 355
Failed to allocate manager object: Function not implemented
[!!!!!!] Failed to allocate manager object, freezing.
** Affects: qemu
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1470170
Title:
Unsupported syscalls 370 and 355
Status in QEMU:
New
Bug description:
Qemu seems to be missing syscalls 370 and 355 when running qemu
usermode arm. These are used by systemd or some similar new package.
This can be detected by creating an debian sid armhf with qemu
debootstrap. When the system is launched with "systemd-nspawn -bD sid-
arm" this happens (newest git as of today):
pawning container sid-arm on /home/jpakkane/qemutest/sid-arm.
Press ^] three times within 1s to kill container.
Failed to create directory /home/jpakkane/qemutest/sid-arm//sys/fs/selinux:
Read-only file system
Failed to create directory /home/jpakkane/qemutest/sid-arm//sys/fs/selinux:
Read-only file system
/etc/localtime is not a symlink, not updating container timezone.
qemu: Unsupported syscall: 370
qemu: Unsupported syscall: 370
qemu: Unsupported syscall: 370
qemu: Unsupported syscall: 370
qemu: Unsupported syscall: 370
qemu: Unsupported syscall: 370
qemu: Unsupported syscall: 370
qemu: Unsupported syscall: 370
qemu: Unsupported syscall: 370
qemu: Unsupported syscall: 370
qemu: Unsupported syscall: 370
qemu: Unsupported syscall: 384
qemu: Unsupported syscall: 370
qemu: Unsupported syscall: 370
qemu: Unsupported syscall: 370
qemu: Unsupported syscall: 370
qemu: Unsupported syscall: 370
qemu: Unsupported syscall: 370
qemu: Unsupported syscall: 370
qemu: Unsupported syscall: 370
qemu: Unsupported syscall: 370
systemd 221 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR
+SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT -GNUTLS +ACL +XZ -LZ4 +SECCOMP
+BLKID -ELFUTILS +KMOD -IDN)
Detected virtualization systemd-nspawn.
Detected architecture arm.
Welcome to Debian GNU/Linux stretch/sid!
Set hostname to <manos>.
qemu: Unsupported syscall: 355
Failed to allocate manager object: Function not implemented
[!!!!!!] Failed to allocate manager object, freezing.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1470170/+subscriptions
