1. Overview
VMware vSphere Distributed Resource Scheduler (DRS) balances compute and memory load across cluster hosts. However, setting the migration threshold too aggressively can trigger "vMotion storms"—where VMs constantly migrate back and forth to satisfy temporary load spikes, causing network congestion and hypervisor stun.
2. Technical Breakdown: The 5 Migration Thresholds
vCenter provides a 5-point slider for DRS automation:
- Priority 1 (Conservative): Only applies mandatory recommendations (host maintenance mode or affinity rule violations). Zero dynamic balancing.
- Priority 2: Applies recommendations that promise extremely significant performance improvement.
- Priority 3 (Default & Recommended): Applies recommendations with at least good performance improvement. Balances cluster without excessive migrations.
- Priority 4: Applies recommendations that offer moderate performance improvement.
- Priority 5 (Aggressive): Applies even slight performance improvements. Susceptible to ping-pong migrations.
3. Diagnostic CLI Commands
4. Summary & Takeaways
DRS in vSphere 8 scores VM happiness rather than cluster standard deviation. Tuning your migration threshold to Priority 3 provides optimal balance while protecting host network bandwidth.
Written by Moinul Haque
Practicing infrastructure architect documenting VMware systems engineering and production hypervisors.