Quoting Martin Pitt ([email protected]): > > Note that when i start up a vivid vm without cgmanager installed, cpuset is > > still mounted and login sessions get a cpuset cgroup: > > 2:cpuset:/user.slice/user-1000.slice/session-1.scope > > Note that this is by request of Stèphane, it's an ubuntu specific patch > to make user LXC containers work under systemd. I didn't follow the > discussion here in depth and I don't know much about the cgroup > internals -- I just wanted to say let me know if the above is unintended > and systemd should stop configuring the cpuset controller for user > sessions (then user LXC would need to get some adjustments for that too, > though)
Cpusets are not *required* for lxc. Perhaps we should in fact default to only providing name=systemd, devices and freezer cgroups for users? We'd want to very widely advertise how to enable other cgroups. Currently lxc would fail this way, but we could teach it to ignore inability to create cgroups which aren't required. (This isn't as simple as it seems, since using the keyword "all" for controllers would no longer work, but it's doable) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1392176 Title: mounts cgroups unconditionally which causes undesired effects with cpu hotplug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cgmanager/+bug/1392176/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
