Virtualization

Inside a virtual machine

See how a guest OS uses virtual CPU, memory, disk, and network devices that the hypervisor maps onto a physical host.

One VM · guest OS plus virtual devicesCompute requestsCompute requestsMemory viewMemory viewDisk I/ODisk I/ONetwork framesNetwork framesvm-vcpu ↔ vm-hypervisorvm-memory ↔ vm-hypervisorvm-disk ↔ vm-hypervisorvm-vnic ↔ vm-hypervisorPhysical resourcesPhysical resourcesGuest OS and appsGuest OS and appsvCPUvCPUGuest memoryGuest memoryVirtual diskVirtual diskvNICvNICHypervisorHypervisorPhysical hostPhysical host
Legend

Current step

The guest schedules work on vCPUs

A vCPU is a virtual scheduling context; it is not automatically one permanently reserved physical core.

The guest sees virtual devices, not a dedicated physical computer. The hypervisor schedules and maps requests to the host resources available to it.

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

Tags

  • virtualization
  • vm
  • guest os
  • vCPU
  • vRAM
  • vNIC
  • virtual disk

Lessons using this diagram