Public bug reported: Hi, I'm using nspawn and asked the question @systemd-devel. They redirected me to you, guessing that nspawn calls a syscall or ioctl qemu isnt aware of and can't implement properly? They were like: "Sorry, that's not my department." ^^
Maybe you can reproduce the issue or help me investigating whats wrong or put the ball right back into their court? :D Testscript: wget https://downloads.raspberrypi.org/raspios_lite_armhf_latest -o r.zip unzip r.zip LOOP=$(losetup --show -Pf *raspios-buster-armhf-lite.img) mount ${LOOP}p2 /mnt mount ${LOOP}p1 /mnt/boot systemd-nspawn --bind /usr/bin/qemu-arm-static --boot --directory=/mnt -- systemd.log_level=debug Output: see attachment System: uname -a Linux MArch 5.8.7-arch1-1 #1 SMP PREEMPT Sat, 05 Sep 2020 12:31:32 +0000 x86_64 GNU/Linux qemu-arm-static --version qemu-arm version 5.1.0 systemd-nspawn --version systemd 246 (246.4-1-arch) +PAM +AUDIT -SELINUX -IMA -APPARMOR +SMACK -SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +ZSTD +SECCOMP +BLKID +ELFUTILS +KMOD +IDN2 -IDN +PCRE2 default-hierarchy=hybrid ** Affects: qemu Importance: Undecided Status: New ** Attachment added: "log.txt" https://bugs.launchpad.net/bugs/1895053/+attachment/5409190/+files/log.txt ** Description changed: Hi, I'm using nspawn and asked the question @systemd-devel. They redirected me to you, guessing that nspawn calls a syscall or ioctl qemu isnt aware of and can't implement properly? They were like: "Sorry, that's not my department." ^^ - Maybe you can reproduce the issue or help me investigating whats wrong or put the ball right back into their court? :D -  - From: "chiasa.men" <chiasa....@web.de> - To: systemd-de...@lists.freedesktop.org - Date: 09.09.20 14:20 - (cf. https://github.com/systemd/systemd/issues/16975) + Maybe you can reproduce the issue or help me investigating whats wrong + or put the ball right back into their court? :D Testscript: wget https://downloads.raspberrypi.org/raspios_lite_armhf_latest -o r.zip unzip r.zip LOOP=$(losetup --show -Pf *raspios-buster-armhf-lite.img) mount ${LOOP}p2 /mnt mount ${LOOP}p1 /mnt/boot systemd-nspawn --bind /usr/bin/qemu-arm-static --boot --directory=/mnt -- systemd.log_level=debug - Output: see attachment System: uname -a - Linux MArch 5.8.7-arch1-1 #1 SMP PREEMPT Sat, 05 Sep 2020 12:31:32 +0000 + Linux MArch 5.8.7-arch1-1 #1 SMP PREEMPT Sat, 05 Sep 2020 12:31:32 +0000 x86_64 GNU/Linux - systemd-nspawn --version + systemd-nspawn --version systemd 246 (246.4-1-arch) - +PAM +AUDIT -SELINUX -IMA -APPARMOR +SMACK -SYSVINIT +UTMP +LIBCRYPTSETUP - +GCRYPT +GNUTLS +ACL +XZ +LZ4 +ZSTD +SECCOMP +BLKID +ELFUTILS +KMOD +IDN2 -IDN + +PAM +AUDIT -SELINUX -IMA -APPARMOR +SMACK -SYSVINIT +UTMP +LIBCRYPTSETUP + +GCRYPT +GNUTLS +ACL +XZ +LZ4 +ZSTD +SECCOMP +BLKID +ELFUTILS +KMOD +IDN2 -IDN +PCRE2 default-hierarchy=hybrid ** Description changed: Hi, I'm using nspawn and asked the question @systemd-devel. They redirected me to you, guessing that nspawn calls a syscall or ioctl qemu isnt aware of and can't implement properly? They were like: "Sorry, that's not my department." ^^ Maybe you can reproduce the issue or help me investigating whats wrong or put the ball right back into their court? :D Testscript: wget https://downloads.raspberrypi.org/raspios_lite_armhf_latest -o r.zip unzip r.zip LOOP=$(losetup --show -Pf *raspios-buster-armhf-lite.img) mount ${LOOP}p2 /mnt mount ${LOOP}p1 /mnt/boot systemd-nspawn --bind /usr/bin/qemu-arm-static --boot --directory=/mnt -- systemd.log_level=debug Output: see attachment System: uname -a Linux MArch 5.8.7-arch1-1 #1 SMP PREEMPT Sat, 05 Sep 2020 12:31:32 +0000 x86_64 GNU/Linux + qemu-arm-static --version + qemu-arm version 5.1.0 + systemd-nspawn --version systemd 246 (246.4-1-arch) +PAM +AUDIT -SELINUX -IMA -APPARMOR +SMACK -SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +ZSTD +SECCOMP +BLKID +ELFUTILS +KMOD +IDN2 -IDN +PCRE2 default-hierarchy=hybrid -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1895053 Title: Cannot nspawn raspbian 10 [FAILED] Failed to start Journal Service. Status in QEMU: New Bug description: Hi, I'm using nspawn and asked the question @systemd-devel. They redirected me to you, guessing that nspawn calls a syscall or ioctl qemu isnt aware of and can't implement properly? They were like: "Sorry, that's not my department." ^^ Maybe you can reproduce the issue or help me investigating whats wrong or put the ball right back into their court? :D Testscript: wget https://downloads.raspberrypi.org/raspios_lite_armhf_latest -o r.zip unzip r.zip LOOP=$(losetup --show -Pf *raspios-buster-armhf-lite.img) mount ${LOOP}p2 /mnt mount ${LOOP}p1 /mnt/boot systemd-nspawn --bind /usr/bin/qemu-arm-static --boot --directory=/mnt -- systemd.log_level=debug Output: see attachment System: uname -a Linux MArch 5.8.7-arch1-1 #1 SMP PREEMPT Sat, 05 Sep 2020 12:31:32 +0000 x86_64 GNU/Linux qemu-arm-static --version qemu-arm version 5.1.0 systemd-nspawn --version systemd 246 (246.4-1-arch) +PAM +AUDIT -SELINUX -IMA -APPARMOR +SMACK -SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +ZSTD +SECCOMP +BLKID +ELFUTILS +KMOD +IDN2 -IDN +PCRE2 default-hierarchy=hybrid To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1895053/+subscriptions
