Virtual machine placement groups are used to constrain the placement and migration of virtual machines, ensuring they run on appropriate hosts. Placement group rules affect the target host selection during virtual machine startup, migration, and HA rebuilding. Improper configuration may cause virtual machines to fail to rebuild as expected when a failure occurs.
The following { .labels.vms_count } VMs violate the mandatory placement policies by VM placement group { .labels._pg_name }: { .labels.placegroups }.
The VM { .labels.vm_name } is tied to conflicting placement policies in the following { .labels.placegroup_count } placement groups: { .labels.placegroups }.
If the host where the virtual machine resides does not comply with placement group rules, the expected virtual machine placement policy will be violated.
If a virtual machine has multiple conflicting placement group rules, when HA is triggered, the virtual machine may not be able to rebuild on the expected target node, affecting service availability.
The host where the virtual machine currently resides does not comply with placement group rules.
The placement group itself has conflicting rule definitions.
Host violating virtual machine placement group rules
Log in to AOC, go to the cluster, select All > VM placement group, select the placement group involved in the alert, and check on the details page whether the virtual machine has been incorrectly assigned to an unsuitable placement group. If there is an incorrect assignment, reassign the correct placement group based on actual requirements. If the placement group rules are as expected, migrate the virtual machine to a host that complies with the policy, and the alert will be automatically cleared.
Conflicting rules defined in the placement group
Log in to AOC, go to the cluster, select All > VM placement group, select the placement group involved in the alert, and check and adjust the conflicting placement group rules. Once the rules are no longer in conflict, the alert will be automatically cleared.