Given the constrained RAM situation described in this question, what is the cleanest method (manual or programmatically) to:
- Identify VMware virtual machines whose RAM has been reclaimed by the VMware balloon driver.
- "Unballoon" the RAM.
Assume that more physical RAM is available to the environment.
I've found that I can vMotion a VM to another host, and that clears the ballooned state. Is there any other method that works?
Note: I've added several hosts and ~512GB of RAM to the environment. The ballooned VMs did not trigger a DRS rebalance action or unballoon themselves. I've had to manually vMotion each of the affected virtual machines to clear this, as shown below...
Here's the before...
And the after... Following a vMotion to another host in the cluster.