| dataVolume.maxNum |
The maximum number of data volumes that can be attached to a VM
instance. Default: 24. |
24 |
[0,24] |
| host.syncLevel |
The maximum number of commands that can be concurrently executed
in a host. Default: 10. Excessive concurrently executed commands may
bring too high loads to a host. Please proceed with caution. |
10 |
(2,+∞) |
| reservedMemory |
The reserved memory size of hosts that apply KVM virtualization.
Default: 1 GB. Unit: GB, MB, KB, and byte. |
1 GB |
[0,+∞) |
| vm.cacheMode |
The cache mode of a VM instance. Default: none.
Valid values: none, writethrough, and writeback.
- writethrough: The host page cache is used and data writes
are reported as completed only when the data has been
committed to the storage device.
- none: The host page cache is bypassed and data is directly
read from or written to the storage device of the VM
instance.
- writeback: The host page cache is used and data writes are
reported as completed when data is placed in the host page
cache.
|
none |
- none
- writeback
- writethrough
|
| vm.cpuMode |
- Specifies whether to select the same CPU model as the host
for VM instances on the Cloud. Default: None. Valid values:
None, host-model, and host-passthrough, and a specific CPU
model.
- If you select none, the VM CPU model is inconsistent with
the host CPU model.
- If you select host-model, the CPU model of the VM instance
is the same as that of the host, such as Intel Haswell
CPU.
- If you select host-passthrough, the CPU features of the VM
instance are the same as the CPU features of the host, such
as the page table extension, huge page, and virtualization
features.
- If you select a specific CPU model, the CPU model of VM
instances is set to the specified model.
 Note:
- If you select host-model, the CPU of the VM instance may
not support the extended page table extension, huge
page, and virtualization features.
- If you select host-passthrough, the VM instance allows
for virtualization. However, if you migrate the VM
instance to a host whose CPU model is different from the
current host, the migration may fail. In addition, the
CPU utilization of the VM instance measured within the
instance may differ from the CPU utilization measured
from the host.
- If you specifically set the CPU model of an individual
VM instance, the VM CPU model configured in the global
settings does not take effect on the VM instance.
- If you specifically set the CPU model for a cluster, the
VM CPU model configured in the global settings does not
take effect on the VM instances in the cluster.
- If you modify the CPU model, you need to restart a VM
instance to make the modification take effect for the VM
instance.
|
none |
- None
- host-model
- host-passthrough
- A specific CPU model
|
| vm.migrationQuantity |
The maximum number of VM instances that can be concurrently
migrated when a host is in maintenance mode. Default: 2. |
2 |
(0,+∞) |
| vmSyncOnHostPing |
Specifies whether to synchronize the status of VM instances while
pinging the host. Default: true. |
true |
|
| host.DNSCheckList |
The checklist used to check the DNS server while adding a host to
a cluster. |
yahoo.com,google.com,baidu.com |
|
| host.DNSCheckAliyun |
The server IP address of Alibaba Cloud images. |
mirrors.aliyun.com |
|
| host.DNSCheck163 |
The server IP address of NetEase Cloud images. |
mirrors.163.com |
|
| checkHostCpuModelName |
Specifies whether to inspect the CPU type of the host that is to
be added to a cluster or to be used for migration. You can use this
setting to check the CPU type consistency of hosts. Default:
false. |
false |
|
| ignoreMsrs |
Specifies whether to enable the ignore_msrs option in the KVM
kernel module of hosts. Default: false. |
false |
|
| migrate.autoConverge |
- Specifies whether to enable the auto converge feature.
Default: false. If set to true, the auto converge feature is
used during hot migrations of KVM VM instances.
- You can also enable auto converge for a single VM instance.
By default, this setting complies with that in the Global
Setting.
- If the migration is blocked because the VM instance has high
I/O operations for a long time, you can enable auto converge
to ensure the migration is successful.
- If your applications are performance sensitive, we recommend
that you do not enable auto converge.
|
false |
|
| vm.createConcurrency |
The maximum number of VM instances that can be concurrently
created in a host. Default: 1. |
1 |
[1,10] |
| host.snapshot.syncLevel |
The maximum number of commands that can be concurrently executed
in a host. Default: 10. Excessive concurrently executed commands may
bring too high loads to a host. Please proceed with caution. |
10 |
[2,+∞) |
| ivshmem.size |
The memory size of the Inter-VM shared memory (ivshmem) device.
Default: 0. Unit: byte. This value indicates that memory is not
shared between VM instances and the host. If you set a custom value,
the value must be the powers of 2 and cannot be lower than 1
MiB. |
0 |
[0,+∞) |
| restartagentwhenfakedead |
Specifies whether to restart KVM agent if the agent is detected
hung. Default: true. |
true |
|
| migrate.xbzrle |
Specifies whether to enable the Xor Based Zero Run Length
Encoding (XBZRLE) feature. Default: true. Enabling this feature can
make hot migrations of VM instances more efficient. If your VM
instances have high data write workloads, you can enable this
feature to reduce the time for migration. |
true |
|
| testSshPortOpenTimeout |
The timeout period of SSH reconnecting hosts. Default: 5. Unit:
second. If the timeout period expires, SSH reconnection
fails. |
5 |
[1,+∞) |
| enable.host.tcp.connection.check |
Specifies whether to enable fast inspection of
host connection status. Default: false. If set to true, the interval
of inspecting the connection status of the host is shortened. |
false |
|
