On 05/05/2016 11:56 AM, Michal Privoznik wrote: > Fron c3bd0019c0e on instead of creating the following path for > cgroups: > > /sys/fs/cgroupX/$name.libvirt-$driver > > we generate rather more verbose one: > > /sys/fs/cgroupX/$driver-$id-$name.libvirt-$driver > > where $name is optional and included iff contains allowed chars. > See original commit for more reasoning. Now, problem with the > original commit is that we are unable to start any LXC domain > after it. Because when starting LXC container, the CGroup layout > is created by our lxc_controller process and then detected and > validated by libvirtd. The validation is done by trying to match > detected layout against all the possible patterns for cgroup > paths that we've ever had. And the commit in question forgot to > update this part of the code. > > Signed-off-by: Michal Privoznik <mprivozn@xxxxxxxxxx> > --- > > I am really surprised how long this bug went unnoticed. Is > anybody using LXC? When pushed, it should be backported to > 1.3.2+. FWIW libvirt.git without this patch (and with f24 libvirt 1.3.2 package) my containers start fine, and as part of the upstream bug cleanup I did a handful of lxc testing. So I don't think the failure is quite as unconditional as you suggest - Cole -- libvir-list mailing list libvir-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvir-list