[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Bug 1895053] Re: Cannot nspawn raspbian 10 [FAILED] Failed to start Jou
From: |
Thomas Huth |
Subject: |
[Bug 1895053] Re: Cannot nspawn raspbian 10 [FAILED] Failed to start Journal Service. |
Date: |
Sat, 08 May 2021 06:07:02 -0000 |
The QEMU project is currently moving its bug tracking to another system.
For this we need to know which bugs are still valid and which could be
closed already. Thus we are setting the bug state to "Incomplete" now.
If the bug has already been fixed in the latest upstream version of QEMU,
then please close this ticket as "Fix released".
If it is not fixed yet and you think that this bug report here is still
valid, then you have two options:
1) If you already have an account on gitlab.com, please open a new ticket
for this problem in our new tracker here:
https://gitlab.com/qemu-project/qemu/-/issues
and then close this ticket here on Launchpad (or let it expire auto-
matically after 60 days). Please mention the URL of this bug ticket on
Launchpad in the new ticket on GitLab.
2) If you don't have an account on gitlab.com and don't intend to get
one, but still would like to keep this ticket opened, then please switch
the state back to "New" or "Confirmed" within the next 60 days (other-
wise it will get closed as "Expired"). We will then eventually migrate
the ticket automatically to the new system (but you won't be the reporter
of the bug in the new system and thus you won't get notified on changes
anymore).
Thank you and sorry for the inconvenience.
** Changed in: qemu
Status: New => Incomplete
--
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:
Incomplete
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
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [Bug 1895053] Re: Cannot nspawn raspbian 10 [FAILED] Failed to start Journal Service.,
Thomas Huth <=