Hello Helmut and thanks for this bug report. From my testing libvirt VMs do not automatically get registered to machined (they are not listed by `systemctl list-machines`), and indeed machined, not "owning" then, doesn't seem to touch them at shutdown.
To better understand your issue here and verify this is actually a bug in Ubuntu and not a local configuration issue we need more details on how you start the affected VMs. Could you please provide a minimal set of steps to reproduce the issue from a clean Ubuntu system? I can't exclude that libvirt doesn't play well with machined in some cases, but should this behavior given by how libvirt behaves and not by how it's distributed in Ubuntu then my suggestion here is to file a bug upstream: https://gitlab.com/libvirt/libvirt/-/issues Waiting for your reply here I'm marking this bug report as Incomplete. ** Changed in: libvirt (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1939577 Title: Missing dependency in libvirt-guests.service leads sometimes to killed VMs on host shutdown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1939577/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
