Perform this task to set system-related parameters, including upload/download temporary directories, personal disk storage pool, and personal disk retention duration.
Private disks are supported only for VDI cloud desktops that are installed with Windows and Kylin operating systems.
Before you configure private disk parameters, first configure shared storage pools or GlusterFS storage of the custom storage type. For more information about configuring shared storage pools, see "Configure shared storage for a cluster." For more information about GlusterFS storage configuration, see "GlusterFS settings."
Private disks are not supported by RBD network storage.
Editing the reserved memory on the management node is a high-risk operation. Please perform this operation with caution.
From the left navigation pane, select System > Advanced Settings > System Parameters.
Click Edit at the lower left corner, configure system parameters, and then click Save.
Editing the Upload/Download Temporary Directory parameter is a critical task. In the dialog box that opens after the modification, you must select I am fully aware of the impacts of this operation, enter the administrator password, and then click OK.
Upload/Download Temporary Directory: Specify the directory for temporarily save files during upload or download. For example, files uploaded in file distribution will be saved in this temporary directory. The default is /vms/tmp. The temporary directory cannot be /, /vms, /var, /root, or /home. The temporary directory will be cleared regularly. Please do not use it to save user data.
Private Disk Storage Pool: Specify the shared storage pool or GlusterFS storage of the custom storage type for allocating personal disk spaces for users.
Private Disk Retention Time: Set the time for retaining the private disk of a user after the user is deleted, in days. The default is 10 days. Value 0 indicates that the system immediately deletes the private disk of a user after the user is deleted.
System Log Level: Select a log level. Options include Error, Warning, and Info. The default is Error.
Operation Log Lifetime: Specify the time period within which operation logs cannot be deleted.
Alarm Lifetime: Specify the lifetime period of alarms.
Monitor Refresh Interval: Set the automatic refresh time interval for host and VM performance monitoring on the Space Console. Options are 30 seconds, 1 minute, 5 minutes, and 10 minutes. The default is 30 seconds.
Monitor Data Polling Interval: Set the interval for the system to collect CPU, memory, disk, network, and other performance data of hosts and VMs. The performance monitoring tabs for clusters, hosts, and VMs will display various performance monitoring data according to this interval. The minimum interval is 10 seconds, the maximum is 120 seconds, and the default is 120 seconds.
Monitor Data Lifetime: Set the number of days for performance monitoring data to be retained on the system. The default is 7 days.
Access Protocol: Specify the protocol that can be used to access the system. Options include http and https. The default is http. If you change the protocol, you must clear the browser cache before you access Space Console.
HA System Parameters: Host Heartbeat Interval: Specify the interval at which CVK hosts send heartbeat packets to Space Console. If a CVK host fails, the heartbeat is interrupted, and VMs on the host are migrated to other hosts in the same cluster after three host heartbeat intervals and three storage heartbeat intervals.
HA System Parameters: Storage Heartbeat Interval: Specify the interval at which CVK writes timestamps to the storage pool. If a storage network fails, the heartbeat is interrupted, and affected VMs are migrated to other hosts in the same cluster after three storage heartbeat intervals.
Max External Snapshots: Set the maximum number of all external snapshots allowed to be created by the system, including snapshots created by clients, scheduled task snapshots, virtualization snapshot management, and snapshots created from different locations.
Change VNC Console Password: Configure whether a password is required to access the VNC console of a VM. If this feature is enabled, you can set or modify the password used to connect to the VNC console of a newly created VM. This setting applies only to newly created VMs after the password has been set. For VMs deployed in a desktop pool, the VNC password must be set separately on the deployment page.
VNC Console Password: Set the password for connecting to the VNC console of a VM. If you want to change the VNC console password for a particular VM, edit the VM.
| Due to security and confidentiality purposes, if you enable Change VNC Console Password and save the configuration, the parameter will be displayed as disabled regardless of whether you set a password or not. You must enter the password you have set to access the VM console. For use in the future, keep the password safe and secure. |
Host Memory Reservation: Configure whether to reserve memory for CVK hosts. Options include On and Off. The default is Off. If you select On, the system reserves 20% of the host memory or 10 GB host memory (whichever is smaller) for the CVK hosts. If the different between the free memory on a host and the memory used by VMs on the host is smaller than the reserved memory, VMs cannot be started on or migrated to the host. If you select Off, host memory reservation is disabled for CVK hosts. VMs can be started on or migrated to the host as usual.
Reserved Memory on Management Node: Set the default size of the memory reserved for the management node. The actual size of the memory reserved is 40% of the host memory or the default reserved memory size (whichever is smaller). To avoid system operation failure, set an appropriate value for this parameter.
Memory Check: Select whether to enable memory check for VM deployment. If you select On, the total memory size of all VMs deployed on a host cannot exceed 80% of the memory size of the host. The system will check the memory of a host while adding, cloning, or deploying VMs on the host.
CPU Overcommitment: Select whether to enable CPU overcommitment. Options include On and Off. The default is Off. If you select On, the number of vCPUs bound to the physical CPUs of a NUMA node can exceed the number of the physical CPUs. If you select Off, the number of vCPUs bound to the physical CPUs of a NUMA node cannot exceed the number of the physical CPUs.
Shared Storage Fault Action: Select the action to take when the shared storage of a host fails. Options include Restart Host and Do Not Restart Host. If you select Do Not Restart Host, you must enable HA for the cluster.
DRS VM Startup: Select whether to enable DRS VM startup. With this feature enabled, the system examines whether a host meets the VM startup requirements before starting up a VM on the host. If the requirements are not met, the system migrates the VM to the optimal host to startup. This feature takes effect only when automatic migration is enabled for VMs.