On 2021-08-02 11:16, hal wrote:
>
<snip>
> I've been running KVM/QEMU/Virt-Manager on Devuan for many years with
3-4 VMs and haven't had any issues directly related to Devuan. It's not
my intent to bash systemd but it's worth mentioning that I've had many
other issues with Debian based hypervisors over the past few years (50+
VMs across several hypervisors) that involve systemd when reviewing logs
post-mortem. Hypervisors will sometimes not reboot. Even when trying to
un-stick with Magic SysRq. The console will just show systemd errors
instead. Likewise, when systems do reboot, sometimes they inexplicably
stop booting and need to have the power button hit. Another time,
OpenSSH would not work due to /var/run/sshd missing during boot. Another
issue involved systemd and a LUKS encrypted partition. Another time was
missing LVM devices. This happens across systems of varying age so
hardware issues are kind of ruled out. The issues keep getting more
frequent and odd as months go by. It's like these systems have regressed
to what L
> inux was in 1995.
>
> I would strongly suggest running your virtualization on Devuan. The
simplicity and stability is currently unmatched in my experience.
>
<snip>
I would like to tell that in my experience the Debian KVM+QEMU+libvirt
also started to suffer from some misbehaviour then I first time heard
about systemd. I did not took a challenge and migrated to DEVUAN.

May be worth mentioning, that in my setup I use three virtual disks for
one guest, which is not well supported by current apparmor
configuration, so I took a shortcut: I switch the apparmour off
(disable) during snapshots create/commit for back up script. Sure I
better learn about the apparmor configuration, but not this time.

Cheers
Andrzej