Execution cycle
VM-entry, direct execution, VM-exit.
The hypervisor prepares guest control state and enters the virtual CPU. The processor runs guest instructions until an event configured for interception occurs. It then saves guest state, reports an exit reason and resumes the hypervisor.
A VM-exit is not limited to privileged instructions.
Which events exit depends on the VMM’s control settings. Reducing unnecessary exits is one reason paravirtual devices and careful CPU models matter.
One memory reference
Two page-table walks become one hardware-managed translation.
- Guest virtualAddress used by the guest process.
- Guest physicalGuest page tables produce the machine address the guest believes it owns.
- Host physicalEPT on Intel or NPT on AMD maps that address to real memory.
- TLBSuccessful translations are cached to avoid repeating the full walk.
Host evidence
# Linux
lscpu | grep Virtualization
grep -Eo 'vmx|svm' /proc/cpuinfo | head
dmesg | grep -Ei 'kvm|iommu'
# Windows PowerShell
Get-ComputerInfo -Property HyperVRequirement*What hardware acceleration does not solve
Device model
A slow emulated disk or network device can dominate performance even when CPU execution is accelerated.
Scheduling
Too many runnable vCPUs still wait for physical CPU time.
Memory locality
EPT/NPT translates addresses; it does not guarantee NUMA-local placement.
Security policy
Mitigations, VBS and nested configurations can change behavior and overhead.