Dynamic Load Balancer
in Proxmox VE 9.2

No more manual balancing

Until now, balancing load across a Proxmox cluster was the admin's job — they decided which VM to move when a node got busy. Since 9.2 it's automatic: the load balancer watches the cluster and initiates migrations itself, so no node is overloaded while others have headroom.

Decisions based on real load

In dynamic mode the CRS factors in the average CPU and memory usage of active VMs plus their configured quotas — not just the sum of reserved resources. In each HA manager round (about every 10 seconds) it checks whether the cluster imbalance exceeds a threshold.

If the imbalance stays above the threshold for a set number of consecutive rounds (the hold duration), the balancer picks the migration that reduces imbalance the most — and performs it.

Enabling and tuning

• Where — Datacenter → Options → Cluster Resource Scheduling.
• Scheduler mode — requires static-load or dynamic-load; the balancer builds on these.
• Parameters — tune the imbalance threshold and hold duration for your cluster to control sensitivity and migration frequency.

What the balancer respects

• HA-managed VMs only — automatic migrations cover resources managed by the HA stack.
• Always affinity-compliant — migrations never break your node and resource affinity rules (e.g. a VM in a 3-node rule stays on those nodes).