When you edit the number of CPUs for VMs, if the number of CPUs has not been increased after the VMs were created, you cannot reduce the number of CPUs. If you reduce the number of CPUs, make sure the number of CPUs after reduction is not lower than the number set when the VM was created.
On the top navigation bar, click Compute.
From the left navigation pane, select Resource Navigation > All > Resources > Host Pool Name > Cluster Name, Resource Navigation > All > Resources > Host Pool Name > Cluster Name > Host Name, or Resource Navigation > All > Resources > Host Pool Name > Host Name.Click the VMs tab.
Select the target VMs, click Bulk Actions on top of the VM list, and then select Edit.
In the dialog box that opens, click OK.
CPUs: Edit the number of CPUs and CPU cores for the VMs, which cannot be more than the maximum number of CPUs on the host. If you change the number of CPUs for a VM that supports hot-add of CPUs, the operating system of the VM might operate slowly for 3 to 5 seconds. For a Linux VM, do not perform CPU hot-add during VM startup. Windows 7 supports a maximum of two CPUs. To improve processing performance, you can set multiple cores for each CPU.
Memory: Edit the memory size to be assigned to the VMs.
Edit VNC Password: Edit the password for accessing the VM console.
Enable Time Sync: Enable or disable time synchronization between the VMs and the host where the VMs reside.
Enable Auto CAStools Upgrade: Select whether to enable automatic CAStools upgrade. For the system to automatically upgrade the CAStools for VMs, enable this feature.
Enable Anti-Virus: To prevent VMs from virus attacks, enable this feature. To disable this feature, first shut down the VMs.
HA: Enable or disable HA for VMs. If you disable HA, the VMs will not be managed by cluster HA. This parameter is available only when the cluster is enabled with HA. HA is enabled by default.
Advanced settings:
I/O Priority: Edit the I/O priority for VMs. When multiple VMs are accessing the disks of the host to perform read and write operations, VMs with a high I/O priority take precedence. For the configuration to take effect, restart the VMs.
Startup Priority: Select a startup priority for VMs. When a host in an HA-enabled cluster fails, the system migrates the VMs on the host based on their startup priorities.
Edit Memory Priority: Edit the memory priority for VMs.
Edit Service Priority: Set the service priority of VMs. The service priority indicates the importance of a VM. When the host does not have sufficient memory, VMs are shut down based on priority. Low-priority VMs are at risk of shutdown to ensure that high-priority VMs run correctly.
Enable Auto Migration: To enable VMs to automatically migrate in the cluster after the DRS and DPM policies take effect, enable this feature.
Schedule Priority: Edit the schedule priority for VMs. For the configuration to take effect, restart the VMs.
Enable Auto Start: For VMs to start immediately after the attached host starts, enable this feature.
VM Escape Interception: VM escape allows an attacker to exploit vulnerabilities in the software or configuration errors to break out of a VM and gain unauthorized access to the underlying hypervisor or other VMs to obtain sensitive data. For the system to display interception alarms in real-time alarms when VM escape interception is enabled, you must enable VM escape alarm in Security Alarms on the Ops > System Ops > Alarm Management > Alarm Thresholds > Default Threshold Settings.