594
edits
Changes
no edit summary
== NAME ==
<p style="margin-left:11%0; margin-top: 1em">vz.conf −
global OpenVZ configuration file</p>
== SYNOPSIS ==
<p style="margin-left:11%0; margin-top: 1em"><b>/etc/vz/vz.conf</b></p>
== DESCRIPTION ==
<p style="margin-left:11%;"><b>LOGFILE</b>=<i>file</i></p>
<p style="margin-left:22%;">Set location of log file,default is /var/log/vzctl.log.</p>
<p style="margin-left:11%;"><b>LOG_LEVEL</b>=<i>number</i></p>
to be loaded by <b>vz</b> initscript before loading OpenVZ
modules (which is required for iptables to work inside
containers). If not set, value of <b>IPTABLES</b> isused.</p>
<p style="margin-left:11%;"><b>VZFASTBOOT</b>=<b>yes</b>|<b>no</b></p>
initscript when restarts those containers with unclean quota
in a normal way (to recalculate/fix quotas).</p>
<p style="margin-left:11%;"><b>VE_STOP_MODE</b>=<b>suspend</b>|<b>stop</b></p>
<p style="margin-left:22%;">If the value of this parameter
is set to <b>suspend</b> or not set at all, <b>vz</b>
initscript called with <b>stop</b> argument will try to
suspend the running containers, instead of stopping them.
Suspended containers when will be restored on <b>vz
start</b>. This feature usually helps to decrease the reboot
time. If a container fails to suspend, it will be stopped
anyway.</p>
<p style="margin-left:11%;"><b>VE_PARALLEL</b>=<i>number</i></p>
<p style="margin-left:22%;">A number of containers to be
started or stopped simultaneously on node startup or
shutdown. If not specified, the number is calculated based
on amount of CPU cores. Used by the <b>vz</b>
initscript.</p>
<p style="margin-left:11%;"><b>TEMPLATE</b>=<i>directory</i></p>
directory in which all container template data are
stored.</p>
<p style="margin-left:11%;"><b>SKIP_SYSCTL_SETUP</b>=<b>yes</b></p>
<p style="margin-left:22%;">If this parameter is not
present, <b>init.d/vz start</b> sets some
<b>sysctl.conf</b>(5) parameters required or recommended by
OpenVZ (with the help of <b>vz-postinstall sysctl</b>
script), and then adds this parameter to <b>vz.conf</b>.</p>
=== Network interface parameters ===
network device list.</p>
<p style="margin-left:11%;"><b>NEIGHBOUR_DEVS</b>="<b>all</b>|<b>detect</b>|<b>list:</b><i>dev1 </i>[<i>dev2 </i>...]"</p>
<p style="margin-left:22%;">Controls on which interfaces to
add/remove ARP records for a container IP, also which
interfaces to use to query/announce ARP. </p> <p style="margin-left:22%; margin-top: 1em">If this set to<b>all</b>, an empty string, or unset, all possible networkinterfaces (i.e. the ones that are UP and doesn’t haveNOARP, SLAVE, or LOOPBACK flags) are used. This is thedefault mode.</p> <p style="margin-left:22%; margin-top: 1em">If set to<b>detect</b>, the right network interface (i.e. the one which isin the same subnet as a CT container IP) will be chosen automatically.</p> Any other <p style="margin-left:22%; margin-top: 1em">If the value restores old (as of vzctl 3.0.19 or older)behaviorstarts with <b>list:</b> prefix, when all the possible space-separated list ofinterfaces were following the prefix is used.</p>
<p style="margin-left:11%;"><b>ERROR_ON_ARPFAIL</b>=<b>yes</b>|<b>no</b></p>
<p style="margin-left:22%;">In case the value of this
parameter is set to <b>yes</b>, vzctl will fail to start a
container if there is another host with the same IP presentin thenetwork. Any other value makes vzctl to only printsubnetthe warning (which is the default behavior). The </p> <p style="margin-left:11%;"><b>SKIP_ARPDETECT</b>=<b>yes</b>|<b>no</b></p> <p style="margin-left:22%;">In case the value of thisparameter is set to <b>yes</b>, vzctl will not use ARPqueries when starting a container in order to detect ifthere is another host with the same IP present in thenetwork. Note that for each IP, vzctl sends ARP query andwaits up to 1 second for response. Any other value means todo ARP detection.</p> <p style="margin-left:11%;"><b>FORCE_ROUTE</b>=<b>yes</b>|<b>no</b> makes </p> <p style="margin-left:22%;">In case the value of thisparameter is set to <b>yes</b>, vzctl will attempt to changean existing route to point to a container when starting acontainer if new route setup fails. Any other value means to only print thewarningattempt to add new routes (default behavior).</p>
=== Defaults for vzctl create ===
to create a new container. Corresponds to <b>--config</b>
option of <b>vzctl create</b>.</p>
<p style="margin-left:11%;"><b>VE_LAYOUT</b>=<b>simfs</b>|<b>ploop</b>[<b>:</b>{<b>plain</b>|<b>expanded</b>|<b>raw</b>}]</p>
<p style="margin-left:22%;">Default CT filesystem layout
for a new container, can either be <b>ploop</b> or
<b>simfs</b>. In case <b>ploop</b> is used, one can
additionally specify ploop disk image format after a colon.
Possible ploop formats are <b>expanded</b>, <b>plain</b> and
<b>raw</b>. Default is <b>expanded</b>. Using <b>raw</b> is
not recommended and is not supported.</p>
<p style="margin-left:22%; margin-top: 1em">Corresponds to
<b>--layout</b> option of <b>vzctl create</b>.</p>
=== Defaults for containers ===
the actual numeric CT ID.</p>
<p style="margin-left:11%;"><b>IPTABLESSTOP_TIMEOUT</b>="<i>modulenumber</i>"</p> <p style="margin-left:22%;">Time to wait for a container toshut down on <b>vzctl stop</b>, before forcibly killing it,in seconds. Hardcoded to 120 if not set.</p> <p style="margin-left:11%;"><b>NAMESERVER</b>="<i>ip module</i>[<i>ip </i>...]"</p> <p style="margin-left:22%;">Default value for containersnameserver(s).Several name server addresses are divided byspaces.If set to <b>inherit</b>, values from hostsystem’s <b>/etc/resolv.conf</b> are used.</p> <p style="margin-left:11%;"><b>SEARCHDOMAIN</b>="<i>domain </i>[<i>domain </i>...]"</p>
<p style="margin-left:22%;">List of iptables modules to beenabled Default value for containers, corresponds search domains. Several search domains are divided byspaces. If set to <b>--iptablesinherit</b>, values from hostoptionsystem’s <b>/etc/resolv.conf</b> are used.</p>
<p style="margin-left:11%; margin-top: 1em">Most of the