Apologize for the self-reply, but upgrading to dbus-1.8.6 seems to have fixed the cgroup trimming issue. However, systemd-machined still gets a sigterm within a minute or two after a VM starts.
For what it's worth, throwing a loop in bash that calls machinectl every 10 seconds will keep systemd-machined running indefinitely and avoid any cgroup trimming of active virtual machines: while true; do machinectl; sleep 10; done Should systemd-machined remain running whenever a VM or container is running? -- Major Hayden On Nov 4, 2014, at 08:38, Major Hayden <ma...@mhtx.net> wrote: > I'm currently running systemd 216 on Fedora 21 and I've found an issue where > systemd-machined stops running and cgroups are trimmed from the scope of > running qemu virtual machines. The series of events looks like this: > > 1) OpenStack nova creates a KVM virtual machine via libvirt > 2) Libvirt registers the VM with systemd-machined, cgroups appear > 3) 0-300 seconds pass > 4) systemd-machined gets a sigterm and stops > 5) cgroups are trimmed for running virtual machines > > The cgroup trimming is a disaster because it removes devices.allow and > devices.deny ACL's for the running virtual machine. > > Here is a snippet of the systemd journal with two virtual machines running. > You'll see that systemd-machined gets a sigterm and stops: > > > https://gist.github.com/major/2d76cbf0d0de0d62ce3f > > > Shortly after systemd-machined goes offline, the cgroups are removed. > Rebooting the hypervisor, rebooting a virtual machine, or building a new > virtual machine will cause systemd-machined to start again but it will stop > shortly afterwards. > > I'm running libvirt 1.2.9 and systemd 216 on Linux 3.16.7. Thanks in advance > for your help. _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel