This file contains the information to be specified for a virtual machine when creating an L-Server or when modifying a configured (defined) L-Server.
VM specific information definition files can be created for each user group.
Use the UTF-8 character code.
The order of the priority of the parameters is as follows:
L-Server XML file > L-Server template > Definition file (User group) > Definition file (Shared on the system)
[Windows Manager]
Installation_folder\SVROR\Manager\etc\customize_data\vm_prop
[Linux Manager]
/etc/opt/FJSVrcvmr/customize_data/vm_prop
Point
In the storage location above, the sample definition file (vm_VMTYPE.rcxprop.sample) is stored. When using the sample as the definition file, place the file after changing "VMTYPE" to the VM type and deleting ".sample".
Definition files can be divided into definitions that are available for each user group and definitions that are common on the system.
If the same key is configured in the definition file common on the system and the definition file for a specific user group, priority is given to the values indicated in the definition file for the user group.
User Groups
vm_user_group_name_VM_type.rcxprop
Common on System
vm_VM_type.rcxprop
Note
For VM_type, enter the VM type to be specified when creating an L-Server, such as VMware, Hyper-V, Oracle VM, or RHEL-KVM. This value is not case-sensitive.
When there are multiple files with the same VM_type specified in the filename, the VM_type of the filenames are sorted in ascending order of character code, and the one listed first will be selected.
Example
usergroup1_VMware |
Remove any blank spaces in the VM_type.
Example
Oracle VM -> OracleVM |
In the definition file, an item to define is entered on each line. Each line is entered in the following format.
Key = Value |
Specify the following items.
Key | Description |
---|---|
processor_reserve_spec | Specify the minimum amount of CPU resources to be allocated. Enter a value in the range from 0 to the limit of CPU performance, using a number with up to one decimal place, in units of gigahertz. |
processor_share | Specify the relative proportion of CPU resources for allocation. Enter an integer equal to or greater than 1. |
memory_reserve_size | Specify the minimum amount of memory resources to be allocated. Enter a value in the range from 0 to the limit of memory size, using a number with up to one decimal place, in units of gigabytes. |
memory_share | Specify the relative proportion of memory resources for allocation. Enter an integer equal to or greater than 0. |
processor_weight | Specify the priority for CPU allocation. Enter an integer between 1 and 10,000. |
dynamic_memory | Specify the dynamic memory settings.
When omitted, the value varies depending on the initial memory size and memory buffer specified when creating an L-Server.
When dynamic memory is disabled, the values specified for memory_startup_size and memory_buffer_rate will be ignored. |
memory_startup_size | Specify the initial amount of memory to be allocated at startup. Enter a value between 0.1 and the limit of memory size.
When dynamic memory is disabled, this setting is ignored. |
memory_buffer_rate | Specify the percentage of memory to be reserved as a buffer. Enter an integer between 5 and 2000 in units of percent.
When dynamic memory is disabled, this setting is ignored. |
memory_weight | Specify the priority for allocation of memory. Enter an integer between 0 and 10,000. |
max_definable_memory_size | Specify the maximum amount of memory that can be configured for the VM guest on KVM. Enter a value in the range from the limit of memory size to the memory size of a physical server, using a number with up to one decimal place, in units of gigabytes. |
See
When not describing a parameter in the VM specific information definition file, refer to each element name in "14.3.2 Definition Information for Virtual L-Servers (XML)" in the "Reference Guide (Command/XML) CE".
Note
When modifying specifications of an L-Server to which resources have been allocated, the settings in this definition file are not reflected because priority is given to the values already configured for the L-Server. In this case, enter new values in the XML file and then execute the appropriate commands to reflect the changes.
When individual parameters are specified when creating an L-Server template or L-Server, priority is given to those settings over those in this definition file.