7.1 Hyper-V Type 1 Architecture, Installation & Hardware Prerequisites

Hyper-V Type 1 Architecture, Installation & Hardware Prerequisites

Microsoft Hyper-V is an enterprise-grade, bare-metal virtualization platform built directly into Windows Server. This section establishes the foundation: the Type 1 bare-metal partition model, what the hypervisor actually owns versus what the parent partition owns, and the hardware prerequisites and installation paths the exam expects you to recognize. Virtual machine generations, Secure Boot, virtual TPM, Enhanced Session Mode, and the direct guest-access channels build on this model and are covered in section 7.2.

---

1. Hyper-V Type 1 Bare-Metal Hypervisor Architecture

Hyper-V uses a Type 1 (native/bare-metal) microkernelized hypervisor architecture. The hypervisor layer (hvix64.sys or hvax64.sys) loads directly on the physical processor before any operating system boots. It creates and manages isolated execution domains called partitions.

+-----------------------------------------------------------------------------------------+
|                         HYPER-V TYPE 1 HYPERVISOR ARCHITECTURE                         |
|                                                                                         |
|   +-----------------------------+          +--------------------------------------+     |
|   |       ROOT PARTITION        |          |      CHILD PARTITION (GUEST VM)      |     |
|   |    (Parent / Host OS)       |          |                                      |     |
|   |  - Windows Server 2022/2025 |          |  - Windows Server / Client / Linux   |     |
|   |  - Management Stack (WMI)   |          |  - Virtual Applications & Services   |     |
|   |  - Virtual Machine Worker   |          |                                      |     |
|   |    Processes (vmwp.exe)     |          |  +--------------------------------+  |     |
|   |  +-----------------------+  |          |  | Virtualization Service Clients |  |     |
|   |  | Virtualization Service|  |          |  | (VSCs: StorVSC, NetVSC, etc.)  |  |     |
|   |  | Providers (VSPs)      |  |          |  +--------------------------------+  |     |
|   |  +-----------+-----------+  |          +------------------+-------------------+     |
|   +--------------|--------------+                             |                         |
|                  |       ==================================   |                         |
|                  +====== |       VMBus (Shared Memory)    | ==+                         |
|                          ==================================                             |
|                                          |                                              |
|   +---------------------------------------------------------------------------------+   |
|   |                           HYPER-V HYPERVISOR LAYER                              |   |
|   |  - Partitions Isolation, vCPU Scheduling, SLAT/EPT Memory Virtualization        |   |
|   +---------------------------------------------------------------------------------+   |
|                                          |                                              |
|   +---------------------------------------------------------------------------------+   |
|   |                          PHYSICAL HARDWARE (x64 CPU, RAM, NIC, PCIe)            |   |
|   +---------------------------------------------------------------------------------+   |
+-----------------------------------------------------------------------------------------+

Core Architectural Components

1. Hypervisor Layer:

   • A thin layer of code that has direct, unmediated control over physical CPU scheduling, physical memory partitioning, and interrupt routing.
   • Enforces strict memory and compute isolation between partitions using hardware virtualization extensions (Intel VT-x / AMD-V) and Second Level Address Translation (SLAT).

2. Root Partition (Parent Partition):

   • The primary management partition created automatically when Windows Server boots with the Hyper-V role.
   • Runs the management operating system (Windows Server 2022/2025 Standard or Datacenter).
   • Controls physical hardware device drivers (storage controllers, physical network adapters, graphics adapters).
   • Hosts the Virtual Machine Management Service (vmms.exe) and spawns an isolated Virtual Machine Worker Process (vmwp.exe) for each running child VM.
   • Contains Virtualization Service Providers (VSPs) that service I/O requests from child partitions.

3. Child Partitions (Guest VMs):

   • Virtual execution environments instantiated by the root partition via the hypercall API.
   • Do not have direct access to physical hardware devices or the ability to manage other partitions.
   • Run guest operating systems (Windows Server, Windows Client, Linux distributions) containing Virtualization Service Clients (VSCs) (e.g., NetVSC for networking, StorVSC for synthetic storage).

4. VMBus (Virtual Machine Bus):

   • A high-speed, point-to-point, in-memory communications channel that interconnects child partitions directly to the root partition.
   • Avoids the substantial CPU overhead and latency of traditional hardware emulation by transferring requests and data buffers over partitioned shared memory.

---

2. Hyper-V Installation & Hardware Prerequisites

Before deploying Hyper-V in production, the physical server hardware must meet strict architectural criteria.

Hardware Prerequisites

Validating Hardware Prerequisites

# Validate Hyper-V hardware prerequisites via systeminfo
systeminfo.exe

# Look for the 'Hyper-V Requirements' section at the end of the output:
# VM Monitor Mode Extensions: Yes
# Virtualization Enabled In Firmware: Yes
# Second Level Address Translation: Yes
# Data Execution Prevention Available: Yes

# Alternative PowerShell query for firmware virtualization support
Get-ComputerInfo -Property HyperVisorPresent, CsHypervisorPresent, DeviceGuard*

Installing the Hyper-V Role via PowerShell

To install the Hyper-V role along with the PowerShell management module and Hyper-V Manager GUI console:

# Install Hyper-V role with all management tools and initiate an automatic restart
Install-WindowsFeature -Name Hyper-V -IncludeManagementTools -Restart

# Verify successful installation post-reboot
Get-WindowsFeature -Name *Hyper-V*

[!NOTE] On Server Core installations, -IncludeManagementTools installs the Hyper-V PowerShell module. The GUI Hyper-V Manager console (virtmgmt.msc) is excluded automatically since Server Core does not support desktop shell components.

---

Operational Validation After Installation

Treat systeminfo.exe differently before and after the role is active. On a prospective host, its Hyper-V Requirements list must report Yes for VM Monitor Mode extensions, firmware virtualization, Second Level Address Translation, and Data Execution Prevention. On a running Hyper-V host, the tool instead reports that a hypervisor has been detected and does not display the individual requirements; that message confirms the hypervisor is already loaded rather than indicating a failed prerequisite.

Installing only remote management tools does not require SLAT because that workstation is not loading the virtualization components or running guests. Installing the server role does require the hardware features and a restart. During that restart, the hypervisor loads first and the Windows installation that used to run directly on the hardware becomes the root partition. The root partition then supplies device drivers and the management stack, while the hypervisor continues to enforce CPU scheduling and memory isolation.

A final deployment check is software compatibility. VMware Workstation, VirtualBox, and similar products that expect exclusive control of the same processor virtualization extensions can fail to start guests or run unreliably while the Hyper-V hypervisor is active. Diagnose that symptom as hypervisor contention, not as a missing virtual switch or damaged guest disk.