Comment # 16 on bug 1174365 from Klaus Mueller

As I already wrote in Comment 4, my workaround / solution is, to kill libvirtd
after it auto started the defined VMs (ExecStartPost). 

This takes care, that on shutdown of the host, no matter how it is performed,
the VM can't be suspended by libvirtd (because it's not running any more)
before systemd starts to stop the service using the defined ExecStop process.

The question here is: who or what (and how) informs a running libvirtd
(completely outside of the defined shutdown process of systemd) about the
shutdown of the host, which in turn suspends the VMs belonging to this libvirtd
instance? And why can't this be disabled?

BTW: If the VM contains a passed through PCIe card (something like a PCIe
network card), e.g., the suspend isn't executed (it gives an error), because
VMs containing passed through devices can't be suspended - those VMs are
therefore always processed via the subsequent service definition and not
before!

Another bad thing (that's maybe the primary point, why it is a problem to
suspend VMs at all): If the suspended VM is restarted again, the VM proceeds
with the wrong time (it is the time it has been shutdown). I found no way to
fix the time on resume.