After CPU exclusive mode is enabled for a virtual machine, its vCPUs no longer share physical CPU resources with other virtual machines, and the virtual machine is expected to achieve more stable performance. When the schedulable CPU resources on the host where the virtual machine resides are insufficient to meet the exclusive requirements, the alert is triggered.
The CPU exclusivity for the virtual machine { .labels.vm_name } in either powered-on or suspended state does not take effect.
The performance stability of the virtual machine may be lower than expected.
After the virtual machine triggers HA, the number of available CPU cores on the target host is insufficient to meet the exclusive requirements of the virtual machine.
Additionally, system services (such as storage and virtualization scheduling) require CPU cores, and the cluster reserves a certain proportion of CPU resources for non-exclusive virtual machines. This results in the number of vCPUs that a single virtual machine can exclusively use being less than the total number of physical cores on the host.
After confirming that the target host has insufficient available cores (after deducting system-reserved cores) to meet the virtual machine's exclusive requirements, you can take the following measures:
Migrate other exclusive virtual machines
Hot migrate some exclusive virtual machines to other hosts to release CPU resources on the current host, enabling the alerting virtual machine to obtain the required exclusive cores.
Migrate the alerting virtual machine
If there is a host in the cluster with a sufficient number of exclusive cores, migrate the alerting virtual machine to that host to meet its exclusive requirements.
Disable CPU exclusive mode
If CPU exclusive mode is not strictly required, disable it for the alerting virtual machine to clear the alert.
