VMMB: Virtual Machine Memory Balancing for Unmodified Operating Systems

  • Authors:

  • Changwoo Min;Inhyeok Kim;Taehyoung Kim;Young Ik Eom

  • Affiliations:

  • School of Information & Communication Engineering, Sungkyunkwan University, Gyeonggi-Do, Korea 440-746 and Samsung Electronics, Gyeonggi-Do, Korea 443-742;School of Information & Communication Engineering, Sungkyunkwan University, Gyeonggi-Do, Korea 440-746;School of Information & Communication Engineering, Sungkyunkwan University, Gyeonggi-Do, Korea 440-746;School of Information & Communication Engineering, Sungkyunkwan University, Gyeonggi-Do, Korea 440-746

  • Venue:
  • Journal of Grid Computing
  • Year:
  • 2012

Quantified Score

Hi-index 0.00

Visualization

Abstract

Virtualization technology has been widely adopted in Internet hosting centers and cloud-based computing services, since it reduces the total cost of ownership by sharing hardware resources among virtual machines (VMs). In a virtualized system, a virtual machine monitor (VMM) is responsible for allocating physical resources such as CPU and memory to individual VMs. Whereas CPU and I/O devices can be shared among VMs in a time sharing manner, main memory is not amendable to such multiplexing. Moreover, it is often the primary bottleneck in achieving higher degrees of consolidation. In this paper, we present VMMB (Virtual Machine Memory Balancer), a novel mechanism to dynamically monitor the memory demand and periodically re-balance the memory among the VMs. VMMB accurately measures the memory demand with low overhead and effectively allocates memory based on the memory demand and the QoS requirement of each VM. It is applicable even to guest OS whose source code is not available, since VMMB does not require modifying guest kernel. We implemented our mechanism on Linux and experimented on synthetic and realistic workloads. Our experiments show that VMMB can improve performance of VMs that suffers from insufficient memory allocation by up to 3.6 times with low performance overhead (below 1%) for monitoring memory demand.