2.2.1.4. prlsrvctl set

Configures OpenVZ preferences.

Syntax. 

prlsrvctl set [--mem-limit <auto>|<size>]
              [-s, --min-security-level <low|normal|high>]
              [-c, --cep <on|off>] [--mng-settings <allow|deny>]
              [--device <device> --assignment <host|vm>_]
              [--backup-storage [<user>[:<passwd>]@]<server>[:<port>]]
              [--backup-tmpdir <tmp_dir>] [--backup-path <path>]
              [--idle-connection-timeout <timeout>]
              [--verbose-log <on|off>] [--cluster-mode <on|off>]
              [--cpu-features-mask <{+|-}feature1,feature2=value[,...]>]
              [--vm-cpulimit-type <full|guest>]

Table 2.19. Options

NameDescription

--mem-limit {auto|<size>}

Sets the upper limit of the memory size that can be reserved for use by virtual machines. The following options are available:

  • auto - if this option is used, the memory size will be calculated automatically.
  • size - user-defined memory size, in megabytes.

-s, --min-security-level <low|normal|high>

The lowest allowable security level that can be used to connect to the hardware node. The following options are available:

  • low - plain TCP/IP (no encryption).
  • normal - most important data is sent and received using SSL over TCP/IP (user credentials during login, guest OS clipboard, etc.) Other data is sent and received using plain TCP/IP with no encryption.
  • high - all of the data is sent and received using SSL.

-c, --cep <on|off>

Enables/disables the participation in the Customer Experience Program (CEP). The following options are available:

  • on - enables CEP.
  • off - disables CEP.

--mng-settings <allow|deny>

Allows to grant or deny permission to new users to modify OpenVZ preferences. By default, only administrators of the host OS can modify OpenVZ preferences. When a new user profile is created (this happens when a user logs in to the hardware node for the first time), he/she will be granted or denied this privilege based on the default setting. This parameter allows you to set that default setting. Please note that this parameter only affects new users (the users that will be created in the future). The profiles of the existing users will not be modified.

--device <device> --assignment <host|vm>

Allows to set the assignment mode for the specified VTd device. The following options are available:

  • host - assign the device to the hardware node.
  • vm - assign the device to virtual machines.

--backup-storage [<user>[:<passwd>]@]<server>[:<port>]

The default backup server where to store virtual machine backups.

--backup-path <path>

The name and path of the default directory on the backup server where to store virtual machine backups.

--verbose-log <on|off>

Turns the verbose output for the command on or off.

--cluster-mode <on|off>

Turns the cluster mode on or off.

--idle-connection-timeout <timeout>

Sets a timeout interval in seconds after which, if no data has been received from the storage server or backup client, the process of backup/restore is terminated.

--backup-tmpdir <tmp_dir>

Specifies a temporary directory where special snapshots created during virtual machine backup will be stored. This may be necessary so as not to run out of storage space on physical servers where most of the storage space is allocated to virtual machines and very little is left for the server itself.

--cpu-features-mask <{+|-}feature1,feature2=value[,…]>

Changes CPU features mask on the host. To mask/unmask features, use the +feature/-feature syntax respectively. Omitting the sign is equvalent to unmasking. Features that require specific value can be set using the feature=value syntax. To view a full list of host CPU features which are supported, unmaskable and already masked, run the prlsrvctl info --full command.

Note

Note: All virtual machines and containers on the host must be stopped.

--vm-cpulimit-type <full|guest>

Specifies the type of virtual machine threads to be affected by the CPU limit:

  • full (default) - both hardware emulation and guest OS threads are limited.
  • guest - only guest OS threads are limited.

With the guest option, the guest OS is guaranteed to have all the resources implied by the VM configuration. At the same time, the VM’s hardware emulation threads spend additional resources of the host. For example, for a VM with two 2.8 GHz vCPUs, switching to guest means that VM’s guest applications will have all the resources of two 2.8 GHz vCPUs at their disposal.

Note

Notes:

  1. Some types of guest applications, like voice-over-IP software, significantly increase expenses on hardware emulation threads.
  2. After changing this parameter, restart running virtual machines for the changes to take effect.