It seems very strange. systemd-nspawn should have nothing to do with
whether it is running in vm or what is the host of the vm. Try to see
what systemd-detect-virt see's in each case anyway.
For debugging, you can enter the nspawn container --boot and see if
cgroup fs is mounted the same in al
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 system
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 gues
