Thank you for looking into this. I have attached the journal of one shutdown and boot. It seems like during boot, everything happens in the correct order. As you pointed out, this is as expected due to the "After" parameter in the service-files.
However, as you can see from the shutdown.txt file, blkdeactivate gets called before libvirt-guests. It is entirely possible that the issue is not due to libvirt-guests, but I'm struggling to understand what is causing this. The host is set up with software raid where root, boot and swap are on primary partitions, and the remaining space is a LVM volume group used by the libvirt guests. The volume group is also containing the volume mounted on /var/lib/libvirt/qemu/save. The errors from suspending the second and third guest is probably due to the root file system being full, as this is not dimensioned to be able to hold all the suspend data. ** Attachment added: "journal.txt" https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1832859/+attachment/5271194/+files/journal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1832859 Title: during shutdown libvirt-guests gets stopped after file system unmount To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1832859/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
