https://bugzilla.novell.com/show_bug.cgi?id=852005 https://bugzilla.novell.com/show_bug.cgi?id=852005#c11 James Fehlig <jfehlig@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO InfoProvider| |systemd-maintainers@suse.de --- Comment #11 from James Fehlig <jfehlig@suse.com> 2014-01-28 18:49:17 UTC --- (In reply to comment #10)
Do you want to reboot/halt your server and this should be propagated to the clients?
Well, not really propagated to the guests, but a chance for libvirt-guests to do whatever the user has configured it to do on host shutdown/startup.
Then this seems to more a problem of the libvirt-guests.service which is part of the package libvirt-client.
The problem is that systemd has killed off the guests by the time libvirt-guests runs. When libvirt starts a qemu guest, it uses the CreateMachine dbus call to create a scope for the guest. So each qemu guest is running inside a scope, which is not connected by any dependencies to either systemd-machine.service or libvirt-guests.service. When the host is shutdown, the scopes will be stopped in parallel to running libvirt-guests, and depending on timing, guests may killed with SIGTERM before libvirt-guests is able to process them. The libvirt community is looking for ways to solve this problem. One idea was to inject a 'After=libvirt-guests.service' when creating the scope, e.g. diff --git a/src/util/virsystemd.c b/src/util/virsystemd.c index 503fff7..3243d35 100644 --- a/src/util/virsystemd.c +++ b/src/util/virsystemd.c @@ -243,8 +243,9 @@ int virSystemdCreateMachine(const char *name, iscontainer ? "container" : "vm", (unsigned int)pidleader, rootdir ? rootdir : "", - 1, "Slice", "s", - slicename) < 0) + 2, + "Slice", "s", slicename, + "After", "s", "libvirt-guests.service") < 0) goto cleanup; ret = 0; but that caused the CreateMachine dbus call to fail. So it is not clear how to describe the dependency when creating the scope. This is where some advice from the systemd community would be helpful, but there has been no response to Cole's question on systemd-devel http://lists.freedesktop.org/archives/systemd-devel/2013-December/015534.htm... Since upstream has been silent, I'm hoping to get some advice from internal systemd experts on how to proceed. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.