Virtualization

A host shares finite resources

Follow CPU and memory allocation from one physical host to several VMs, including the need to leave capacity headroom.

Independent guest workloadsvCPU · memoryvCPU · memoryvCPU · memoryvCPU · memoryvCPU · memoryvCPU · memoryPhysical capacityPhysical capacityApplication VMApplication VMDatabase VMDatabase VMLab VMLab VMHypervisor schedulerHypervisor schedulerPhysical host resource poolPhysical host resource pool
Legend

Current step

Guests receive virtual capacity

The hypervisor presents vCPUs and memory to each guest while drawing on the same host pool.

Illustrative only: no capacity numbers are implied. Overcommit can increase density, but sustained demand beyond available host capacity can cause contention and poor performance.

Documentation example: addresses use the RFC 5737 ranges and ASNs use the reserved private range. Nothing here connects to a real network.

Tags

  • virtualization
  • vCPU
  • memory
  • resource pool
  • overcommit
  • NUMA

Lessons using this diagram