This article is part of an Essential Guide, our editor-selected collection of our best articles, videos and other content on this topic. Explore more in this guide:
9. - Terms to know for virtualization automation: Read more in this section
- memory ballooning
- Microsoft System Center Virtual Machine Manager 2012
Explore other sections in this guide:
- 1. - Benefitting from task automation and workflow orchestration
- 2. - Automation is a must-learn technology for IT pros
- 3. - Finding a data center automation balance
- 4. - Expert advice: Use common sense when devising an automation strategy
- 5. - How to avoid manual resource allocation
- 6. - IT process automation in a Hyper-V environment
- 7. - What you should know to get the most out of vCenter Orchestrator
- 8. - Workflow automation software showdown: Citrix, Microsoft and VMware
Memory ballooning is a virtual memory management technique used to free unused memory.
Having multiple virtual machines (VMs) on a single physical server requires virtual memory management techniques to control resource sharing and to prevent shortages. Some processor chipsets use hardware to offload a portion of the virtual memory management work by creating two layers of page tables, the data structure that provides the mapping between virtual addresses and physical addresses. The layers, however, make it difficult for the hypervisor to see a VM's memory contents, how much memory that VM requires or whether the VM is consuming too much memory.
Balloon drivers, which are installed in each VM, transfer the memory shortage from the host (where the shortage exists) to the VM. The hypervisor alerts the balloon driver of low memory instances and instructs it to inflate, which locks a set of unused memory in the VM. The hypervisor can then reassign the physical memory to another VM. This swap activity can potentially impact performance depending upon the amount of memory to recoup and/or the quality of the storage IOPS delivered to the VM. In a VMware environment, the balloon driver only activates when memory becomes scarce, so it’s best to have no ballooning activity at all. In a Windows Server environment, the balloon driver allocates RAM to the VM on-demand.