Name

Description

--applyconfig <name>

This option lets you set the resource parameters for the Container not one by one, but by reading them from the Container sample configuration file. All Container sample configuration files are located in the /etc/vz/conf directory and are named according to the following pattern: ve- <name> .conf-sample , so you should specify only the <name> part of the corresponding sample name after the --applyconfig option. Note that the names of sample configuration files cannot contain spaces. The --applyconfig option applies all the parameters from the specified sample file to the given Container, except for the OSTEMPLATE , TEMPLATES , VE_ROOT , VE_PRIVATE , HOSTNAME , IP_ADDRESS , TEMPLATE , NETIF parameters (if they exist in the configuration sample file).

-p, --numproc <bar : lim>

Number of processes and threads allowed. Upon hitting this limit, the Container will not be able to start new process or thread. In this version of Parallels Cloud Server, the limit shall be set to the same value as the barrier.

Note: Currently, this option may not be supported by the prlctl utility. Use vzctl instead.

--numtcpsock <bar : lim>

Number of TCP sockets ( PF_INET family, SOCK_STREAM type). This parameter limits the number of TCP connections and, thus, the number of clients the server application can handle in parallel. In this version of Parallels Cloud Server, the limit shall be set to the same value as the barrier.

Note: Currently, this option may not be supported by the prlctl utility. Use vzctl instead.

--numothersock <bar : lim>

Number of socket other than TCP. Local (UNIX-domain) sockets are used for communications inside the system. UDP sockets are used for Domain Name Service (DNS) queries, for example. In this version of Parallels Cloud Server, the limit shall be set to the same value as the barrier.

Note: Currently, this option may not be supported by the prlctl utility. Use vzctl instead.

-e, --numiptent <bar : lim>

Number of IP packet filtering entries.

Note: Currently, this option may not be supported by the prlctl utility. Use vzctl instead.

--vmguarpages <bar : lim>

Memory allocation guarantee, in pages (one page is 4 KB). Applications are guaranteed to be able to allocate memory while the amount of memory accounted as privvmpages does not exceed the configured barrier of the vmguarpages parameter. Above the barrier, memory allocation may fail in case of overall memory shortage. In this version of Parallels Cloud Server, the limit shall be set to the same value as the barrier.

Note: Currently, this option may not be supported by the prlctl utility. Use vzctl instead.

-k, --kmemsize <bar : lim>

Size of unswappable kernel memory (in bytes), allocated for internal kernel structures of the processes of a particular Container. Typical amounts of kernel memory are 16…50 KB per process.

Note: Currently, this option may not be supported by the prlctl utility. Use vzctl instead.

--tcpsndbuf <bar : lim>

Total size (in bytes) of send buffers for TCP sockets – amount of kernel memory allocated for data sent from an application to a TCP socket, but not acknowledged by the remote side yet.

Note: Currently, this option may not be supported by the prlctl utility. Use vzctl instead.

-b, --tcprcvbuf <bar : lim>

Total size (in bytes) of receive buffers for TCP sockets. Amount of kernel memory received from the remote side but not read by the local application yet.

Note: Currently, this option may not be supported by the prlctl utility. Use vzctl instead.

--othersockbuf <bar : lim>

Total size in bytes of UNIX-domain socket buffers, UDP and other datagram protocol send buffers.

Note: Currently, this option may not be supported by the prlctl utility. Use vzctl instead.

--dgramrcvbuf <bar : lim>

Total size in bytes of receive buffers of UDP and other datagram protocols.

Note: Currently, this option may not be supported by the prlctl utility. Use vzctl instead.

--oomguarpages <bar : lim>

Out-of-memory guarantee, in 4-KB pages. Any Container process will not be killed even in case of heavy memory shortage if the current memory consumption (including both physical memory and swap) does not reach the oomguarpages barrier. In this version of Parallels Cloud Server, the limit shall be set to the same value as the barrier.

Note: Currently, this option may not be supported by the prlctl utility. Use vzctl instead.

-l, --lockedpages <bar : lim>

Memory not allowed to be swapped out (locked with the mlock() system call), in 4-KB pages.

Note: Currently, this option may not be supported by the prlctl utility. Use vzctl instead.

--shmpages <bar : lim>

Total size of shared memory (including IPC, shared anonymous mappings and tmpfs objects), allocated by processes of a particular Container, in 4-KB pages.

Note: Currently, this option may not be supported by the prlctl utility. Use vzctl instead.

--physpages <bar : lim>

The total size of RAM used by processes, in 4-KB pages. This is accounting-only parameter currently. It shows the usage of RAM by the Container. For memory pages used by several different Containers (mappings of shared libraries, for example), only a fraction of a page is charged to each Container. The sum of the physpages usage for all Containers corresponds to the total number of pages used in the system by all accounted users.

Note: Currently, this option may not be supported by the prlctl utility. Use vzctl instead.

--privvmpages <bar : lim>

Size in 4-KB pages of private (or potentially private) memory, allocated by Container applications. Memory that is always shared among different applications is not included in this resource parameter.

Note: Currently, this option may not be supported by the prlctl utility. Use vzctl instead.

-n, --numfile <bar : lim>

Number of files opened by all Container processes. In this version of Parallels Cloud Server, the limit shall be set to the same value as the barrier.

Note: Currently, this option may not be supported by the prlctl utility. Use vzctl instead.

-f, --numflock <bar : lim>

Number of file locks created by all Container processes.

Note: Currently, this option may not be supported by the prlctl utility. Use vzctl instead.

-t, --numpty <bar : lim>

Number of pseudo-terminals. For example, ssh session, screen , xterm application consumes pseudo-terminal resource. In this version of Parallels Cloud Server, the limit shall be set to the same value as the barrier.

Note: Currently, this option may not be supported by the prlctl utility. Use vzctl instead.

-i, --numsiginfo <bar : lim>

Number of siginfo structures (essentially, this parameter limits size of signal delivery queue). In this version of Parallels Cloud Server, the limit shall be set to the same value as the barrier.

Note: Currently, this option may not be supported by the prlctl utility. Use vzctl instead.

-x, --dcachesize <bar : lim>

Total size, in bytes, of dentry and inode structures locked in memory. Exists as a separate parameter to impose a limit causing file operations to sense memory shortage and return an error to applications, protecting from excessive consumption of memory due to intensive file system operations.

Note: Currently, this option may not be supported by the prlctl utility. Use vzctl instead.

--cpuunits <units>

CPU weight. This is a positive integer number that defines how much CPU time the Container can get as compared to the other virtual machines and Containers running on the server. The larger the number, the more CPU time the Container can receive. Possible values range from 8 to 500000.

If this parameter is not set, the default value of 1000 is used.

--cpulimit <percent | megahertz>

CPU limit, in per cent or megahertz (MHz), the Container is not allowed to exceed. This parameter is not set for newly created Containers; so they can consume all free CPU power of the server.

By default, the limit is set in percent. To set the limit in MHz, specify "m" after the value.

When setting this parameter in per cent, keep in mind that one CPU core makes up 100%. So if the server has 4 CPU cores, the total CPU power will equal 400%.

--cpus <num>

Number of CPU cores defining the CPU limit for a Container. The limit is calculated by multiplying the power of one CPU core by the number of the specified CPU cores.

This option also defines the number of CPUs shown to Container users.

This parameter is not set for newly created Containers; so they can consume all free CPU power of the server.

--cpumask <num>

CPU affinity mask. This mask defines the CPUs on the server that can be used to handle the processes running in the Container. The CPU mask can be specified as both separate CPU index numbers (1,2,3) and CPU ranges (2-4,5-7).

--nodemask < num | all>

The NUMA node mask defining a NUMA node to bind the Container to.

Once you set the mask, the processes running in the Container will be executed only on the CPUs that belong to the specified NUMA node.

Note: Currently, this option may not be supported by the prlctl utility. Use vzctl instead.

--diskspace <bar : lim>

Total disk space consumed by the Container, in 1-KB blocks. In the current version of Parallels Cloud Server, both values must be equal.

--quotaugidlimit <0 | N >

Enables (if set to a value other than 0 ) or disables (if set to 0 ) per-user/group quotas for further management with the standard Linux quota utility.

Keep in mind the following:

• Enabling per-user and per-group quotas for a Container requires restarting the Container.
• If you delete a registered user but some files with their ID continue residing inside your Container, the current number of UGIDs (user and group identities) inside the Container will not decrease.
• If you copy an archive containing files with user and group IDs not registered inside your Container, the number of UGIDs inside the Container will increase by the number of these new IDs.

--ioprio <num>

The Container priority for disk I/O operations. The allowed range of values is 0-7 . The greater the priority, the more time the Container has for writing to and reading from the disk. The default Container priority is 4 .

--iolimit <num>

The bandwidth a Container is allowed to use for its disk input and output (I/O) operations. By default, the limit is set in megabytes per second. However, you can use the following suffixes to use other measurement units:

• G : sets the limit in gigabytes per second.
• K : sets the limit in kilobytes per second.
• B : sets the limit in bytes per second.

In the current version of Parallels Cloud Server, the maximum I/O bandwidth limit you can set for a Container is 2 GB per second.

The default I/O bandwidth limit for all newly created Containers is set to 0, which means that no limits are applied to any Containers.

--iopslimit <num>

The maximum number of disk input and output operations per second a Container is allowed to perform.

By default, any newly created Container does not have the IOPS limit set and can perform so many disk I/O operations per second as necessary.

--rate <class : Kbits>

If traffic shaping is turned on, then this parameter specifies bandwidth guarantee for the Container. The format is class : Kbits where class is the network class (group of IP addresses) and Kbits is the traffic bandwidth.

--ratebound <yes | no>

If set to “yes”, the bandwidth guarantee is also the limit for the Container and the Container cannot borrow the bandwidth from the TOTALRATE bandwidth pool.

--reset_ub

Resets the current values of all system parameters of the server to the ones set in the 0.conf file.

Note: Currently, this option may not be supported by the prlctl utility. Use vzctl instead.

--memsize

The amount of RAM that can be used by the processes of a Container, in megabytes. You can use the following suffixes to set the RAM in other measurement units:

• G in gigabytes
• K in kilobytes
• B in bytes

--swappages

The amount of swap space that can be used by the Container for swapping out memory once the RAM is exceeded, in 4-KB pages. You can use the following suffixes to set swap in other measurement units:

• G in gigabytes
• M megabytes
• K in kilobytes
• B in bytes

--swap

The amount of swap space that can be used by the Container for swapping out memory once the RAM is exceeded, in bytes. You can use the following suffixes to set swap in other measurement units:

• G in gigabytes
• M in megabytes
• K in kilobytes

--vm_overcommit

Memory overcommit factor that defines the memory allocation limit for a Container. The limit is calculated as

(PHYSPAGES + SWAP) * factor

Note: Currently, this option may not be supported by the prlctl utility. Use vzctl instead.