2,253
edits
Changes
Automated import of articles *** existing text overwritten ***
<p>[<i>flags</i>] <b>start</b> <i>CTID</i> [<b>--wait</b>]
[<b>--force</b>] [<b>--skip-fsck</b>][<b>--skip-remount</b>]</p></td></tr>
<tr valign="top" align="left">
<td width="11%"></td>
<p>[<i>flags</i>] <b>restart</b> <i>CTID</i>
[<b>--wait</b>] [<b>--force</b>] [<b>--fast</b>]
[<b>--skip-fsck</b>] [<b>--skip-remount</b>]</p> </td></tr>
<tr valign="top" align="left">
<td width="11%"></td>
<p>[<i>flags</i>] <b>snapshot-switch</b> <i>CTID</i>
[<b>--skip-resume</b> | <b>--must-resume</b>] [<b>--skip-config</b>] <b>--id</b><i>uuid</i></p> </td></tr>
<tr valign="top" align="left">
<td width="11%"></td>
is set to the value of <b>VERBOSE</b> parameter in the
global configuration file [[Man/vz.conf.5|<b>vz.conf</b>(5)]], or to <b>0</b>
if not set by <b>ViERBOSEVERBOSE</b> parameter.</p>
=== Setting container parameters ===
[<b>--name </b><i>name</i>]
[<b>--description </b><i>string</i>]
[<b>--ostemplate </b><i>string</i>]
[<b>--stop-timeout </b><i>seconds</i>]
[<b>--ipadd </b><i>addr</i>]
[<b>--cpulimit </b><i>num</i>]
[<b>--cpus </b><i>num</i>]
[<b>--cpumask </b><i>cpus</i>|<b>auto</b>|<b>all</b>][<b>--nodemask </b><i>nodes</i>|<b>all</b>]
[<b>--meminfo none</b>|<i>mode</i>:<i>value</i>]
[<b>--iptables </b><i>name</i>[<b>,</b>...]]
<p style="margin-left:17%;">Add a textual description for a
container.</p>
<p style="margin-left:11%;"><b>--ostemplate</b>
<i>string</i></p>
<p style="margin-left:17%;">Sets a new value of
<b>OSTEMPLATE</b> parameter in container configuration file
[[Man/ctid.conf.5|<b>ctid.conf</b>(5)]]. Requires <b>--save</b> flag. Useful
after a change/upgrade of a distribution running inside
container, as vzctl uses the value of OSTEMPLATE to run
distribution-specific scripts.</p>
<p style="margin-left:11%;"><b>--stop-timeout</b>
<p style="margin-left:11%;"><b>--cpumask</b> <i>cpus</i> |
<b>auto</b> | <b>all</b></p>
<p style="margin-left:22%;">sets Sets list of allowed CPUs for
the container. Input format is a comma-separated list of
decimal numbers and /or ranges. Consecutively set bits are shownas two hyphen-separated decimal numbers, the smallest andlargest bit numbers set in the range. For example, if youwant the container to execute on CPUs 0, 1, 2, 7, you shouldpass <b>0-2,7</b>. Default value is <b>all</b> (thecontainer can execute on any CPU). If used with the<b>--nodemask</b> option, value of <b>auto</b> assigns allCPUs from the specified NUMA node to a container.</p> <p style="margin-left:11%;"><b>--nodemask</b> <i>nodes</i>| <b>all</b></p> <p style="margin-left:22%;">Sets list of allowed NUMA nodesfor the container. Input format is the same as for<b>--cpumask</b>. Note that <b>--nodemask</b> must be usedwith the <b>--cpumask</b> option.</p>
==== Memory output parameters ====
netfilter/iptables modules for a container. This option
replaces obsoleted <b>--iptables</b>.</p>
<p style="margin-left:22%; margin-top: 1em">Note that
changing this parameter requires container restart, so
consider using <b>--setmode</b> option.</p>
<p style="margin-left:22%; margin-top: 1em">The following
arguments can be used: <b><br>
• disabled</b></p>
<p style="margin-left:32%;">no modules are allowed</p>
<p style="margin-left:22%;"><b>• stateless</b></p>
<p style="margin-left:32%;">all modules except NAT and
conntracks are allowed (i.e. filter and mangle); this is the
default</p>
<p style="margin-left:22%;"><b>• stateful</b></p>
<p style="margin-left:32%;">all modules except NAT are
allowed</p>
<table width="100%" border="0" rules="none" frame="void"
cellspacing="0" cellpadding="0">
<tr valign="top" align="left">
<td width="22%"></td>
<td width="9%">
<p><b>• full</b></p></td>
<td width="1%"></td>
<td width="36%">
<p>all modules are allowed</p></td>
<td width="32%">
</td></tr>
</table>
<p style="margin-left:11%;"><b>--iptables</b>
<p style="margin-left:11%;"><b>snapshot-switch</b>
<i>CTID</i> [<b>--skip-resume</b> | <b>--must-resume</b>] [<b>--skip-config</b>]<b><br>--id</b> <i>uuid</i></p>
<p style="margin-left:17%;">Switches the container to a
snapshot identified by <i>uuid</i>, restoring its filesystem state, configuration (if available) and its runningstate (if available). </p> <p style="margin-left:17%; margin-top: 1em"><b>Note that the currentstate of a container (including its file systemcontainer state and its configuration file system state ) is lost! If</b></p> <p style="margin-left:17%; margin-top: 1em">Optionsnapshot contains <b>--skip-resume</b> is used to ignore a CT memory dumpfilein a snapshot, and as a result the container will end up beingin a stopped state (same as if a snapshot has been takenwith <b>--skip-suspend</b>).</p> <p style="margin-left:17%; margin-top: 1em">If option<b>--skipmust-resume</b> is not specifiedset, container absense of a memory dump isrestoredtreated as an error, otherwise it and the inability to restore from thememory dump is stoppedtreated as an error rather than warning. If snapshot contains CT</p> configuration file, and <p style="margin-left:17%; margin-top: 1em">Option option <b>--skip-config</b> is notused to ignore the CT configurationspecifiedfile in a snapshot, container i.e. the current configuration file willbe left as is restored.</p>
<p style="margin-left:11%;"><b>snapshot-delete</b>
<p style="margin-left:11%;"><b>start</b> <i>CTID</i>
[<b>--wait</b>] [<b>--force</b>] [<b>--skip-fsck</b>][<b>--skip-remount</b>]</p>
<p style="margin-left:17%;">Mounts (if necessary) and
<b>--skip-fsck</b> to skip fsck for ploop-based container
filesystem (this option is used by vz initscript).</p>
<p style="margin-left:17%; margin-top: 1em">By default, if
a container to be started happens to be already mounted, it
is unmounted and mounted again. This behavior can be turned
off by using <b>--skip-remount</b> flag.</p>
<p style="margin-left:17%; margin-top: 1em">Note that this
