Microsoft Hyper-V Architecture Overview

Microsoft entered the virtualization field in 2003 by acquiring Connectix, the creator of Virtual PC, and subsequently released Virtual Server; with the later launch of Hyper‑V, Microsoft gained a prominent position in server virtualization.

Hyper‑V is a server‑level hypervisor comparable to VMware ESXi, supported since Windows Server 2008, managed through Hyper‑V Manager, and can be clustered using System Center VMM.

Microsoft provides several deployment options: a free Hyper‑V Server edition (limited features, no clustering), a full Windows Server installation with the Hyper‑V role, and a Server Core mode that strips the GUI for higher reliability.

The architecture differs from earlier Hybrid‑virtualization products; Hyper‑V uses a parent partition that offers services to child partitions. The Virtualization Service Provider (VSP) directly accesses hardware, the Virtual Service Consumer (VSC) runs inside the child partition, and VMBus connects VSP and VSC for each device.

Hyper‑V follows a microkernel design where only essential functions (process scheduling, memory management, inter‑process communication) run in kernel mode, while other services run as user‑mode processes, enhancing security and creating a lightweight system.

Virtual networking in Hyper‑V relies on VMBus and a virtual switch (vSwitch), providing three network types: private (VM‑to‑VM only), internal (VM‑to‑VM and VM‑to‑host), and external (VM‑to‑VM, VM‑to‑host, and VM‑to‑physical network).

The vSwitch offers features such as multi‑tenant isolation, VM Queue (VMQ), extensible SDN capabilities (e.g., OpenFlow, NIC teaming), and driver filtering via NDIS and Windows Filtering Platform.

SR‑IOV (Single Root I/O Virtualization) maps portions of a physical NIC directly to virtual machines, allowing VMs to access the NIC without passing through the vSwitch.

VMQ assigns a dedicated receive queue on the physical NIC to each VM, enabling the NIC to place incoming packets directly into the appropriate VM’s queue, reducing overhead.

The article concludes with a QR code inviting readers to follow the “ICT_Architect” public account for more content, followed by a commercial recommendation for a fashion store.