[systemd-devel] Systemd failed to create /init.scope under systemd-nspawn

[An Liu]

Hi,
I'm playing systemd-nspawn, and something interesting happens.
Try 1: host CentOS 8 Stream, systemd-nspawn to Debian Trixie
everything goes well.

Try 2: host CentOS 8 Stream , kvm guest CentOS 8 Stream
a: in guest systemd-nspawn to Debian Trixie , nspawn is OK to start without
—boot
b: in guest systemd-nspawn to Debian Trixie with --boot, nspawn failed
nspawn failed due to failed to create /init.scope

Try 3: host Debian bookworm, kvm guest CenOS 8 Stream, nspawn to Trixie
nspawn OK for whatever --boot present or not

Can someone explain what lead to the different behavior, Can we manage to
fix it to make
if so, what should we do. say, at the host side or at the kvm guest side?


Try 4: host centos 8 stream, kvm guest centos 8 stream, starts with the
same rootfs above but in pod man, this time systemd could start as
 pid 1


Thanks

Liu An
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/systemd-devel/attachments/20250508/aa473c8c/attachment.htm>