libvirtd fails to start qemu domains after having its cgroup changed

Bug #827538 reported by Serge Hallyn
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
libvirt (Ubuntu)
Won't Fix
Undecided
Unassigned

Bug Description

If libvirtd's cgroup is changed after it starts, then it fails from then on when trying to start a kvm domain.

The workaround is to 'stop libvirt-bin; start libvirt-bin' and hope cgred does not re-classify it.

Revision history for this message
Serge Hallyn (serge-hallyn) wrote :

While I think it is feasible to fix this, I don't think the patch would be acceptable upstream.

I'm going to mark it wontfix (because i do see it as a bug) and open a bug against cgroup-bin about the broken libvirt-cgroup-wait.conf, so at least libvirt wont' start until init has been reclassified to /sysdefault.

Changed in libvirt (Ubuntu):
status: New → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.