[Users] Upstream kernel and vzctl updated documentation

Devon B. devon.b at virtualcomplete.com
Sat Feb 21 12:51:38 PST 2015


Is there updated documentation on vzctl with the upstream kernel?

If not, maybe we can add some to the wiki.

1. ) How does LOCAL_UID work?  Does it just add n to the container's
uid?  Is there a limit?  For example, with LOCAL_UID=100000, UID 0
(root) becomes 100000, but what about UID 100000, does it become
200000?  What about 1000000?

2.)  How to define an apparmor profile or selinux context for the container?

3.)  Has checkpointing support with CRIU advanced?

4.)  Has a list function be built in to replace the use of vzlist?

5.)  Has any implementation like fuse-procfs or lxcfs been tried for a
per-container meminfo/cpuinfo/stat?

6.)  How is --cpus implemented?  cpuset.cpus only accepts static values
as far as I know, for instance 0-1 will assign CPU 0 and CPU 1 to a
container compared to OpenVZ's dynamic vcpu allocation. How does vzctl
handle allocation?



More information about the Users mailing list