From: Laurent Vivier <1895053@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Bug 1895053] Re: Cannot nspawn raspbian 10 [FAILED] Failed to start Journal Service.
Date: Thu, 10 Sep 2020 06:16:37 -0000 [thread overview]
Message-ID: <159971859744.20242.11094215187977520391.malone@gac.canonical.com> (raw)
In-Reply-To: 159968542073.11462.1191604929312152807.malonedeb@chaenomeles.canonical.com
Could you try with the patch attached to bug 1823790?
https://bugs.launchpad.net/qemu/+bug/1823790/+attachment/5405549/+files/SO_PEERGROUPS.patch
--
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
next prev parent reply other threads:[~2020-09-10 6:26 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-09 21:03 [Bug 1895053] [NEW] Cannot nspawn raspbian 10 [FAILED] Failed to start Journal Service Petunia
2020-09-10 6:10 ` [Bug 1895053] " Laurent Vivier
2020-09-10 6:16 ` Laurent Vivier [this message]
2020-09-10 16:18 ` Petunia
2020-09-10 16:19 ` Petunia
2020-09-10 16:50 ` Laurent Vivier
2020-09-10 17:47 ` Laurent Vivier
2020-09-10 17:51 ` Laurent Vivier
2020-09-11 7:50 ` Petunia
2020-09-11 9:20 ` Laurent Vivier
2020-09-13 10:08 ` Petunia
2020-09-13 16:36 ` Laurent Vivier
2020-09-13 20:07 ` Petunia
2020-09-14 10:18 ` Laurent Vivier
2020-09-14 22:03 ` Petunia
2020-09-16 9:42 ` Laurent Vivier
2020-09-15 1:38 ` Paul Zimmerman
2020-09-15 17:32 ` Petunia
2020-09-15 18:33 ` Petunia
2020-09-16 13:57 ` Petunia
2020-09-29 13:05 ` Petunia
2020-09-29 13:31 ` Laurent Vivier
2020-10-08 7:41 ` Petunia
2020-10-23 10:54 ` Petunia
2021-05-08 6:07 ` Thomas Huth
2021-07-08 4:17 ` Launchpad Bug Tracker
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=159971859744.20242.11094215187977520391.malone@gac.canonical.com \
--to=1895053@bugs.launchpad.net \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).