# Memory Resource Management in VMware ESX Server ## One-line Summary This paper introduced some mechanisms and policies for better memory management in ESX Servers. ## Paper Structure Outline 1. Introduction 2. Memory Virtualization 3. Reclamation Mechanisms 1. Page Replacement Issues 2. Ballooning 3. Demand Paging 4. Sharing Memory 1. Transparent Page Sharing 2. Content-Based Page Sharing 3. Implementation 5. Shares cs. Working Sets 1. Share-Based Allocation 2. Reclaiming Idle Memory 3. Measuring Idle Memory 4. Experimental Results 6. Allocation Policies 1. Parameters 2. Admission Control 3. Dynamic Reallocation 7. I/O Page Remapping 8. Related Work 9. Conclusions ## Background & Motivation This paper attempts to resolve some issues in existing Virtual Machine Managers (VMMs) by introducing several novel mechanisms and policies to manage memory. ## Design and Implementation Several novel techniques and mechanisms are presented. ### Ballooning ![](/files/-MNQM0kPk-fS6cHCI3aX) This technique allows memories to be reclaimed by ESX Servers from the guest OS. When a VM is claimed memory, the ballooning technique persuades the guest OS into cooperating with it. A balloon module is loaded into the guest OS as a pseudo-device driver or kernel service. When the balloon is inflated (by pinning physical pages), the guest OS gets pressured and invokes its own memory management algorithms. Based on the amount of remaining memory, the guest OS either returns pages from its free list or pages out some particular pages to its own virtual disk. In contrast, when a balloon is deflated, the guest OS gets to use more memory. ![Ballooning adds a small overhead (1.4% to 4.4%, because guest OS uses more resources when given more memory initially) while obtaining similar performance compared with a VM w/o ballooning.](/files/-MNQVgKF0W5mAjuvGO8u) ### Idle Memory Tax Idle clients can hoard memory while active clients without enough memory suffer severe memory pressure. This technique basically charges a client more for an idle page than for one it is actively using, preventing the aforementioned scenario from happening when memory is scarce. To estimate the fraction of active memory of each virtual machine, ESX Server uses a statistical sampling approach to obtain estimates. ![The evaluations are obtained by varying the tax rate on two VMs.](/files/-MNQQZFpg1kRYaOb_vTv) ### Content-Based Page Sharing Transparent page sharing is pioneered by Disco, but in order to achieve page sharing, Disco needs to make interface changes in the guest OS. In this paper, ESX Server finds identical pages between VMs by scanning for shared opportunities and hashing the contents for easy comparison. If a match is found, a standard copy-on-write (COW) technique is used to share the pages. ![](/files/-MNQSylxpIc9cSBDc1zi) ![For large numbers of VMs, around 2/3 of all VM memory is reclaimed.](/files/-MNQWly4_MoTQ0tK352o) ### Hot I/O Page Remapping For high-memory systems, modern processors support a physical address extension (PAE) mode that allows the hardware to address up to 64 GB of memory with 36-bit addresses. However, many devices that use direct memory access (DMA) for I/O transfers can only address a subset of this memory. The existing solution is to copy the data in high memory through a temporary bounce buffer into low memory. This creates significant overhead. ESX Server addresses this issue by maintaining statistics to track "hot" pages in high memory that are involved in repeated I/O operations. When the page is too hot (count exceeding a threshold), the page is remapped into low memory. ## Evaluation Unlike a traditional paper, this paper does not have a section dedicated to evaluations. Instead, the evaluations are broken down, following techniques of which they analyze. See the previous section for the evaluations. ## New Vocabulary * ESX Server: An enterprise-level virtualization tool. ESX Server runs on "bare-metal". This means that the ESX Server software is directly installed into the computer w/o an operating system for it to run on top of. ## Links * [Paper PDF](http://pages.cs.wisc.edu/~remzi/Classes/736/Fall2010/Papers/esx-osdi02.pdf) * [Presentation Slides](http://www.waldspurger.org/carl/papers/esx-osdi02-slides.pdf) * [What is VMware ESX Server?](https://www.pluralsight.com/blog/it-ops/what-is-vmware-esx-server-and-why-you-need-it) * [Paper review](https://zhu45.org/posts/2019/Mar/11/memory-resource-management-in-vmware-esx-server/) by [Zeyuan Hu](https://zhu45.org/about-me.html), a UW-Madison alumni, now a Ph.D. student at UT-Austin. * [CS 736 @ UW-Madison Spring 2015 Panel Discussion](http://pages.cs.wisc.edu/~swift/classes/cs736-sp15/blog/2015/02/memory_resource_management_in.html) --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://blog.ruipan.xyz/earlier-readings-and-notes/index/memory-resource-management-in-vmware-esx-server.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.