This from the bug description:
> where /mnt/cgroups/cpu/sysdefault/libvirt does not exist, but
/mnt/cgroups/cpu/libvirt/qemu (Note the difference in the path:
sysdefault is missing)
This definately should be a result of libvirt being started before
libcgroup was ready for it. (note that 'restart libvirt-bin' would not
suffice in place of 'stop libvirt-bin; star tlibvirt-bin). So I'm
hoping that there is a different cause of the failure after that.
What does an strace of fm start after libvirt-bin stop/start show?
** Changed in: libvirt (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/905565
Title:
libvirt-bin does not start kvm machine because of cgroup problem
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/905565/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
