<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW --- - when a unit file is removed, systemd abandons running processes" href="https://bugs.freedesktop.org/show_bug.cgi?id=65973#c2">Comment # 2</a> on <a class="bz_bug_link bz_status_NEW " title="NEW --- - when a unit file is removed, systemd abandons running processes" href="https://bugs.freedesktop.org/show_bug.cgi?id=65973">bug 65973</a> from <a class="email" href="mailto:zbyszek@in.waw.pl" title="Zbigniew Jedrzejewski-Szmek <zbyszek@in.waw.pl>"> Zbigniew Jedrzejewski-Szmek</a> <pre>(In reply to <a href="show_bug.cgi?id=65973#c1">comment #1</a>) > Hmm, my guess is that libvirt moved qemu into its own cgroup and hence > outside of the control of systemd. Of course, libvirt really should have > killed the VM when it was uninstalled... It seems that everything is still in the same cgroup (this is after restarting libvirtd.service). CGroup: name=systemd:/system/libvirtd.service ├─ 1278 /sbin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/default.conf ├─ 2593 /usr/bin/qemu-system-x86_64 -machine accel=kvm ... └─26765 /usr/sbin/libvirtd > So, not sure we can do anything about this, except filing a bug against > libvirt to fix its scriptlets? It's on purpose, so that running VM are not interrupted by libvirtd restarts. Tying the VMs to libvirtd lifecycle would be a huge drawback. The service file has: KillMode=process</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> <li>You are the assignee for the bug.</li> </ul> </body> </html>