So far as I can tell, the current behavior assumes that lxc has full control over the cgroups involved in supporting the new lxc container, including each cgroup/dir in the lxc.cgroup.dir path. This does not play well with systems/situations in which a dedicated part of the cgroup tree set up for lxc containers. In fact, it breaks them.
Do I need to patch my builds of lxc to avoid this behavior?
It would be helpful if some of the lxc devs would comment on this.