Changes

Jump to: navigation, search

Vzctl for upstream kernel

83 bytes added, 13:57, 10 September 2012
assorted small fixes and formatting
Since 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.
 
{{Warning| Running vzctl on upstream kernels is considered an experimental feature.}}
 
With this release vzctl tool is expected to run with Upstream Linux kernels. 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 functionality may be present with limited functionality, while some are not present at all.
== Limitations ==
* <code>quotaon</code>/<code>quotaoff</code>/<code>quotainit</code> (vzquota-specific)
* <code>convert</code>, <code>compact</code>, <code>snapshot*</code> (ploop-specific)
* <code>console</code> (need 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://crui.org/ CRIU] will be supported later)
=== Resource management ===
Setting resources like <code>--physpages ram</code> and <code>--cpuunits </code> 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:
* cpu.cfs_quota_us
* cpu.shares
=== Compile ===
Upstream support is not enabled by default. To build it into vzctl, one needs to specify the <code>--with-cgroup</code> switch to <code>configure</code>. Also, it makes sense to add <code>--without-ploop </code> (unless you want ploop compiled it) because otherwise you will need ploop lib headers.
$ ./configure --with-cgroup --without-ploop

Navigation menu