Changes

Jump to: navigation, search

Vzctl for upstream kernel

403 bytes removed, 15:41, 3 April 2013
removed some limitations (3.8 has pid ns entering)
'''This article describes using OpenVZ tool vzctl as an alternative to LXC tools.'''
 
Since [[Download/vzctl/4.0|version 4.0]], vzctl tool can be used with upstream (non-OpenVZ) Linux kernels (that essentially means any recent 3.x kernel). At the moment, it provides just basic functionality.
It is currently possible to create and start a container with the same steps as one would use for a normal OpenVZ container. Other features may be present with limited functionality, while some are not present at all. We appreciate all bug reports, please file to [http://bugzilla.openvz.org/enter_bug.cgi?component=vzctl bugzilla].
{{Warning|Running vzctl on upstream kernels is considered an experimental feature. See [[#Limitatons]] below.}}
== Installation ==
* <code>convert</code>, <code>compact</code>, <code>snapshot*</code> (ploop-specific)
* <code>console</code> (needs a virtual /dev/console, /dev/ttyN device)
* <code>enter</code>, <code>exec</code> and <code>runscript</code> (need pidns entering support)
* <code>chkpnt</code>, <code>restore</code> (currently need OpenVZ-kernel-specific checkpointing, [http://criu.org/ CRIU] will be supported later)
 
The following commands have severe limitations:
* <code>stop</code>. A container can be stopped from inside (say if one is connected to CT over ssh) in case the underlying kernel supports rebooting a PID namespace (> 3.4). Using vzctl, the "stop" command is not supported, unless accompanied by the --fast switch, which will simply forceably kill all processes in the container.
The following binaries are not ported to work on top of upstream kernel:
Retrieved from "https://wiki.openvz.org/Special:MobileDiff/13597"

Navigation menu