Windows & Linux · Hyper-V Lab · Hyper-V Overview

Hyper-V Overview

A structured breakdown of what Hyper-V is, how the hypervisor works, and how enabling it fundamentally transforms Windows into a root partition under a Type-1 virtualization framework.

What is Hyper-V?

Hyper-V is Microsoft's built-in virtualization platform that allows the creation and management of virtual machines (VMs) in Windows environments. It is similar in concept to VMware or Oracle VirtualBox, but uniquely integrated into the Windows operating system itself.

Hyper-V is included in:

  • Windows Server
  • Windows 11 Pro
  • Windows 11 Enterprise
  • Windows 11 Education

The Hyper-V technology is the hypervisor that powers the virtual infrastructure.

Hyper-V = Hypervisor

A hypervisor is a lightweight software layer that allows multiple operating systems to run simultaneously on the same physical hardware. This includes Windows, Linux, BSD, pfSense, and many more.

Hyper-V is always a Type 1 (bare-metal) hypervisor — even when installed on a laptop.

Runs Directly on Hardware — Regardless of the Host

Whether installed on a Dell or HP enterprise rack server, or a Lenovo ThinkPad running Windows 11, Hyper-V runs directly on the hardware layer — not inside the Windows operating system.

Windows Becomes the Root Partition

Once Hyper-V is enabled and the machine reboots, Windows is no longer the base operating system. It becomes the Root Partition (also called the Parent Partition).

Root Partition Responsibilities

  • Has direct access to hardware drivers
  • Manages storage and networking
  • Controls all child VMs
  • Runs Hyper-V Manager / PowerShell virtualization modules
  • Hosts virtual disk files (.vhdx)
  • Creates, deletes, and manages VMs
  • Owns the Virtual Switch Manager

Therefore, Windows serves as the management OS for the hypervisor — not the execution layer for the VMs.

VMs = Child Partitions

Each VM runs inside a Child Partition — an isolated execution environment controlled by the hypervisor.

Child Partition Characteristics

  • Do not have direct access to hardware
  • Must use the hypervisor for CPU, memory, storage, and I/O
  • Use synthetic drivers provided by the root partition
  • Are strictly managed by the hypervisor + root partition

Operating Systems That Run as Child Partitions

  • pfSense
  • Ubuntu
  • Windows Server
  • Kali Linux
  • Arch Linux

Microsoft uses the term "partition" instead of "VM" because the architecture is container-based at the hypervisor level.

How Hyper-V Changes System Architecture

Before Hyper-V

A Windows machine operates normally: Hardware → Windows → Applications

After Hyper-V is Enabled

The boot process changes dramatically: Hardware → Hyper-V Hypervisor → Windows (Root Partition)

Hyper-V takes over the virtualization extensions of the CPU and becomes the true base layer of the machine.

During Boot

  • The system reboots
  • The Windows bootloader loads hvboot.sys
  • The hypervisor initializes and takes control over hardware virtualization
  • Windows starts as a privileged partition

Why VMware and VirtualBox Stop Working

Hyper-V "owns" the CPU virtualization extensions (Intel VT-x / AMD-V). Because it's a Type-1 hypervisor, it does not allow other hypervisors to run beneath it.

This is why VMware Workstation and VirtualBox often fail to start once Hyper-V is enabled.

Lab Context

In this lab, Hyper-V is enabled and configured on a Lenovo ThinkPad running Windows 11 Professional. Enabling the feature transforms Windows into a root partition operating under the Hyper-V hypervisor. All virtual machines used in this lab run as child partitions.

← Back to Home