Comment # 21 on bug 1174365 from
(In reply to Klaus Mueller from comment #20)
> I'm now testing automation with a VM which most probably can be paused /
> saved without any issues on shutdown of the host. That's pretty easy for me
> as the existing automation had just to be modified a little bit (remove the
> killing of libvirtd after startup and adding the guest-set-time instead).

If this works out for you, and you're hesitant to raise the issue upstream,
maybe just close the bug. Configurable VM state handling on host shutdown when
using unprivileged libvirtd is really an upstream feature request IMO.


You are receiving this mail because: