Ubuntu
cgmanager package

  1. Bug #1392176
  2. Comment #61

Comment 61 for bug 1392176

Revision history for this message
bugproxy (bugproxy) wrote : Comment bridged from LTC Bugzilla

------- Comment From <email address hidden> 2016-06-18 09:49 EDT-------
(In reply to comment #77)
> "LXC cases, like docker and KVM" - did you mean non-lxc cases?
>
> xenial by default should now be using libpam-cgfs, should not be using
> cgmanager, and should not be creating cpusets.

Thanks for the info. However what I cares is the docker/KVM case. For example, when I created docker on xenial 16.04, the container process will still be added into /sys/fs/cgroup/cpuset/docker; When creating KVM, the KVM process will be added into sub cpuset cgroup as well. As a result, the issue can still impact those tasks.

For the above, is it already covered(on higher xenial version) or does it need more consideration?

Regards,
- Simon