On Mon, Sep 29, 2014 at 02:48:34PM +0530, Kashyap Chamarthy wrote: > On Mon, Sep 29, 2014 at 08:17:11AM +0200, Guido Günther wrote: > > On Mon, Sep 29, 2014 at 07:12:29AM +0530, Kashyap Chamarthy wrote: > > > Applied it: > > > > > > $ git log | head -5 > > > commit da0a33c3f286ff69b910bc2a84e9ec3a844e3ce8 > > > Author: Guido Günther <agx@xxxxxxxxxxx> > > > Date: Thu Sep 25 14:30:42 2014 +0200 > > > > > > qemu: use systemd's TerminateMachine to kill all processes > > > > > > And tested (by building RPMs, restarting libvirtd and attempting to > > > start the guest again, still no luck: > > > > > > $ sudo systemctl restart libvirtd > > > $ sudo systemctl daemon-reload > > > > Did you reboot in between? > > No, I didn't. I realized rebooting might help solve the issue as this > was related to systemd, but didn't wanted to, as it's my main laptop, > and have several other things that I'm processing. > > > The patch fixes the _stopping_ of the vm. Once the vm is in the state > > you describe the patch won't help. > > Ah. > > > > > An alternative to rebooting is to remove related processes manually, see: > > > > http://bugs.debian.org/761521 > > I don't see x2d<$vmname>.scope under machine.slice (mostly as the > guests are all off, but I can't start them anyhow): > > $ tree /sys/fs/cgroup/cpuset/machine.slice Please check /sys/fs/cgroup/systemd/machine.slice/ . Does machinectl list anything? -- Guido -- libvir-list mailing list libvir-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvir-list