The virtualization service can emulate the physical CPUs on a host as vCPUs of a generation less than or equal to the actual generation of the physical CPU, for use by virtual machines. This mechanism ensures smooth hot migration of virtual machines between hosts with CPUs of different generations.
Note: A higher-generation CPU can emulate a lower-generation one, but not the other way around.
When the default virtual machine CPU compatibility of the cluster cannot accommodate all hosts in the cluster, or is not the optimal compatibility setting, the relevant alert is triggered.
The current cluster VM CPU compatibility { .labels.current_model } is not compatible with all the hosts in the cluster.
The current cluster VM CPU compatibility { .labels.current_model } is not the most compatible option for the cluster.
If the CPU compatibility generation is higher than the physical CPU generation of some hosts, virtual machines using this compatibility setting cannot run on those hosts.
If the CPU compatibility generation is lower than that of all physical CPUs in the cluster, virtual machines may not be able to fully utilize the advanced instruction sets provided by the physical CPUs.
The default virtual machine CPU compatibility level of the cluster is inconsistent with the actual minimum generation of physical CPUs in the cluster.
It is generally recommended to set the cluster's default CPU compatibility to the lowest physical CPU generation among all nodes in the cluster. This ensures that in most cases, virtual machines with default configurations can freely start, perform hot migration, and use HA in the cluster to guarantee high availability. For virtual machines with special performance requirements, CPU compatibility can be set individually.
