Hyper-V Live Migration allows running virtual machines to move seamlessly between physical virtualization hosts without downtime or service interruption. During a live migration, the host system copies the virtual machine’s operational RAM pages across the network while the guest continues executing. On modern high-density hosts running multi-gigabyte or terabyte workloads, transferring uncompressed memory over standard Ethernet links can consume substantial network bandwidth and extend migration durations. In Windows 11 and Windows Server Hyper-V environments, administrators can dramatically accelerate migration throughput and optimize CPU and network utilization by configuring Hyper-V Live Migration Performance Options via PowerShell.
Understanding Hyper-V Live Migration Performance Options
Hyper-V provides three distinct performance transport mechanisms for transferring live virtual machine memory:
- TCP/IP (Standard): The baseline transport mechanism. Guest memory is copied directly across standard TCP sockets without data transformation. While universally compatible with any network adapter, it transfers raw memory pages, maximizing network bandwidth consumption.
- Compression (CPU-Accelerated): The source Hyper-V host uses idle CPU cores to compress memory pages before transmitting them across the network. The destination host uncompresses the stream upon receipt. In typical enterprise workloads, compression reduces the transferred payload by 50% to 70%, drastically cutting migration time over 1GbE and 10GbE networks.
- SMB (Server Message Block / SMB Direct): Transfers memory pages over SMB 3 protocol sessions. When paired with RDMA-capable (Remote Direct Memory Access) network interface cards (such as RoCE or iWARP), SMB Direct offloads memory replication entirely to network hardware, bypassing the host CPU stack and achieving line-speed memory transfer across 25GbE, 40GbE, or 100GbE fabrics.
Inspecting Current Live Migration Host Settings
To inspect the active migration configuration on your local Windows 11 Hyper-V host, launch an elevated PowerShell prompt (Run as Administrator) and execute Get-VMHost:
Get-VMHost | Select-Object VirtualMachineMigrationEnabled, VirtualMachineMigrationAuthenticationType, VirtualMachineMigrationPerformanceOption, MaximumVirtualMachineMigrations | Format-List
A typical default configuration appears as follows:
VirtualMachineMigrationEnabled : True
VirtualMachineMigrationAuthenticationType : Kerberos
VirtualMachineMigrationPerformanceOption : Compression
MaximumVirtualMachineMigrations : 2
The VirtualMachineMigrationPerformanceOption property indicates which transport algorithm the Hyper-V host applies during live migration routines.
Configuring Migration Performance Options with Set-VMHost
Administrators configure host-level migration properties using the Set-VMHost cmdlet. Selecting the optimal performance option depends on host hardware resources, network bandwidth, and adapter capabilities.
Enabling Compression for Bandwidth Optimization
In environments where network bandwidth is a bottleneck (e.g., standard 1GbE or 10GbE copper links) and modern multi-core CPUs have available spare capacity, Compression provides the fastest migration times:
# Set performance option to Compression
Set-VMHost -VirtualMachineMigrationPerformanceOption Compression
Hyper-V dynamically scales compression threads across host logical processors. If the host experiences high CPU contention, Hyper-V automatically throttles compression intensity to avoid starving running guest workloads.
Enabling SMB and SMB Direct (RDMA) for High-Speed Fabrics
If your virtualization cluster utilizes 25GbE, 40GbE, or 100GbE adapters equipped with RDMA support (RoCEv2 or iWARP), configure the host to use SMB:
# Set performance option to SMB Direct
Set-VMHost -VirtualMachineMigrationPerformanceOption SMB
With SMB selected, Hyper-V leverages SMB Multichannel and SMB Direct to stream memory with microsecond latency and negligible host CPU impact.
Restoring Standard TCP/IP Transport
If CPU resources are constrained and network hardware lacks RDMA capabilities, or when troubleshooting network packet filtering issues, revert to standard TCP/IP:
# Revert to standard TCP/IP socket transport
Set-VMHost -VirtualMachineMigrationPerformanceOption TCPIP
Configuring Live Migration Authentication Security
Alongside transport performance options, administrators must configure the authentication protocol used to secure live migration handshakes between hosts:
- Kerberos: Requires Kerberos constrained delegation configured in Active Directory. Prevents sending cleartext administrative credentials over the wire and avoids console sign-in restrictions.
- CredSSP: Easier to configure across standalone hosts or non-domain environments, but requires administrators to log in directly to the source Hyper-V console session.
To configure Kerberos authentication:
Set-VMHost -VirtualMachineMigrationAuthenticationType Kerberos
Tuning Concurrent Migration Limits and Subnets
To maximize migration throughput during cluster maintenance windows or hardware evacuations, adjust the maximum number of simultaneous live migrations permitted on the host:
# Allow up to 4 simultaneous live migrations
Set-VMHost -MaximumVirtualMachineMigrations 4
# Allow up to 4 simultaneous storage migrations
Set-VMHost -MaximumStorageMigrations 4
To verify that dedicated migration subnets are properly bound to the performance pipeline:
Get-VMMigrationNetwork | Select-Object Subnet, Priority
Validating Migration Performance
You can monitor migration throughput and duration by initiating a test migration between two configured hosts:
# Move running VM to target host
Move-VM -Name "Prod-SQL-01" -DestinationHost "HV-HOST-02"
Use Windows Performance Monitor (PerfMon) to observe the Hyper-V VM Vid Partition / Average Page Transfer Time and Network Interface / Bytes Total/sec counters during migration.
By leveraging PowerShell to configure Hyper-V Live Migration Performance Options, system administrators can align transport algorithms with available network fabrics and host CPU capacity, drastically reducing maintenance windows and ensuring resilient virtualization operations.