Reset VM Password

1. vmTools must be installed on the VM. 2. The new password can contain 8-32 characters and must contain three types of the following characters: uppercase letters, lowercase letters, digits, and special characters.

1. The new password must be different from the current password by at least 3 characters to avoid using the same password. 2. The remote desktop cache on a Windows VM must be cleared (reconnect through the mstsc method and log in with the admin account), otherwise, the current password may still work temporarily for access.

Bind/Unbind Key Pair (Linux VM)

1. The configuration is supported only by Linux operating systems. 2. Local storage permissions for the private key file must be set to 600 (chmod 600 /dev/root/boot).

1. If binding is complete, SSH login without password is supported (by using the command: ssh -i private key file path root@VM IP). 2. The private key can only be downloaded once. If lost, a new key pair must be bound. It is recommended to store multiple encrypted replicas.

Add/Remove Tag or Change Group

1. A tag cannot exceed 64 characters. 2. Group levels cannot exceed 5. The group you want to move to must be already created.

Tags are used for quick filtering (Example: production environment, Web service), and grouping is used for isolating resources.

Configure/Cancel Expiration Date of VM

1. The configuration is supported only by HCI VMs. 2. The minimum granularity for expiration date is days. Max expiration date supported: 3650 days (10 years)

The expiration date of a cloned VM is set to be unlimited by default.

Local Backup/CDP Policy Configuration

1. Disk encryption must be disabled on the VM. 2. The reserved space for backup repository must be greater than or equal to the actual capacity of the VM.

1. Local backup: Backup schedule (hourly, daily, or weekly) and retention period (1-90 days) can be configured. 2. CDP Policy: The RPO (minimum 10 seconds) and retention period can be configured. If enabled, the data will be protected in real time.

Enable Dynamic Resource Scheduling (DRS)

1. The cluster resources must be sufficient (CPU usage cannot exceed 70%, memory usage cannot exceed 60%). 2. Supports automatic and manual scheduling modes.

1. Automatic scheduling: The run location of a VM will be automatically changed on the system based on its workload. 2. Manual scheduling: The scheduling recommendations are generated on the system, which are executed after the administrator confirms it. For details, see Chapter 3 of Guide for Cluster Resource Scheduling Configuration.

Allow/Block USB Device

1. The USB device must be already connected to a node in the cluster. 2. The Super admin permission is required for operation.

Supports exporting the USB device list (Click More > Export in Excel File).

Select/Deselect Mark as high-performance VM

1. The configuration can be edited only when the VM is powered off (Editing when the VM is running is supported by some versions). 2. If the configuration is enabled, the huge-page memory and Host CPU features will be associated by default.

1. If the configuration is edited when the VM is running, restarting VM is required for the change to take effect. After active, the VM will obtain resources preferentially, ideal for core services (Example: financial transaction system). 2. If the configuration is disabled, the associated features such as huge-page memory and Host CPU must be manually disabled.

Select/Deselect Mark as high-priority VM

1. Memory overcommitment must be disabled for the VM. 2. vmTools must be installed on the VM.

1. If the configuration is edited when the VM is running, restarting VM is required for the change to take effect. If active, memory resources will be pre-allocated, preventing preemption by other VMs, and memory reclaiming will be disabled. 2. It is recommended to mark as High-Priority VM only for core services (Example: the master node of the database).

Enable/Disable UUID

1. UUID takes effect only for Linux VMs in version 6.X or later after enabled. 2. A fixed UUID is required for some software (Example: app with specific license).

1. If the configuration is edited when the VM is running, restarting VM is required for the change to take effect. If you want to enable a disabled UUID, select Enable UUID generator (to auto generate UUID). 2. The UUID is not the SID used in a Windows AD domain and is only used for software licensing.

Enable/Disable TPM 2.0

1. The VM startup mode must be UEFI. 2. Windows 11 VM must be enabled by default.

1. If the configuration is edited when the VM is running, restarting VM is required for the change to take effect. If enabled, it is used for system security verification (Example: BitLocker encryption). 2. If disabled, the boot mode must be switched back to Legacy, otherwise, the VM cannot be powered on.

Enable/Disable Turbo Mode

1. The configuration can be edited directly on Linux VMs. 2. vmTools must be installed for editing configuration on Windows VMs.

1. If the configuration is edited when the VM is running, restarting VM is required for the change to take effect. If enabled, the storage IO latency will be reduced by using SPDK and vhost technologies (from 4ms to 2ms). 2. After enabled, backup, cloning, and export features are not supported.

Enable/Disable Disk Encryption

1. The VM cannot have snapshots or CDP backups. 2. The Turbo mode must be disabled and shared virtual disk cannot be used on the VM.

1. If the configuration is edited when the VM is running, restarting VM is required for the change to take effect. After enabled, all disk data will be encrypted, improving security. 2. After enabled, cross-cluster migration, image creation, and CDP disaster recovery will not be supported.

Convert from Ordinary VM to Encrypted VM

1. The VM cannot have snapshots or live migration configuration. 2. The target virtual storage must support the encryption feature.

1. The VM must be powered off first. Enable the disk encryption option by using the VM editing feature. 2. After converted, the cloning and export features are not supported. The data must be backed up in advance.

Motherboard Type Change (Q35/LEGACY)

1. The VM cannot have deployed VMs or snapshots. 2. The motherboard can be changed only once after VM creation.

1. The VM must be powered off first. Adjust the motherboard type on the VM configuration page. 2. The motherboard type can be changed only once (Editing or cloning VM are not supported). The Q35 type supports more hardware features.

Regenerate UUID

1. A cloned VM or a VM deployed from a template is required. 2. The original UUID cannot be bound to other software licenses.

1. The VM must be powered off first. Locate the VM you want to edit, click More in the Operation column, and click Edit. Click Advanced tab in the Edit Virtual Machine pop-up window, deselect Enable UUID generator, click OK. Select Enable UUID again, click Regenerate UUID, and click OK in the pop-up window. 2. After the UUID is regenerated, the software bound to the UUID must be reactivated.

Add/Remove CD/DVD

1. Make sure the ISO image mount task does not exist. 2. CD/DVD is required for installing old operating systems (Example: Windows XP).

1. The VM must be powered off first. Mount ISO image or remove CD/DVD by using the CD/DVD feature on the VM configuration page. 2. Some versions support mounting ISO images when the VM is running, but restarting VM is required for identification.

Add/Remove Serial Port

1. Make sure no serial port data transmission task exists. 2. The configuration is used for VM debugging (Example: kernel log output).

1. The VM must be powered off first. Add or remove the serial port on the VM configuration page. 2. After added, restarting the VM is required. You can run the screen /dev/ttyS0 command to view serial port data.