Bug#1050045: systemd-nspawn fails to start systemd >=253 in QEMU-emulated container

2023-08-23 Thread Michael Tokarev
Ok. This is in qemu linux-user/syscall.c: #define CLONE_IGNORED_FLAGS \ (CLONE_DETACHED | CLONE_IO) /* Flags for fork which we can implement within QEMU itself */ #define CLONE_OPTIONAL_FORK_FLAGS \ (CLONE_SETTLS | CLONE_PARENT_SETTID | CLONE_PIDFD | \

Bug#1050045: systemd-nspawn fails to start systemd >=253 in QEMU-emulated container

2023-08-23 Thread Michael Tokarev
23.08.2023 15:37, Michael Biebl wrote: [...] systemd upstream argued in https://github.com/systemd/systemd/issues/28901 that the error is in QEMUs incomplete syscall emulation. Thus tentatively reassigning the bug report. Well, this is not exactly helpful. Which syscall is failing or

Bug#1050045: systemd-nspawn fails to start systemd >=253 in QEMU-emulated container

2023-08-23 Thread Michael Biebl
Control: reassign -1 qemu-user-static Control: affects -1 systemd On Sat, 19 Aug 2023 01:22:42 +0200 MichaIng wrote: Package: systemd Version: 254.1-2 since systemd 253 was merged into Sid/unstable and Trixie/testing, systemd-nspawn fails to boot Sid and Trixie containers with foreign

Bug#1050045: systemd-nspawn fails to start systemd >=253 in QEMU-emulated container

2023-08-18 Thread MichaIng
Package: systemd Version: 254.1-2 since systemd 253 was merged into Sid/unstable and Trixie/testing, systemd-nspawn fails to boot Sid and Trixie containers with foreign architectures via qemu-user-static and binfmt: --- Spawning container rootfs on /root/rootfs. Press Ctrl-] three times