<description>The default /etc/resolv.conf file.</description>
</data>
</collection>
+
+ <collection name="cgroup" use="optional" since="0.30.216" id="global-cgroup">
+ <description>
+This directory contains cgroup settings which should be applied to all guests.
+See your kernel documentation for what settings are valid with your
+configuration.
+ </description>
+ <scalar name="mnt">
+ <description>
+The directory to mount the cgroup hierarchy at. The default is /dev/cgroup.
+ </description>
+ </scalar>
+ <scalar name="subsys">
+ <description>
+Comma-separated list of subsystems to enable on the cgroup mount point.
+The default is "all".
+ </description>
+ </scalar>
+ <list name="inherit">
+ <description>
+Some subsystems start out with clean slates, making it impossible to use the
+cgroup before certain things have been set. This is true for e.g. the cpuset
+subsystem. This file contains a list of filenames which should be explicitly
+inherited from the parent (root) cgroup, if not overridden elsewhere.
+The default is cpuset.cpus and cpuset.mems.
+ </description>
+ </list>
+ <scalar name="name" id="global-cgroup-name">
+ <description>
+If this file exists, all guests will be put in one cgroup named after the
+contents of this file. The default is to put each guest in a cgroup named the
+same thing as the guest.
+ </description>
+ </scalar>
+ <scalar name="base">
+ <description>
+If this file exists, all cgroups will be created underneath this directory
+in the cgroup mount point.
+ </description>
+ </scalar>
+ </collection>
</collection>
<collection name=".distributions" use="optional">
values.
</description>
</list>
- <list name="flags">
+ <list name="cflags" id="cflags" since="0.30.216">
<description>
Contains per line a flag. See <ulink
url="http://svn.linux-vserver.org/svn/util-vserver/trunk/lib/cflags-v13.c">lib/cflags-v13.c</ulink>
for possible values.
</description>
- <!--
- <elements>
- <element name="fakeinit">
- <description>
-The new process will believe it is process number 1. Useful to run a
-real /sbin/init in a vserver. Warning: this flag should not be used
-unless you know what you are doing. Often, it is better to use the
-'plain' initstyle.
- </description>
- </element>
- <element name="lock">
- <description>
-The new process is trapped and can't use chcontext anymore.
- </description>
- </element>
- <element name="sched">
- <description>
-The new process and its children will share a common
- </description>
- </element>
- <element name="nproc">
- <description>
-Limit the number of process in the vserver according to
-ulimit setting. Normally, ulimit is a per user thing.
-With this flag, it becomes a per vserver thing.
- </description>
- </element>
- <element name="private">
- <description>
-No one can join this security context once created.
- </description>
- </element>
- <element name="ulimit">
- <description>
-Apply the current ulimit to the whole context
- </description>
- </element>
- </elements>
- -->
+ </list>
+ <list name="flags">
+ <description>
+Old name for <optionref>cflags</optionref>. Deprecated.
+ </description>
</list>
<list name="nflags" since="0.30.212">
<description>
<optionref>fstab</optionref> also.
</description>
</data>
+ <scalar name="badness">
+ <description>
+Contains the bias to be applied to processes in this guest when the OOM-killer strikes.
+ </description>
+ </scalar>
<collection name="apps">
<collection name="init">
</description>
</hash>
</collection>
-
+
+ <collection name="vdevmap">
+ <collection name="x" type="sybmolic">
+ <description>'x' is an arbitrary name, replace it with e.g. device names</description>
+ <boolean name="open">
+ <description>When this file exists, the device can be opened</description>
+ </boolean>
+ <boolean name="create">
+ <description>When this file exists, the device can be created (if the guest has <optionref ref="bcapabilities">CAP_MKNOD</optionref>)</description>
+ </boolean>
+ <boolean id="guest-vdevmap-remap" name="remap">
+ <description>
+When this file exists, <optionref ref="guest-vdevmap-target">target</optionref> will
+have to exist as well and opening the device will in fact open the target device
+ </description>
+ </boolean>
+ <scalar name="flags">
+ <description>This file will let you specify unimplemented flags manually</description>
+ </scalar>
+ <scalar name="device">
+ <description>Contains the name of a device node</description>
+ </scalar>
+ <scalar id="guest-vdevmap-target" name="target">
+ <description>Contains the device node of the target node to open instead of the device when <optionref ref="guest-vdevmap-remap">remap</optionref> is set</description>
+ </scalar>
+ </collection>
+ </collection>
+
<collection name="vshelper">
<scalar name="sync-timeout">
<default>30</default>
interface will be executed.
</description>
</boolean>
+ <boolean name="tun" since="0.30.215">
+ <description>
+When this file exists, a tun interface will be created when the guest
+starts, and removed when the guest stops.
+ </description>
+ </boolean>
+ <boolean name="tap" since="0.30.215">
+ <description>
+When this file exists, a tap interface will be created when the guest
+starts, and removed when the guest stops.
+ </description>
+ </boolean>
+ <boolean name="nocsum" since="0.30.215">
+ <description>
+If a tun or tap interface is created, the presence of this file will
+disable checksumming on it.
+ </description>
+ </boolean>
+ <boolean name="shared" since="0.30.215">
+ <description>
+When this file exists, the tun/tap interface created will not be
+owned by this particular guest.
+ </description>
+ </boolean>
+ <scalar name="uid" since="0.30.215">
+ <description>
+Sets the ownership of tun/tap interfaces. Requires a user id, not a
+username.
+ </description>
+ </scalar>
+ <scalar name="gid" since="0.30.215">
+ <description>
+Sets the group ownership of tun/tap interfaces. Requires a group id,
+not a group name.
+ </description>
+ </scalar>
+ <scalar name="linktype" since="0.30.215">
+ <description>
+Sets the link type of tun/tap interfaces.
+ </description>
+ </scalar>
+ <scalar name="peer" since="0.30.216">
+ <description>
+Sets the peer for a point-to-point link, such as a tun interface.
+ </description>
+ </scalar>
</collection>
</collection>
</collection>
<collection name="dlimits" since="0.30.210">
- <collection name="dlimit" type="symbolic">
+ <description>
+Note that all entries are required for the disk limit to be applied.
+ </description>
+ <collection name="x" type="symbolic">
+ <description>'x' is an arbitrary name, replace it with e.g. integers</description>
<scalar name="directory">
<description>The directory to which the limit should be applied</description>
</scalar>
</collection>
<collection name="cpuset" since="0.30.211">
+ <description>
+Puts the guest in a cpuset. Required entries are name, cpus and mems.
+ </description>
<scalar name="name">
<description>The name of the cpuset for this vserver</description>
</scalar>
</scalar>
</collection>
</collection>
+
+ <collection name="spaces" since="0.30.215">
+ <boolean name="pid">
+ <description>Enables pid virtualization for this guest</description>
+ </boolean>
+ <boolean name="net">
+ <description>Enable network virtualization for this guest</description>
+ </boolean>
+ <scalar name="mask">
+ <description>Contains a mask of spaces to clone/enter</description>
+ </scalar>
+ </collection>
+
+ <collection name="ionice" since="0.30.216">
+ <scalar name="class">
+ <description>The IO scheduling class to use for this guest (see ionice(1)).</description>
+ </scalar>
+ <scalar name="priority">
+ <description>The IO scheduling priority to use for this guest (see ionice(1)).</description>
+ </scalar>
+ </collection>
+
+ <collection name="cgroup" use="optional" since="0.30.216" id="guest-cgroup">
+ <description>
+This directory contains cgroup settings to be applied to this guest.
+See your kernel documentation for what settings are valid with your
+configuration.
+ </description>
+ <scalar name="name">
+ <description>
+If this file exists, the guest will be put in a cgroup named after the
+contents of this file. The default is to name the cgroup the same thing as the
+guest, unless
+<optionref ref="global-cgroup-name">.defaults/cgroup/name</optionref> says
+otherwise.
+ </description>
+ </scalar>
+ </collection>
+ <scalar name="nocgroup" since="0.30.216">
+ <description>
+If this file exists,
+<optionref ref="global-cgroup">.defaults/cgroup</optionref> will be ignored
+for this guest.
+ </description>
+ </scalar>
</collection>
</database>