Microsoft Hyper-V hypervisor overview

Hi! Well, Microsoft, we meet again.

Microsoft Hyper-V is a Type 1 hypervisor whose current version is built into Windows Server 2025, as well as the Pro, Enterprise, and Education editions of Windows 11. It runs virtual machines directly on the Microsoft hypervisor, while Windows operates in a privileged management partition.

That detail matters. Hyper-V may look like an application installed inside Windows, but its architecture is not the same as that of a conventional Type 2 desktop hypervisor.

This article covers Hyper-V architecture, available products, Windows Server licensing, hardware requirements, clustering, storage, GPU virtualization and management. We will also look at situations in which Hyper-V makes sense—and those in which another platform may be a better fit.

What Is Microsoft Hyper-V: About the Hypervisor and Licences

Hyper-V is Microsoft’s hardware virtualization technology. It creates isolated virtual machines that can run Windows, Linux and other supported guest operating systems on the same physical server.

Is Hyper-V a Type 1 or Type 2 hypervisor?

Hyper-V is a Type 1 hypervisor.

When you enable the Hyper-V role, the hypervisor is loaded below Windows and communicates with the physical hardware. The installed Windows Server instance becomes the privileged root partition, sometimes called the management or parent partition. It provides device drivers, management services and access to physical I/O for the guest partitions.

The resulting architecture is approximately:

Physical hardware → Microsoft hypervisor → root and child partitions → guest operating systems

Type 1 hypervisor.

Type 2 hypervisor.

Therefore, it is correct to say that Hyper-V runs directly on the hardware, but the explanation should not stop there. The Windows interface visible to the administrator is the root partition, not a conventional host OS sitting underneath a Type 2 hypervisor. Microsoft describes this design in its Hyper-V architecture documentation.

Virtual machines are isolated from one another and receive virtual processors, memory, storage and network interfaces. The hypervisor schedules their access to the physical resources of the server.

Virtualization can consolidate services that would otherwise require several physical servers. A mail server, domain controller, file server and application server can run in separate VMs on one host. They remain logically isolated while sharing the same physical hardware.

However, virtualization is not automatically the right answer. If a small server performs one predictable task and does not require isolation, migration or rapid recovery, adding a hypervisor may only introduce more administration. The practical benefit appears when consolidation, high availability, testing, workload separation or flexible resource allocation justifies the extra layer.

Hyper-V options: Windows Server 2025, Windows 11 and Hyper-V Server 2019

The name “Hyper-V” now describes technology available through three different products:

• Hyper-V role in Windows Server 2025. This is the current option for production server virtualization. The role is available in Windows Server Standard and Datacenter. The chosen edition determines Windows Server virtualization rights and access to features such as Storage Spaces Direct and shielded VMs.

• Client Hyper-V in Windows 11. Hyper-V is included in Windows 11 Pro, Enterprise and Education. It is suitable for development, testing, demonstrations and local labs. It is not a replacement for a Windows Server failover cluster and does not grant Windows Server guest licences.

• Microsoft Hyper-V Server 2019. This is a separate, minimal, free virtualization product based on Windows Server technologies. It is not simply “Server Core with the Hyper-V role pre-installed.” Hyper-V Server 2019 was the final standalone release; Microsoft did not release Hyper-V Server 2022 or 2025. Its mainstream support ended on January 9, 2024, and extended support ends on January 10, 2029, according to the Microsoft lifecycle page.

The discontinuation of the standalone Hyper-V Server product does not mean that Hyper-V itself has been discontinued. Hyper-V remains an actively developed role in Windows Server 2025 and a component of other Microsoft virtualization platforms.

For a new production environment, Windows Server 2025 is normally the more sustainable choice. Existing Hyper-V Server 2019 deployments can continue to receive extended-support security updates, but they need a migration plan before January 2029.

Hyper-V Licensing: How an Administrator Can Stay on Their Toes

If you enjoy licensing documents, Microsoft provides plenty of reading. If you do not, here is the practical version.

The Hyper-V technology itself does not create guest operating system rights. Licensing depends on the product used for the host and on the operating systems running inside the VMs.

Windows Server 2025 core licensing

Windows Server 2025 Standard and Datacenter use core-based licensing. When licensing a physical server, you must license:

• all physical cores in the server;

• at least eight cores per physical processor;

• at least 16 cores per physical server.

Number of 2-core packages required for core processors.

Core licences are commonly sold in 2-core and 16-core packs. A 2-core pack contains licences for two cores; it is not a single licence that somehow covers two cores.

For example, a server with two 12-core processors has 24 physical cores. All 24 must be licensed. A single-socket server with six physical cores is still subject to the 16-core minimum.

Microsoft also permits per-VM licensing in specific subscription or active Software Assurance scenarios, subject to separate minimums. Because the applicable rights depend on the agreement and purchasing channel, organisations using that model should verify it against the current Windows Server 2025 licensing guidance.

Windows Server Standard virtualization rights

After all physical cores have been licensed, Windows Server 2025 Standard provides rights for two Windows Server operating system environments, or OSEs.

The physical Windows Server instance used as the Hyper-V host does not consume one of those two rights if it is used solely to host and manage the virtual machines. In that configuration, you can run:

• one physical Windows Server management environment; and

• up to two Windows Server virtual OSEs.

If the physical instance also runs unrelated application workloads, its licensing treatment changes because it is no longer used solely for virtualization management.

To run more Windows Server VMs, you can apply licence stacking. Each additional complete set of Standard core licences assigned to the server provides rights for two more Windows Server OSEs.

For example, fully licensing the server three times with Standard can provide rights for six Windows Server OSEs. Each stack must cover all physical cores and satisfy the applicable minimums.

Windows Server Datacenter virtualization rights

When all physical cores are licensed with Windows Server Datacenter, the host receives rights to run an unlimited number of Windows Server OSEs on that server.

“Unlimited” refers to licensing rights, not infinite physical capacity. The number of useful VMs is still limited by processors, memory, storage performance, networking, backup windows and failover capacity.

Datacenter also includes features unavailable in Standard, including:

• Storage Spaces Direct;

• shielded VMs;

• software-defined networking;

• unrestricted software-defined storage capabilities.

Licensing a Hyper-V cluster

A failover cluster does not create extra Windows Server virtualization rights.

Each host must have sufficient rights for the Windows Server workloads that may run on it. If a cluster can move ten Windows Server VMs onto one node during maintenance or failure, the licensing design must account for that possible placement—not only the normal distribution when every node is healthy.

At the same time, it is too broad to say that every node must always be licensed for every VM in every cluster. The result depends on:

• the maximum workloads permitted to run on each host;

• whether hosts are licensed by physical cores or by VM;

• Standard stacking or Datacenter rights;

• licence reassignment restrictions;

• Software Assurance or subscription benefits;

• failover, disaster recovery and cloud-migration rights.

Guest licences, CALs and Hyper-V Server 2019

Hyper-V Server 2019 does not include Windows Server guest rights. Even if the host hypervisor is free, running Windows Server virtual machines does not eliminate Microsoft’s licensing requirements. All physical cores on the host must be licensed, while the number of permitted Windows Server VMs depends on the edition: Standard provides rights for up to two virtual machines per fully licensed server, whereas Datacenter allows an unlimited number. The same rules apply when Windows Server runs on third-party hypervisors.

Linux guest operating systems normally do not require a Windows Server guest licence, although commercial Linux subscriptions, application licences and support contracts may still apply.

Windows Server Standard and Datacenter generally require Windows Server Client Access Licences for each user or device accessing server services, subject to the exceptions and terms of the applicable agreement. CALs are not purchased separately for every server: one User CAL allows a licensed user to access any number of licensed Windows Servers within the organisation, while one Device CAL provides the same right for a licensed device. Therefore, a company with 500 users who all require access would typically need 500 User CALs in total — not 500 CALs for each server. CALs must also be compatible with the Windows Server version in use. Remote Desktop Services and certain other functionality require additional licences.

Client Hyper-V in Windows 11 does not grant Windows Server guest rights either. A Windows Server VM running on a Windows 11 workstation must have its own valid licence.

Azure benefits

Azure Hybrid Benefit can reduce the Windows component of eligible Azure VM costs when you have qualifying Windows Server licences with active Software Assurance or a qualifying subscription.

It should not be described simply as “running Azure VMs at no additional cost.” Compute, storage, networking and other Azure services remain chargeable, and Standard and Datacenter have different concurrent-use and migration rights.

What’s Included in Hyper-V

Hyper-V is more than the small Hyper-V Manager window visible on an administrator’s desktop. Its main components and services include:

• Microsoft hypervisor. The lowest software layer, responsible for processor and memory virtualization, isolation and partition scheduling.

• Root partition. The privileged Windows partition that owns the virtualization stack, physical device drivers and management services. Microsoft recommends keeping production hosts dedicated to virtualization management instead of running unrelated application workloads there.

• Child partitions. Isolated environments in which guest operating systems run.

• VMBus. A high-speed communication channel between the root and child partitions.

• Virtualization Service Providers and Clients. Components that coordinate virtual I/O between the root partition and guest VMs.

• Synthetic devices. Virtual devices designed for efficient communication through VMBus. They usually provide lower overhead than legacy emulated hardware.

• Emulated devices. Compatibility-oriented virtual hardware used when a guest cannot use the preferred synthetic device.

• Integration Services. Drivers and services that improve time synchronization, shutdown, backup coordination, heartbeat monitoring and data exchange between host and guest. They are built into current supported Windows guests and many supported Linux distributions.

• VHD and VHDX virtual disks. VHDX is the preferred format for current deployments because it supports larger disks and provides better resilience than the older VHD format.

• Virtual switches. Software-defined network switches connecting VMs to external, internal or private networks.

• Checkpoints. Production checkpoints use guest-aware backup technology where supported; standard checkpoints capture VM state and are more appropriate for testing. Neither type should replace a proper backup.

• Live Migration and Storage Migration. Live Migration moves a running VM between compatible hosts. Storage Migration moves its files between storage locations with minimal service interruption.

• Hyper-V Replica. Asynchronous VM replication between hosts or sites for disaster recovery. It complements backup and clustering but does not replace either.

Hyper-V management tools

The current management stack includes several tools rather than one universal console:

• Hyper-V Manager for basic host and VM administration;

• VMConnect for console access to virtual machines;

• Failover Cluster Manager for clustered workloads;

• Windows Admin Center for browser-based server, VM and cluster administration;

• PowerShell for automation, repeatable configuration and management at scale;

• System Center Virtual Machine Manager 2025 provides centralised management, templates, fabric administration and orchestration for larger Microsoft environments. It is a separate System Center product, is not included with Windows Server or Hyper-V, and requires separate licensing.

Azure Arc can add inventory, policy and selected hybrid management services to Windows Server. Azure Local is a separate hyperconverged platform built around Microsoft technologies; it is not merely a new name for ordinary Windows Server Hyper-V.

Minimum System Requirements for Microsoft Hyper-V on Windows Server

The official minimum is straightforward. A Hyper-V host requires:

• a 64-bit processor with second-level address translation, or SLAT;

• VM Monitor Mode extensions;

• hardware-assisted virtualization, such as Intel VT-x or AMD-V, enabled in UEFI or BIOS;

• hardware-enforced Data Execution Prevention, using Intel XD or AMD NX;

• at least 4 GB of RAM for the host.

Before enabling the role, run:

systeminfo.exe

On a system where the hypervisor is not already running, the Hyper-V Requirements section should report that the required capabilities are available. You can also inspect them through PowerShell:

Get-ComputerInfo -Property "HyperVRequirement*"

If Windows reports that a hypervisor has already been detected, the individual requirement values may no longer be displayed because the system is already running above Hyper-V.

Minimum requirements vs production sizing

A production host also needs:

• memory for the root partition, all active VMs and operational reserve;

• NUMA-aware processor and memory planning;

• enterprise or otherwise vendor-supported storage;

• redundant network paths and power supplies;

• supported server firmware, storage controllers, NICs and drivers;

• enough spare capacity to absorb a host failure;

• backup resources and a tested recovery process.

CPU core count alone is not a useful sizing method. A lightly loaded domain controller and a busy database VM can have the same vCPU count but completely different memory, latency and storage requirements.

The Best Server for Virtual Machines guide covers CPU, memory, storage and form-factor selection in more detail.

Maximum scale vs realistic sizing

Windows Server 2025 significantly raises Hyper-V’s technical ceilings. Microsoft lists the following limits in its Windows Server 2025 feature documentation:

These figures are engineering limits, not recommended configurations. Most environments should scale according to measured workload demand, fault domains and recovery objectives rather than trying to approach the maximum values.

Key Features of Microsoft Hyper-V

Hyper-V’s core purpose has not changed: it creates and runs isolated virtual machines. Windows Server 2025 adds several useful capabilities without turning Hyper-V into a different product.

What’s new in Windows Server 2025

The most relevant Hyper-V changes include:

• GPU partitioning, or GPU-P. A compatible physical GPU can be divided into partitions assigned to multiple VMs. Windows Server 2025 also adds live migration support for GPU-P VMs under supported configurations.

• Workgroup cluster Live Migration. Workgroup clusters existed before Windows Server 2025, but Windows Server 2025 adds Live Migration for clusters whose nodes are not joined to an Active Directory domain.

• Dynamic processor compatibility. For supported clustered VMs, Hyper-V can calculate a common processor feature set across hosts. This can make migration between different CPU generations less restrictive than the previous fixed compatibility mode.

• Higher scale limits. Hosts support up to 2,048 logical processors and up to 4 PB of memory on systems with 5-level paging. Generation 2 VMs support up to 2,048 virtual processors and 240 TB of memory.

• Generation 2 by default. Hyper-V Manager now selects Generation 2 when creating a new VM. Generation 1 remains relevant mainly for legacy guest and boot requirements.

Storage for Hyper-V

Hyper-V supports several storage designs:

• local SAS, SATA or NVMe storage for standalone hosts;

• Fibre Channel or iSCSI SAN storage;

• SMB 3 file shares for VM configuration and VHDX files;

• Cluster Shared Volumes for coordinated access by failover-cluster nodes;

• Storage Spaces Direct for software-defined storage built from drives installed in cluster nodes.

Storage Spaces Direct requires Windows Server Datacenter. It can support hyperconverged deployments, where the same nodes provide compute and storage, or converged designs with separate storage and compute roles.

For production use, storage selection should account for latency, IOPS, throughput, controller cache, disk endurance, multipathing and failure domains. A redundant array does not eliminate the need for backup, and a cluster does not protect against accidental deletion, ransomware or corrupted application data.

Networking and high availability

A basic Hyper-V virtual switch can connect VMs to the external network, to the host or only to one another. Production designs may additionally use:

• VLAN isolation;

• Switch Embedded Teaming;

• SR-IOV for supported high-performance network adapters;

• quality-of-service policies;

• dedicated or logically separated management, storage, cluster and Live Migration traffic;

• redundant NICs, switches and upstream paths.

Failover Clustering provides high availability by restarting or moving VMs between nodes. Cluster Shared Volumes, SMB-based storage or another supported shared-storage design keeps VM data accessible from the destination node.

Live Migration reduces planned downtime, but a VM affected by a sudden host failure normally has to restart on another node. That is different from fault tolerance with uninterrupted processor state.

Capacity planning must leave enough CPU and memory reserve for the expected failure scenario. A two-node cluster operating both nodes near full capacity has nowhere useful to restart its VMs when one node fails.

GPU virtualization: GPU-P and DDA

Hyper-V provides two distinct GPU assignment models.

GPU partitioning (GPU-P) divides a supported physical GPU between several VMs. It is useful for VDI, graphics and selected AI or inference workloads that do not require an entire GPU per VM.

Discrete Device Assignment (DDA) passes a complete compatible PCIe device directly to one VM. The host cannot use that device while it is assigned. DDA is appropriate when the guest requires direct access to the full GPU, but it reduces sharing flexibility.

Compatibility is not automatic. Before choosing either option, verify:

• the server CPU, motherboard and IOMMU capabilities;

• UEFI settings such as SR-IOV and VT-d or AMD-Vi;

• the exact GPU model;

• host and guest driver versions;

• guest operating system support;

• GPU vendor licensing;

• cluster and Live Migration requirements.

GPU-P is available for standalone Windows Server 2025 hosts, including Standard under supported conditions. Clustered high availability for GPU-P workloads requires Windows Server 2025 Datacenter. Clustered DDA with GPU pools also has Datacenter and hardware-homogeneity requirements.

Security and recovery

Hyper-V supports Secure Boot for compatible Generation 2 guests, virtual TPM, VM isolation, encrypted migration traffic and integration with Windows security controls.

Shielded VMs provide stronger protection against compromised fabric administrators by using Host Guardian Service and virtual TPM technologies. The complete shielded-VM host capability is a Datacenter feature; it should not be presented as a general Standard-edition function.

For recovery, distinguish between:

• Failover Clustering for local high availability;

• Hyper-V Replica for asynchronous replication;

• backup for recoverable historical copies;

• application-level replication for workload-aware availability.

Using all four may be appropriate for a critical service, but each solves a different problem.

Microsoft Hyper-V Usage Scenarios

Hyper-V is particularly well suited to Microsoft-heavy environments, but that is not its only use.

When Hyper-V is the right choice

Consider Hyper-V when:

• most guest workloads run Windows Server;

• the organisation already uses Active Directory, PowerShell or System Center;

• Windows Server Datacenter guest rights align with a dense VM environment;

• administrators already have strong Windows Server skills;

• Failover Clustering and Microsoft management tools match existing operations;

• the environment needs supported Windows and Linux virtual machines;

• Azure Arc, Azure services or Azure Local are part of the wider hybrid strategy.

Common scenarios include:

• consolidating application, file, database and infrastructure servers;

• creating development and test environments;

• hosting Remote Desktop Services or VDI components;

• providing highly available VMs in server rooms and data centres;

• running branch-office services;

• building isolated labs on Windows 11 client systems.

When Hyper-V may not be the right choice

Another platform may be more practical when:

• the operations team is Linux-first and has little Windows administration experience;

• the required hardware, GPU or drivers are not supported;

• the organisation wants an integrated open-source virtualization and container platform;

• an existing backup, HCI or management ecosystem is designed around another hypervisor;

• Windows guest rights provide little financial value because nearly all workloads use Linux;

• the migration cost would exceed the operational benefit.

Do not compare licence price alone. Include management, backup, monitoring, staff skills, migration work, downtime, hardware compatibility and the cost of changing operational procedures.

Migration checklist: VMware or older Hyper-V to Windows Server 2025

1. Inventory the environment. Record VM operating systems, firmware type, virtual disks, snapshots, networks, storage dependencies, passthrough devices and application owners.

2. Check guest support. Confirm that every guest OS and application is supported on the intended Hyper-V version.

3. Design the destination. Map compute, storage, virtual switches, VLANs, IP addressing, backup and monitoring before converting anything.

4. Choose the conversion path. VMware virtual disks normally need conversion to VHDX. Remove or replace hypervisor-specific guest tools and verify boot mode, storage drivers and network configuration.

5. Review older Hyper-V VMs. Check configuration versions, Generation 1 dependencies, checkpoints, integration services and processor compatibility before upgrading VM configuration.

6. Validate backup and recovery. Create an application-consistent backup and prove that it can be restored independently of the source hypervisor.

7. Run a pilot. Migrate a representative non-critical workload and test boot, network access, performance, backup, monitoring and application behaviour.

8. Define rollback. Keep the original VM and data unchanged until the destination has passed acceptance testing. Document the exact point after which changes can no longer be rolled back without data reconciliation.

9. Migrate in controlled groups. Avoid converting the entire estate in one maintenance window.

10. Recheck licensing. Validate Windows Server, CAL, application and management licences against the final cluster placement.

Comparing Microsoft Hyper-V with Other Hypervisors

The short answer is that Hyper-V is strongest when Windows integration and Windows Server guest rights matter. VMware offers a mature commercial ecosystem; Proxmox VE combines KVM and LXC in an integrated platform; raw KVM offers flexibility but requires a Linux management stack and the expertise to operate it.

For a deeper comparison of licensing, hardware compatibility, clustering, backup and migration, see Which Hypervisor to Choose?.

Guest operating system and application licensing applies independently of the hypervisor. A free host platform does not make a commercial Windows, database or enterprise application licence free.

Microsoft Hyper-V vs KVM

KVM is built into the Linux kernel and is usually combined with QEMU, libvirt and management software. It is a powerful open-source virtualization foundation rather than a complete, single-vendor management product.

Raw KVM does require Linux knowledge and a management stack. Administrators must select and operate the tools used for clustering, storage, networking, backup and monitoring.

Proxmox VE is a separate ready-to-use platform built around KVM for virtual machines and LXC for containers. It adds a web interface, cluster management, software-defined storage integrations and backup tooling. It should not be confused with raw KVM, and it is not accurate to dismiss it as a conventional Type 2 desktop hypervisor merely because its host environment is based on Debian.

Hyper-V is usually easier to integrate into an established Windows estate. KVM can be more natural for Linux-focused teams that already operate open-source infrastructure tools.

Microsoft Hyper-V vs ESXi

VMware’s enterprise virtualization products use the ESX/ESXi architecture and are commonly deployed through the vSphere and VMware Cloud Foundation ecosystem.

The important comparison is no longer “free ESXi versus paid Hyper-V.” Organisations should compare the current VMware subscription bundle, management components, hardware compatibility, backup integrations and migration terms with the complete Windows Server and System Center design.

Hyper-V may provide attractive economics when Windows Server Datacenter guest rights are already required. VMware may remain the easier operational choice where the existing estate, staff skills, automation and third-party products are deeply tied to VMware.

Neither answer can be reduced to a single licence price.

General Comparison of Hyper-V, ESXi, KVM and Proxmox VE Hypervisors

The right choice depends on more than the hypervisor kernel. Evaluate the complete platform: hardware compatibility, high availability, storage, networking, backup, security, monitoring, support and the skills of the people who will operate it.

FAQ

Is Hyper-V a Type 1 or Type 2 hypervisor?

Hyper-V is a Type 1 hypervisor. After the role is enabled, the Microsoft hypervisor loads below Windows. Windows operates in the privileged root partition and manages virtual machines and device access.

Is Microsoft Hyper-V free?

Client Hyper-V is included in eligible Windows 11 editions. Hyper-V Server 2019 was a free standalone product, but it does not include Windows Server guest rights and is now in extended support. Current server deployments normally use the Hyper-V role in licensed Windows Server 2025.

Is Hyper-V Server 2019 the same as Windows Server Core?

No. Hyper-V Server 2019 is a separate standalone product based on Windows Server technologies. Server Core is an installation option for Windows Server Standard and Datacenter.

How many VMs can Windows Server 2025 Standard run?

After all physical cores are licensed, Standard provides rights for two Windows Server OSEs. Additional complete Standard licence stacks provide rights in increments of two. Hyper-V can technically run other properly licensed guest operating systems, including Linux, but host capacity remains finite.

Does Windows Server Datacenter include unlimited VMs?

It provides unlimited Windows Server virtualization rights on a host whose physical cores are fully licensed with Datacenter. It does not remove hardware limits or licensing requirements for SQL Server, Remote Desktop Services and other separately licensed products.

Can Hyper-V run Linux?

Yes. Hyper-V supports multiple Linux distributions. Confirm the specific distribution and version against Microsoft’s supported guest list, especially when vendor support is required.

Does a Hyper-V cluster replace backup?

No. Clustering protects service availability after a host failure. It does not preserve historical versions or protect against deletion, guest corruption and every ransomware scenario. Use independent, tested backups.

Should an existing Hyper-V Server 2019 deployment be migrated now?

It does not require an emergency replacement if it is secure, supported and meeting operational requirements. However, extended support ends on January 10, 2029, so the replacement or migration should be planned and tested well before that date.