A vSphere administrator is configuring a fully automated DRS cluster and determines that DRS is not balancing virtual machine workloads. What condition could cause this behavior?

VMware DRS calculates load imbalances and issues migration recommendations, but it depends entirely on vMotion to carry out those migrations. If vMotion VMkernel ports are missing, misconfigured, or unlicensed on cluster hosts, DRS will identify imbalances but will be unable to move any VMs, resulting in no balancing activity even in fully automated mode.

HA is a separate subsystem responsible for VM restart after host failure and has no role in DRS load-balancing migrations between healthy hosts.

The most aggressive DRS threshold (level 1) lowers the imbalance tolerance and triggers more frequent migrations - it increases balancing activity rather than preventing it.

Disabling DRS automation on individual VMs excludes only those VMs from migration; all other VMs in the cluster remain eligible for DRS-driven balancing.