6,534
edits
Changes
beta version of man2wiki man page (work in progress!)
== NAME ==
<p style="margin-left:11%; margin-top: 1em">vz.conf −
global OpenVZ configuration file</p>
== SYNOPSIS ==
<p style="margin-left:11%; margin-top: 1em">/etc/vz/vz.conf</p>
== DESCRIPTION ==
<p style="margin-left:11%; margin-top: 1em">This is the
global configuration file for OpenVZ. It consists of lines
in the form</p>
<p style="margin-left:11%; margin-top: 1em"><b>PARAMETER</b>="<i>value</i>"</p>
<p style="margin-left:11%; margin-top: 1em">All parameter
names and values are case-sensitive. Quotes surrounding
<i>value</i> are required if value contains spaces, and are
optional otherwise. Extra spaces are not allowed. All
unrecognized lines will be ignored.</p>
=== Global parameters ===
<p style="margin-left:11%;"><b>VIRTUOZZO</b>=<b>yes</b>|<b>no</b></p>
<p style="margin-left:22%;">This parameter can be set to
<b>yes</b> or <b>no</b>, and used by the <b>vz</b> init
script. In case it is not set to <b>yes</b>, nothing will be
done to boot up OpenVZ on this node.</p>
<p style="margin-left:11%;"><b>LOCKDIR</b>=<i>directory</i></p>
<p style="margin-left:22%;">Set the directory to put lock
files to.</p>
<p style="margin-left:11%;"><b>VE0CPUUNITS</b>=<i>number</i></p>
<p style="margin-left:22%;">Value of this parameter sets
<b>cpuunits</b> for CT0 (host system).</p>
<p style="margin-left:11%;"><b>LOGGING</b>=<b>yes</b>|<b>no</b></p>
<p style="margin-left:22%;">Enables or disables logging.
This parameter can be set to <b>yes</b> or <b>no</b>,
default is <b>yes</b>.</p>
<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>
<p style="margin-left:22%;">Set the logging level for the
log file (does not affect console output). The greater the
<i>number</i> is, the more information will be logged to the
<b>LOGFILE</b>. Default is <b>0</b>, which means to log
normal messages and errors. If set to <b>-1</b>, only errors
will be logged.</p>
<p style="margin-left:11%;"><b>VERBOSE</b>=<i>number</i></p>
<p style="margin-left:22%;">Set the logging level for
console/terminal output (does not affect log file). Default
is <b>0</b>, which means to log normal messages and errors.
Increasing the <b>number</b> makes [[Man/vzctl.8|<b>vzctl</b>(8)]] more
verbose.</p>
<p style="margin-left:11%;"><b>MODULES_DISABLED</b>=<b>yes</b>|<b>no</b></p>
<p style="margin-left:22%;">If the value of this parameter
is set to <b>yes</b>, no attempt to load kernel modules is
made by the <b>vz</b> initscript. This is helpful on systems
which have OpenVZ-specific features compiled into the kernel
(i. e. not as modules).</p>
<p style="margin-left:11%;"><b>IPTABLES_MODULES</b>="<i>module module ...</i>"</p>
<p style="margin-left:22%;">List of iptables kernel modules
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> is
used.</p>
<p style="margin-left:11%;"><b>VZFASTBOOT</b>=<b>yes</b>|<b>no</b></p>
<p style="margin-left:22%;">If the value of this parameter
is set to <b>yes</b>, <b>vz</b> initscript called with
<b>start</b> argument will start the containers with
uncleanly shutdown quota state without performing quota
reinitialization (which is usually a time-consuming
process). After all the containers are started, the
initscript when restarts those containers with unclean quota
in a normal way (to recalculate/fix quotas).</p>
<p style="margin-left:11%;"><b>TEMPLATE</b>=<i>directory</i></p>
<p style="margin-left:22%;">Value of this parameter is a
directory in which all container template data are
stored.</p>
=== Network interface parameters ===
<p style="margin-left:11%;"><b>VE_ROUTE_SRC_DEV</b>="<i>device</i>"</p>
<p style="margin-left:22%;">This parameter specifies the
network device name which IP address will be used as the
source IP. This is helpful in case more than one network
interface is configured on HN and there is a need to specify
the source IP address. Default is the first device in the
network device list.</p>
<p style="margin-left:11%;"><b>NEIGHBOUR_DEVS</b>="<b>detect</b>"</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. If this is set to
<b>detect</b>, the right network interface (the one which is
in the same subnet as a CT IP) will be chosen automatically.
Any other value restores old (as of vzctl 3.0.19 or older)
behavior, when all the possible interfaces were 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 in the
subnet. The value of <b>no</b> makes vzctl to only print the
warning.</p>
=== Defaults for containers ===
<p style="margin-top: 1em">Below parameters are defaults
for containers, and can be overwritten by parameters in
[[Man/ctid.conf.5|<b>ctid.conf</b>(5)]] per-container configuration file.</p>
<p style="margin-left:11%;"><b>DISK_QUOTA</b>=<b>yes</b>|<b>no</b></p>
<p style="margin-left:22%;">In case the value of this
parameter is set to <b>no</b>, all disk quota operations are
disabled.</p>
<p style="margin-left:11%;"><b>VE_ROOT</b>=<i>directory</i></p>
<p style="margin-left:22%;">Value of this parameter is the
<i>directory</i> which serves as container root mount point.
Value must contain literal string <b>$VEID</b>, which will
be substituted with the actual numeric CT ID.</p>
<p style="margin-left:11%;"><b>VE_PRIVATE</b>=<i>directory</i></p>
<p style="margin-left:22%;">Value of this parameter is the
<i>directory</i> in which all the files and directories
specific to that container are stored. Value must contain
literal string <b>$VEID</b>, which will be substituted with
the actual numeric CT ID.</p>
<p style="margin-left:11%;"><b>CONFIGFILE</b>=<i>name</i></p>
<p style="margin-left:22%;">Default configuration file for
<b>create</b> action, corresponds to <b>--config</b>
option.</p>
<p style="margin-left:11%;"><b>IPTABLES</b>="<i>module module ...</i>"</p>
<p style="margin-left:22%;">List of iptables modules to be
enabled for containers, corresponds to <b>--iptables</b>
option.</p>
<p style="margin-left:11%; margin-top: 1em">Most of the
other parameters that appear in per-container configuration
files [[Man/ctid.conf.5|<b>ctid.conf</b>(5)]] can be also set here. Still, it is
recommended to keep <b>TEMPLATE</b>, <b>VE_PRIVATE</b> and
<b>VE_ROOT</b> in this configuration file, and all the other
container related parameters in per-container configuration
files.</p>
== SEE ALSO ==
<p style="margin-left:11%; margin-top: 1em">[[Man/vzctl.8|<b>vzctl</b>(8)]],
[[Man/ctid.conf.5|<b>ctid.conf</b>(5)]].</p>
== LICENSE ==
<p style="margin-left:11%; margin-top: 1em">Copyright (C)
2000-2011, Parallels, Inc. Licensed under GNU GPL.</p>
<p style="margin-left:11%; margin-top: 1em">vz.conf −
global OpenVZ configuration file</p>
== SYNOPSIS ==
<p style="margin-left:11%; margin-top: 1em">/etc/vz/vz.conf</p>
== DESCRIPTION ==
<p style="margin-left:11%; margin-top: 1em">This is the
global configuration file for OpenVZ. It consists of lines
in the form</p>
<p style="margin-left:11%; margin-top: 1em"><b>PARAMETER</b>="<i>value</i>"</p>
<p style="margin-left:11%; margin-top: 1em">All parameter
names and values are case-sensitive. Quotes surrounding
<i>value</i> are required if value contains spaces, and are
optional otherwise. Extra spaces are not allowed. All
unrecognized lines will be ignored.</p>
=== Global parameters ===
<p style="margin-left:11%;"><b>VIRTUOZZO</b>=<b>yes</b>|<b>no</b></p>
<p style="margin-left:22%;">This parameter can be set to
<b>yes</b> or <b>no</b>, and used by the <b>vz</b> init
script. In case it is not set to <b>yes</b>, nothing will be
done to boot up OpenVZ on this node.</p>
<p style="margin-left:11%;"><b>LOCKDIR</b>=<i>directory</i></p>
<p style="margin-left:22%;">Set the directory to put lock
files to.</p>
<p style="margin-left:11%;"><b>VE0CPUUNITS</b>=<i>number</i></p>
<p style="margin-left:22%;">Value of this parameter sets
<b>cpuunits</b> for CT0 (host system).</p>
<p style="margin-left:11%;"><b>LOGGING</b>=<b>yes</b>|<b>no</b></p>
<p style="margin-left:22%;">Enables or disables logging.
This parameter can be set to <b>yes</b> or <b>no</b>,
default is <b>yes</b>.</p>
<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>
<p style="margin-left:22%;">Set the logging level for the
log file (does not affect console output). The greater the
<i>number</i> is, the more information will be logged to the
<b>LOGFILE</b>. Default is <b>0</b>, which means to log
normal messages and errors. If set to <b>-1</b>, only errors
will be logged.</p>
<p style="margin-left:11%;"><b>VERBOSE</b>=<i>number</i></p>
<p style="margin-left:22%;">Set the logging level for
console/terminal output (does not affect log file). Default
is <b>0</b>, which means to log normal messages and errors.
Increasing the <b>number</b> makes [[Man/vzctl.8|<b>vzctl</b>(8)]] more
verbose.</p>
<p style="margin-left:11%;"><b>MODULES_DISABLED</b>=<b>yes</b>|<b>no</b></p>
<p style="margin-left:22%;">If the value of this parameter
is set to <b>yes</b>, no attempt to load kernel modules is
made by the <b>vz</b> initscript. This is helpful on systems
which have OpenVZ-specific features compiled into the kernel
(i. e. not as modules).</p>
<p style="margin-left:11%;"><b>IPTABLES_MODULES</b>="<i>module module ...</i>"</p>
<p style="margin-left:22%;">List of iptables kernel modules
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> is
used.</p>
<p style="margin-left:11%;"><b>VZFASTBOOT</b>=<b>yes</b>|<b>no</b></p>
<p style="margin-left:22%;">If the value of this parameter
is set to <b>yes</b>, <b>vz</b> initscript called with
<b>start</b> argument will start the containers with
uncleanly shutdown quota state without performing quota
reinitialization (which is usually a time-consuming
process). After all the containers are started, the
initscript when restarts those containers with unclean quota
in a normal way (to recalculate/fix quotas).</p>
<p style="margin-left:11%;"><b>TEMPLATE</b>=<i>directory</i></p>
<p style="margin-left:22%;">Value of this parameter is a
directory in which all container template data are
stored.</p>
=== Network interface parameters ===
<p style="margin-left:11%;"><b>VE_ROUTE_SRC_DEV</b>="<i>device</i>"</p>
<p style="margin-left:22%;">This parameter specifies the
network device name which IP address will be used as the
source IP. This is helpful in case more than one network
interface is configured on HN and there is a need to specify
the source IP address. Default is the first device in the
network device list.</p>
<p style="margin-left:11%;"><b>NEIGHBOUR_DEVS</b>="<b>detect</b>"</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. If this is set to
<b>detect</b>, the right network interface (the one which is
in the same subnet as a CT IP) will be chosen automatically.
Any other value restores old (as of vzctl 3.0.19 or older)
behavior, when all the possible interfaces were 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 in the
subnet. The value of <b>no</b> makes vzctl to only print the
warning.</p>
=== Defaults for containers ===
<p style="margin-top: 1em">Below parameters are defaults
for containers, and can be overwritten by parameters in
[[Man/ctid.conf.5|<b>ctid.conf</b>(5)]] per-container configuration file.</p>
<p style="margin-left:11%;"><b>DISK_QUOTA</b>=<b>yes</b>|<b>no</b></p>
<p style="margin-left:22%;">In case the value of this
parameter is set to <b>no</b>, all disk quota operations are
disabled.</p>
<p style="margin-left:11%;"><b>VE_ROOT</b>=<i>directory</i></p>
<p style="margin-left:22%;">Value of this parameter is the
<i>directory</i> which serves as container root mount point.
Value must contain literal string <b>$VEID</b>, which will
be substituted with the actual numeric CT ID.</p>
<p style="margin-left:11%;"><b>VE_PRIVATE</b>=<i>directory</i></p>
<p style="margin-left:22%;">Value of this parameter is the
<i>directory</i> in which all the files and directories
specific to that container are stored. Value must contain
literal string <b>$VEID</b>, which will be substituted with
the actual numeric CT ID.</p>
<p style="margin-left:11%;"><b>CONFIGFILE</b>=<i>name</i></p>
<p style="margin-left:22%;">Default configuration file for
<b>create</b> action, corresponds to <b>--config</b>
option.</p>
<p style="margin-left:11%;"><b>IPTABLES</b>="<i>module module ...</i>"</p>
<p style="margin-left:22%;">List of iptables modules to be
enabled for containers, corresponds to <b>--iptables</b>
option.</p>
<p style="margin-left:11%; margin-top: 1em">Most of the
other parameters that appear in per-container configuration
files [[Man/ctid.conf.5|<b>ctid.conf</b>(5)]] can be also set here. Still, it is
recommended to keep <b>TEMPLATE</b>, <b>VE_PRIVATE</b> and
<b>VE_ROOT</b> in this configuration file, and all the other
container related parameters in per-container configuration
files.</p>
== SEE ALSO ==
<p style="margin-left:11%; margin-top: 1em">[[Man/vzctl.8|<b>vzctl</b>(8)]],
[[Man/ctid.conf.5|<b>ctid.conf</b>(5)]].</p>
== LICENSE ==
<p style="margin-left:11%; margin-top: 1em">Copyright (C)
2000-2011, Parallels, Inc. Licensed under GNU GPL.</p>
