Guided path: Virtualization & VBS
Step 2 of 3
Hyper-V & partitions
Root vs child partitions, vCPUs, and synthetic devices.
Official Microsoft docs
Closest official references related to this topic on Microsoft Learn.
Why it matters
Explains Task Manager 'Virtual machine' workloads, core isolation, and why some features require firmware virtualization on.
Mental model
Hyper-V creates partitions. The root partition hosts management; guests use emulated or synthetic devices depending on integration services.
How it works
- 1The hypervisor schedules virtual processors across logical CPUs.
- 2Guest physical memory is backed by host RAM with nested page tables.
- 3Integration services provide enlightened I/O on VMBus.
Key terms
- Root partition
- The management OS partition with direct hardware access.
- Enlightened I/O
- Guest I/O path optimized via VMBus instead of full emulation.
A Gen2 VM booting quickly
UEFI + synthetic storage/network reduce legacy emulation overhead compared to older emulated devices.
Common misconception
Enabling Hyper-V does not automatically virtualize your entire desktop inside a VM. The host still runs Windows natively as the root partition.
You should read next
Ranked from your current topic, related links, branch depth, and any active guided path.
expert
VBS, HVCI & isolation
Virtualization-based security features that protect credentials and kernel code.
Next step in your guided path
beginner
Virtualization
Hypervisor layers, virtual machines, and how Windows isolates guests from the host.
Related topic
expert
Plug and Play & power
How devices appear, initialize, and change power state without manual kernel bookkeeping.
Related topic
Related topics
Virtualization
Hypervisor layers, virtual machines, and how Windows isolates guests from the host.
Plug and Play & power
How devices appear, initialize, and change power state without manual kernel bookkeeping.
Storage & file systems
Disks, volumes, cache, and the file-system layers that make persistence usable.