Changes

* == Limitations ==The following vzctl commands are not working at all:* <code>quotaon</code>/<code>quotaoff</code>/<code>quotainit</code> (vzquota-specific)* <code>convert</code>, convert<code>compact</code>, <code>snapshot*</code> (ploop-specific)* <code>console</code> (need a virtual /dev/console, /dev/ttyN device)* <code>enter</code>, <code>exec </code> and <code>runscript are not expected to work. Checkpoint </code> (need pidns entering support)* <code>chkpnt</code>, <code>restore is also not possible</code> (currently need OpenVZ-kernel-specific checkpointing, but upstream support for that is progressing very fast (See [http://criucrui.org for details/ CRIU] will be supported later).

The following commands have severe limitations:* Networking <code>stop</code>. A container can be stopped from inside (say if one is available through connected to CT over ssh) in case the switches --netdev_add, --netif_add, and their respective deletion counterpartsunderlying kernel supports rebooting a PID namespace (> 3. IP mode networking (--ipadd / --ipdel4) . Using vzctl, the "stop" command is currently not supported, unless accompanied by the --fast switch, which will simply forceably kill all processes in the container.

* Stopping a container once one Software that depend on information supplied by the proc filesystem may not work correctly, since there is logged in is possible, in case the underlying kernel supports rebooting not a PID namespace (> 3.4)full solution for full /proc virtualization. Using vzctlFor instance, the "stop" command /proc/stat is not supportedyet virtualized, unless accompanied by the --fast switch, which and top will simply forceably kill all processes in the containershow distorted values.

* Software that depend on information supplied by the proc filesystem may not work correctly, since there is not a full solution for full /proc virtualization. For instance, /proc/stat is not yet virtualized, and top will show distorted values. * Setting resources like --physpages and --cpuunits work, but there their effect is dependent on what the current kernel supports, through the cgroups subsystem. When a particular cgroup file is present, it will be used. Currently, vzctl will search for the following files:

$ ./configure --with-cgroup--without-ploop