Changes

[<b>--force</b>] [<b>--skip-fsck</b>][<b>--skip-remount</b>]</p></td></tr>

[<b>--skip-fsck</b>] [<b>--skip-remount</b>]</p> </td></tr>

<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><td width="7%"> <p><b>vzctl</b></p></td><td width="2%"></td><td width="80%"> <p>[<i>flags</i>] <b>snapshot-delete</b> <i>CTID</i> <b>--id</b><i>uuid</i></p> </td></tr>

reserved for OpenVZ internal purposes. A numeric ID shouldnot be more than <b>2147483644</b>.</p>

if not set by <b>ViERBOSEVERBOSE</b> parameter.</p>

[<b>--cpumask&nbsp;</b><i>cpus</i>|<b>auto</b>|<b>all</b>][<b>--nodemask&nbsp;</b><i>nodes</i>|<b>all</b>]

<b>auto</b> | <b>all</b></p>

<p style="margin-left:22%;">sets Sets list of allowed CPUs for

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>

==== Netfilter (iptables ) control parameters ==== <p style="margin-left:11%;"><b>--netfilter&nbsp;disabled</b>|<b>stateless</b>|<b>stateful</b>|<b>full</b></p> <p style="margin-left:22%;">Restrict access tonetfilter/iptables modules for a container. This optionreplaces obsoleted <b>--iptables</b>.</p> <p style="margin-left:22%; margin-top: 1em">Note thatchanging this parameter requires container restart, soconsider using <b>--setmode</b> option.</p> <p style="margin-left:22%; margin-top: 1em">The followingarguments can be used: <b><br>&bull; disabled</b></p> <p style="margin-left:32%;">no modules are allowed</p> <p style="margin-left:22%;"><b>&bull; stateless</b></p> <p style="margin-left:32%;">all modules except NAT andconntracks are allowed (i.e. filter and mangle); this is thedefault</p> <p style="margin-left:22%;"><b>&bull; stateful</b></p> <p style="margin-left:32%;">all modules except NAT areallowed</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>&bull; 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:22%;"><b>Note</b> this option isobsoleted, <b>--netfilter</b> should be used instead.</p> <p style="margin-left:22%; margin-top: 1em">Allow to use the functionalityof <i>name</i> iptables module inside the container.Multiple comma-separated <i>name</i>s can be specified.</p>

specified, is ignored. </p> <p style="margin-left:22%; margin-top: 1em">By default,ploop resize is done online, i.e. on a mounted ploop. Thisis a preferred way of doing resize. Although, in a rare casea container was using lots of disk space and should now beresized to a much smaller size, an offline resize might bemore appropriate. In this case, make sure the container isstopped and unmounted and use additional<b>--offline-resize</b> option</p> <p style="margin-left:22%; margin-top: 1em">Note that such ploopresize is NOTperformed on container start, so for consistency<b>--diskspace</b> must be used together with <b>--save</b>flag.</p>

<i>CTID</i> [<b>--skip-resume</b> | <b>--must-resume</b>][<b>--skip-config</b>] <b><br>--id</b> <i>uuid</i></p>

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! </b></p> <p style="margin-left:17%; margin-top: 1em">Option<b>--skip-resume</b> is used to ignore a CT memory dump filein a snapshot, 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 givenoptionsnapshot contains CT <b>--must-resume</b> is set, absense of a memory dumpistreated as an error, it and the inability to restore from thememory dump is restoredtreated as an error rather than warning.</p> <p style="margin-left:17%; margin-top: 1em">Option option<b>--skip-config</b> is used to ignore the CT configurationfile in a snapshot, otherwisei.e. the current configuration file willcontainer be left as is stopped.</p>

<b>--diskspace</b> option and <b>--diskinodes</b> options to specify container file systemsize. Note that forsize<b>ploop</b> layout, you will not be able to change inodesvalue later. </p> <p style="margin-left:17%; margin-top: 1em">If <b>DISKSPACE </b> is not specified either in the sampleconfiguration file used for creation or in global configuration file[[Man/vz.conf.5|<b>vz.conf</b>(5)]], this <b>--diskspace</b>parameter is required for<b>ploop</b> layout.</p>

[<b>--wait</b>] [<b>--force</b>] [<b>--skip-fsck</b>][<b>--skip-remount</b>]</p>