Microsoft Hyper-V hypervisor overview

Hi! Well, Microsoft, we meet again.
Microsoft Hyper-V is the second largest hypervisor on the market (after ESXi). Particularly because of its integration into Windows Server (and Windows for PCs too). This article is going to be long and detailed, so a A cup/glass of something stronger wouldn't hurt - I'll try to cover the essentials, including licensing, system requirements, key features, and at the end I'll compare it to ESXi, KVM and Proxmox.

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

Hyper-V is a type 1 (Bare Metal) hypervisor from Microsoft. This type of hypervisor runs directly on the hardware, without first installing the host operating system. The structure is as follows: physical hardware → hypervisor → virtual machines (VMs) → guest operating systems. The hypervisor completely isolates the virtual machines from each other and emulates all the hardware, although it actually uses only a fraction of the server's physical resources. This allows multiple users to run virtual machines on the same server without knowing of each other's existence and without interfering with each other (different guest operating systems, different application software, etc.).

Type 1 hypervisor. 

Type 2 hypervisor.

If your server is designed to perform a single task, such as hosting a website, virtualization may be unnecessary (especially with paid software), but in many scenarios a hypervisor is justified because you can distribute different services across different isolated virtual machines. For example, mail server, file server, domain controller, application server. One server instead of four, with easy scaling, maintenance, and no conflicts. Sounds good? And you'll be able to tackle more complex tasks.

Hyper-V Licensing: How an administrator can stay on their toes

The Hyper-V hypervisor is tightly integrated into the Windows Server operating system and the Microsoft ecosystem as a whole. If you bought Windows Server, you bought Hyper-V, so this is the bundle we are going to look at. There is, of course, another option, which is to install the hypervisor as a separate piece of software, which is called "Hyper-V Server", without the GUI and additional Windows Server roles, but this is a rather niche solution (I will explain why later).

Seems simple, doesn't it? No, the devil is in the details.

It is the version of Windows Server that determines Hyper-V licensing. The wrong choice can cost large infrastructures hundreds of thousands of euros. Therefore, you should consider this issue carefully, especially if you are going to use virtualization with Windows guests.

We'll break down these three products:

To keep administrators on their toes, Microsoft introduced the terms Physical Operating System Environment (OSE) and Virtual OSE.

Physical OSE refers to the underlying "physical" Windows Server installed on a hardware server. And Virtual OSE refers to a virtual OS running in a virtual machine on the same hardware server.

When you buy Windows Server, you can install one physical OSE and some number of virtual OSEs on the same physical server. But how many is the main question, and the answer depends not only on the server capacity, but also on the edition of the system :) It's time to deal with Windows Server editions and licenses, but let's go through them in order.

• Windows Server Standard Edition - allows you to run up to two virtual OSEs (per license) and an unlimited number of containers, as long as the Physical OSE only manages virtual machines (provided you license all physical server cores, more on this later). But if you use the Physical OSE to run server roles other than Hyper-V (such as a file server), you lose the right to one of the virtual machines. Storage Spaces Direct and shielded virtual machines are not available in the Standard edition.

• Windows Server Datacenter Edition - does not limit you to deploying Virtual OSEs and containers on a single physical server (as long as all physical server cores are licensed). A great choice for data centers and cloud environments with a high degree of virtualization. Physical OSEs can be used for virtualization management (via Hyper-V) or other roles with no limit on the number of virtual OSEs. The only limitation is the physical capabilities of the host. "Data Center" has access to Host Guardian Service (HGS) and Storage Spaces Direct and Shielded Virtual Machines technologies

• Hyper-V Server is the Server Core version (a minimalistic installation of Windows Server, there is a smaller version called Nano Server that is used for containers). Server Core comes pre-installed with a Hyper-V role that is configured during installation. Best of all, Hyper-V Server is completely free. But Microsoft is not a charitable company: you'll have to pay for guest licenses (per license). If you use a lot of Windows virtual machines, this will cost a lot of money, so you need to see if it's cheaper to buy a paid Windows Server and run it. The most common use case for Hyper-V Server is a host running open source virtual machines, such as Linux-based VDI. You don't have to pay for such a bundle, only for the administrator's salary :)

Number of 2-core packages required for core processors.

Good Corporation has moved to kernel-based licensing starting with Windows Server 2016. That is, you have to buy a license not for the processor, as it used to be, but for its/their kernels.

• You must purchase a minimum of 8 Core licenses per physical processor (1 Core license covers 2 cores), even if you do not have an 8-core processor;

• A minimum of 16 cores must be licensed per server (in a single socket server too), even if you don't have 16 physical cores. Anything over 16 must also be licensed.

Now a question for the experts: How do I continue to use Windows Server Standard if I need more than two virtual OSEs?

A: License stacking - Windows Server Standard Edition OS License stacking.

Because Microsoft felt that the licensing model was not complex enough, they came up with stacking, also known as Windows Server Standard license stacking.

For example, on a host whose cores are triple covered by Windows Server Standard license, you can deploy up to six virtual OSEs on a single physical server (since each license entitles you to two virtual instances).

What's included in Hyper-V

Microsoft Hyper-V is a complex hardware virtualization software product with many components at its core. Together, they create a virtualization platform that allows administrators to make the most efficient use of server hardware resources.

• Hypervisor kernel. Compatible with 64-bit x86 systems. The kernel is responsible for creating, isolating and managing virtual machines. It virtualises the physical resources of the server: CPU, memory, network, storage, etc. The Hyper-V kernel runs at the lowest level - directly on the hardware.

• Virtualization Management Services (VSP, virtualization Service Provider). These services run in the parent operating system (hosted in the root partition) and provide virtual machines with access to physical resources.

• Virtual Devices (VDevs):
  Emulated devices. These software devices are created by the hypervisor and emulate (mimic) the functionality of real hardware at the software level. Emulated devices are created separately for each VM so that they can interact with the host system and other devices. Examples: network card (built-in network adapter), IDE ATA controller.

• Synthetic device drivers. Drivers within virtual machines that do not emulate real components but implement support for synthetic devices via the virtual machine bus (VMBus) - this is faster and more productive than emulation, as the drivers work directly with the hypervisor and leveling overheads. Examples: SCSI controller, HID (human interface device). But sometimes you need an emulated device, for example to run a guest OS without synthetic device support or for compatibility with older versions of software.
  

• Integration Services. A set of drivers and services that enhance the interaction between the physical host and virtual machines, improving performance and manageability.

• Hyper-V Manager, PowerShell, and VMConnect. Basic tools for managing virtual machines and Hyper-V resources using both the graphical user interface (GUI) and command line interface (CLI). Hyper-V Manager is a beginner-friendly option with all the functionality you need, while PowerShell Console is a more flexible and powerful option that allows you to automate operations, create scripts to configure and manage virtual machines, resources, networks, etc. VMConnect is a tool for connecting to VMs, which can be used to install and interact with the guest OS: turning on/off the VM, settings, connecting to a DVD image (.iso file) or a USB stick, and configuring access.

• Hyper-V Live Migration: This is a technology for moving virtual machines between Hyper-V hosts without interrupting the applications and services running on those virtual machines. This allows flexible resource management to improve system availability.

• Azure Hybrid Benefit: If you have a Windows Server subscription with Software Assurance, Azure Hybrid Benefit will allow you to use your licenses to run virtual machines in the Azure cloud at no additional cost.

So, it's time to discuss what equipment you need to make it all work properly.

Minimum system requirements for Microsoft Hyper-V on Windows Server

Let me make it clear that any virtualization system, including a hypervisor, consumes host resources. Therefore, the actual minimum system requirements for Hyper-V are slightly higher than for a Windows Server without the virtualization component enabled. Your hardware may not be suitable for newer technologies such as Storage Spaces Direct and Shielded Virtual Machines, so keep that in mind as upgrades cost money.

Key features of Microsoft Hyper-V

Hyper-V is designed for virtualization. With it, you can create and run virtual machines - that's the foundation. Importantly, each virtual machine runs as a complete server/PC/workstation, with its own OS and software, and they are all isolated from each other, including access control. This is a more efficient approach than running a single OS on a single server (especially in large IT infrastructures). In addition to the standard virtualization features, Hyper-V opens up other possibilities for administrators:

• Create or expand a private cloud environment. You can create a more flexible infrastructure and deploy IT services on demand, adjusting the use of shared server resources as workloads/needs change.

• Efficient use of hardware. Virtualization allows you to consolidate workloads on less and more powerful hardware that uses less power and takes up less space. And Hyper-V itself is well optimized for high performance in virtualized environments.

• HA (High Availability) and business process resiliency. Hyper-V minimizes planned and unplanned downtime for workloads. Clustering and migration of virtual machines ensures uninterrupted operation of applications even in the event of host failures.

• VDI (Virtual Desktop Infrastructure). Deploy Hyper-V and RD virtualization. Host on the same server to create personal virtual desktops or pools of virtual desktops for employees. This improves work flexibility, data security, and simplifies workspace administration.

• Increase development and testing efficiency. A great solution for rapid deployment and destruction of test environments. You can quickly deploy and create development work environments without having to buy and maintain additional physical hardware.

• Ease of Management: Hyper-V supports a convenient remote management interface (and more than one) that makes it easy to create, configure, and manage virtual machines and host resources.

A brief overview of the competitive advantages of Microsoft Hyper-V

For SMBs, Hyper-V is sufficient, but it has a huge share of the virtualization market, including the enterprise segment, for a reason. It is efficient and functional, cheaper than ESXi, all other things being equal; in some aspects it is inferior, in others it is superior. In any case, the choice should be made based on your budget and goals.

Integration with the ecosystem and other Microsoft products: One of Hyper-V's biggest advantages is its deep integration with other Microsoft products and services:

System Centre Virtual Machine Manager (SCVMM). It is an integrated set of virtualization tools that allows you to centrally manage a large number of virtual machines on Hyper-V as well as VMware ESXi 7 and 8 (starting with version 2022). Resource allocation, automation, migration and more.

Windows Administration Centre. A handy graphical user interface (GUI) application for managing local and remote Windows-based servers, including Hyper-V hosts. Designed to replace the command line (although it includes PowerShell), it can be managed through a web browser (Edge, Chrome).

Active Directory and other Windows services. Administrators can use Group Policy, Certificate Services, Identity Awareness, and other tools to control access to virtual machines and Hyper-V resources.

Windows Server Failover Clustering (WSFC). Hyper-V can be used with a WSFC cluster to provide high availability for virtual machines. This allows you to automatically migrate virtual machines (Live Migration) from one cluster node to another in the event of a hardware or software failure.

Cloud support: Hyper-V integrates with Microsoft Azure, so you can run virtual machines on your local network or in the cloud.

Cost: Hyper-V is usually cheaper than VMware vSphere, especially if you are already using Microsoft products. I know of cases where large companies have switched from ESXi to Hyper-V just to save money.

Flexibility and scalability: Hyper-V can be flexibly configured and scaled to adapt to changing requirements and workloads.

Security: VM isolation, access control, virtual traffic encryption, security updates and patches, role delineation, monitoring and auditing, integration with third-party security systems.

Excellent compatibility: Hyper-V works with many open standards and protocols, and Microsoft itself provides open APIs: Windows Management Instrumentation (WMI), Hyper-V Management API, Open virtualization Format (OVF), VHD, VHDX, TCP/IP, IPv6, VLANs, and others.

Microsoft Hyper-V usage scenarios

• Data centers and server rooms. Hyper-V is used in large enterprise environments for virtualization and efficient management of computing resources.

• Test environments with different configurations. With Hyper-V, you can easily create virtual machines with different hardware and software configurations to test application compatibility or performance in different environments.

• Azure Stack hybrid clouds. Azure Stack uses the Hyper-V hypervisor to virtualize resources. This allows companies to build their own hybrid cloud environments running on-premises or in private data centers. You can run Azure Public Services without (or with, if you prefer) an Azure Public Cloud.

• Desktop virtualization (VDI). Hyper-V is a common desktop virtualization solution. It makes it easy to manage upgrades, security and scaling of employee work environments.

• Build a reliable infrastructure. Hyper-V allows you to deploy Failover Clustering with high availability. The failure of a server (node) or multiple servers will not bring business processes to a halt, which is especially important for mission-critical infrastructures. This is especially important for mission-critical applications where even minutes of downtime can have serious consequences.

And that's just the tip of the iceberg. Essentially, you are limited not by Hyper-V capabilities, but by budget, hardware, and competencies. Any large IT infrastructure uses virtualization—not always Hyper-V, but still—if you have a small or medium-sized business, it's worth weighing the pros and cons. If a paid hypervisor is unreasonably expensive, consider Proxmox VE or KVM - they have their pros and cons, but they are free. More on that later.

Comparing Microsoft Hyper-V with other hypervisors

The comparisons will be brief, as detailed technical discussions require separate articles (Email me, I'll do it if you need me to). So, Hyper-V will be competing against ESXi, KVM and Proxmox VE. I will compare them in tables for your convenience.

Note. Guest operating systems (on which users run) cost money on all virtualization platforms. For example, KVM is free, but you have to pay for a guest system on a virtual machine.

Microsoft Hyper-V vs. KVM

KVM (Kernel-based Virtual Machine) is part of the Linux kernel, a hypervisor of the first type. KVM, like Linux, is free and open source software. It, of course, has its pros and cons Overall, KVM is a powerful and flexible hypervisor suitable for a wide range of tasks, especially in a Linux environment. However, it requires a certain level of expertise and is not suitable for all users due to its complexity and lack of official support. However, there is a huge and active community around KVM that is dedicated to support, development and helping newcomers.

Microsoft Hyper-V vs ESXi

       VMware ESXi is a Type 1 (Bare Metal) hypervisor that does not require an OS like Linux or Windows to run. It is based on VMware's own VMkernel. ESXi itself is a fairly complex but highly functional hypervisor and can be used standalone (e.g, for small businesses or simple test environments), but it is typically used as part of the VMware vSphere platform to handle a large number of hosts and virtual machines, allowing centralized management of the entire virtualized infrastructure. The vSphere platform also includes vCenter Server, vSphere Client (management interface), vSphere Update Manager, vSphere Management Assistant (vMA), and other tools and features.

Proxmox VE (Proxmox Virtual Environment) is an open and free virtualization platform based on KVM hypervisor and LXC (Linux Containers). In general, it can be classified as a type 2 hypervisor (but there is another opinion) as it runs on top of Debian, a Linux distribution. Additionally, Proxmox VE is quite a competitive product, especially for SMBs, as it allows you to run virtual machines and containers for free - with good flexibility, high performance and a user-friendly web interface for managing and monitoring virtualized environments. There are also built-in backup, migration and clustering tools. There are companies that deploy highly available and scalable clusters based on Proxmox VE.

General comparison of Hyper-V, ESXi, KVM and Proxmox VE hypervisors

Consider business objectives and budget when selecting a hypervisor. Then consider the competencies, capabilities and preferences of the organization and technical staff. Hyper-V is a great option if you are already running a Windows environment and/or want a cheaper option than ESXi. Enthusiasts who like to work with open source software and small businesses with smaller budgets can look at KVM and Proxmox VE. VMware ESXi is an option for medium to large organizations with a good budget and high requirements for virtualized environments.

Hyper-V - Functional and works well in Windows environments as it is integrated into Windows Server OS (but is also available separately), requires paid licensing if you need additional features.

ESXi - Probably the most extensive functionality, high reliability, requires a paid license, and it is expensive.

KVM - Free, open source, requires no third-party management tools or skills, and has a huge community.

Proxmox VE - Free, open source, web-based management (GUI), ZFS file system integration, large community, paid support.

In lieu of conclusions

Microsoft Hyper -V, as part of Windows Server is a reliable and stable virtualization solution with detailed documentation, extensive functionality and easy management. It is valued for its fair price, reliability, and flexibility.

I have covered the most important aspects of Hyper-V, but don't forget that it has other features as well. Servermall is always ready to help you choose the best servers for Hyper-V, we will take into account your needs, objectives and budget. Our service is fast and free, and we will send you a quote within an hour.