ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Dynamic Memory lets Hyper-V reclaim idle RAM from guests via the Integration Services balloon driver, enabling safe overcommit. Learn how minimum, maximum and buffer settings work, how to monitor with Get-VMMemory, and the limits to watch.
Goal Establish the precise memory overcommit thresholds that trigger a vMotion failure or VM suspension during live migration in vSphere. Constraints and Uncertainty vSphere allows vMotion to be initiated even when host memory overcommit exceeds 100%. While the vSphere Client may display a warning, the migration action remains enabled. There is no documented
The goal is to identify the exact host memory utilization level at which vSphere DRS treats memory pressure as high enough to trigger automatic reclamation mechanisms such as ballooning, swapping, or VMotion-based load balancing. Currently, this threshold is not visible in the vSphere Client and is derived internally from a combination of active memory, swap
vsphere