On Do, 08.05.25 00:09, An Liu (sourceo...@gmail.com) wrote: > 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
Note that we as upstream have no idea what systemd versions these distros "debian trixie" or "centos 8 stream" refer to, hence it's very hard to help here. My educated guess is that this is a cgroupv1 vs. cgroupv2 issue. We do not systematically test combinations of payload and host with the two distinct apis, and there have been reports that things are broken in that regard. And there's little interest to fix that, because cgroupv1 is no longer supported by systemd anyway. Lennart -- Lennart Poettering, Berlin
