[Complete Guide] How to Perform VM Live Migration Hyper-V

Does Hyper-V support live migration?

Yes, Hyper-V fully supports live migration. Since its introduction in Windows Server 2008 R2, it has become a fundamental feature for administrators managing high-availability environments.

At its core, Live Migration is the process of moving a running VM from one physical Hyper-V host to another without any perceived downtime. The VM stays powered on throughout the transition, so network connections remain active and applications keep running uninterrupted.

To understand its value, it helps to distinguish it from other migration methods:

• Live Migration: The VM stays running. Memory and state are synchronized between hosts before the final cutover, with no interruption to end users.
• Quick Migration: The VM is briefly paused and its state is saved to disk before being resumed on the destination host. This results in a short period of unavailability.
• Cold Migration: The VM is fully shut down, its files are moved to the destination, and then it is powered back on. This involves the longest downtime of the three.

For IT teams, this means hardware maintenance, load balancing, and energy optimization can all happen during business hours — without any impact on running workloads.

How Hyper-V Live Migration Works

When a migration is triggered, Hyper-V copies the VM’s memory pages to the destination host in the background while the VM keeps running. It then tracks any pages modified during the transfer, known as “dirty pages”, and copies them in iterative passes.

Once the remaining data is minimal, the VM is paused for under 100 milliseconds for the final cutover, then resumes on the destination host. A Gratuitous ARP message is broadcast to update the network switch with the VM’s new physical location.

The Role of Integration Services

Hyper-V Integration Services facilitate communication between the guest OS and the hypervisor during the handoff. They ensure hardware references and clock synchronization are handled correctly, without requiring a reboot or manual intervention.

What Affects Migration Duration

The biggest factor is VM memory size. The more RAM allocated, the more data need to cross the network during the transfer. Available bandwidth on your dedicated migration network is the second most critical variable.

3 Types of Hyper-V Live Migration

Not every migration scenario is the same. Hyper-V provides three distinct methods to move virtual machines, depending on whether you are using a cluster, shared storage, or standalone servers.

1. Shared Live Migration (Clustered)

This is the traditional method used in high-availability environments. It requires a Failover Cluster and shared storage, such as a Storage Area Network (SAN), iSCSI, or SMB 3.0 file share.

• How it works: Because both hosts have access to the same storage via a Cluster Shared Volume (CSV), only the VM’s memory and execution state are transferred across the network.
• Advantage: Since the virtual hard disks never move, migrations are fast and network overhead is minimal.
• Cross-cluster migration: Starting with Windows Server 2019, live migrations can be performed between different clusters, which is useful when upgrading hardware or consolidating data centers.

2. Shared-Nothing Live Migration

Introduced in Windows Server 2012, shared-nothing live migration allows a running VM to move between two Hyper-V hosts with no common storage or cluster membership.

• How it works: Hyper-V replicates the VM’s virtual hard disks over the network to the destination host while simultaneously synchronizing memory. Once both sides are in sync, the VM switches over to the destination.
• Advantage: VMs can be moved between standalone servers over a standard network connection, making this a practical option for smaller environments or unplanned maintenance.

3. Storage Live Migration

Storage Live Migration moves a VM’s virtual hard disks from one storage location to another while the VM stays powered on.

• How it works: Only the VHDX files are relocated. The VM continues running on the same physical host, with no impact on CPU or memory.
• Advantage: This is well-suited for moving a VM to faster storage, such as an SSD array, or for freeing up a volume that is running low on space — without any service interruption.

Hyper-V Live Migration Step-by-Step Setup Guide

Setting up live migration successfully depends on getting your infrastructure configuration right before the first migration runs. A single mismatch — such as a misnamed virtual switch — is one of the most common causes of migration failure.

Prerequisites & Requirements

• Hardware: Both hosts should run the same CPU generation. If CPU versions differ, enable Processor Compatibility Mode in the VM settings.
• Operating System: Windows Server 2012 R2 or later. On Windows Server 2025, Credential Guard is enabled by default — use Kerberos instead of CredSSP.
• Permissions: Hyper-V Administrators group membership on both hosts. Kerberos Constrained Delegation setup requires Domain Administrator rights.
• Networking: A dedicated 10GbE NIC or faster is recommended to keep migration traffic separate from production traffic.
• Virtual Switch Names: Switch names should match exactly on both hosts — for example, both using “Production-Switch”.
• Performance Options: Hyper-V supports three transfer protocols — TCP/IP (standard), Compression (lower bandwidth), and SMB Direct (for RDMA-enabled networks).

Step-by-Step Setup

1. Enable Live Migration in Hyper-V Settings

Both the source and destination hosts need to be configured to allow live migrations before any VM can be moved.

1. 1. Open Hyper-V Manager.
   2. In the Actions pane, click Hyper-V Settings.
   3. Select Live Migrations from the left menu.
   4. Check Enable incoming and outgoing live migrations.
   5. Under Authentication Protocol, select Kerberos — recommended for security and ease of use.
   6. Under Incoming Live Migrations, select Use these IP addresses to restrict migration traffic to your dedicated migration network.

2. Configure Kerberos Constrained Delegation (Recommended)

Kerberos Constrained Delegation tells Active Directory that your Hyper-V hosts are authorized to delegate credentials to each other for migration purposes.

1. 1. Open Active Directory Users and Computers.
   2. Locate the source host’s Computer Account, right-click it, and select Properties.
   3. Go to the Delegation tab and select Trust this computer for delegation to specified services only.
   4. Select Use Kerberos only.
   5. Click Add, then Users or Computers, and enter the name of the destination host.
   6. From the service list, select both Microsoft Virtual System Migration Service and cifs.
   7. Repeat these steps for the destination host’s computer account, targeting the source host this time.

3. Performing Live Migration via Hyper-V Manager

1. 1. In Hyper-V Manager, right-click the running VM and select Move.
   2. In the Move Wizard, select Move the virtual machine.
   3. Enter the Destination Name of the target host.
   4. Select the appropriate Move Option — for example, “Move all data to a single location” for shared-nothing migrations.
   5. Click Finish to start the migration.

4. Performing Live Migration via PowerShell

For bulk migrations or automation, the Move-VM cmdlet is the most efficient approach.

To move a VM and its storage to another host:

Move-VM -Name "FileServer01" -DestinationHost "HV-HOST-02" -IncludeStorage -DestinationStoragePath "D:\VMs\FileServer01" 

To move a VM within a cluster where storage is shared:

Move-VM -Name "WebServer01" -DestinationHost "HV-HOST-02" 

5. Live Migration with Failover Cluster Manager

1. 1. Open Failover Cluster Manager.
   2. Click Roles and select the VM you want to move.
   3. In the Actions pane, click Move, then Live Migration, then Select Node.
   4. Choose the destination node and click OK.

Hyper-V Live Migration vs VMware vMotion

When evaluating live migration options, the natural comparison is between Hyper-V and VMware vMotion. Both technologies move running VMs without downtime, but they differ in implementation, cost, and management overhead.

Key Differences in Management

The most significant difference lies in the management layer. VMware requires vCenter Server for vMotion to function. Hyper-V, by contrast, can perform a shared-nothing live migration between two standalone hosts using only Hyper-V Manager, though Failover Cluster Manager is the standard tool for larger deployments.

Hyper-V also places more responsibility on the administrator to maintain network consistency. If virtual switch names do not match exactly on both hosts, the migration will fail. VMware abstracts much of this complexity through Distributed Virtual Switches (vDS), which makes configuration less error-prone across large environments.

On simultaneous migrations, Hyper-V offers more flexibility. VMware caps concurrent vMotions at 8 per host to protect network performance, while Hyper-V lets administrators configure the limit based on available hardware and bandwidth.

Simplify Hyper-V VM Migration with i2Migration

Native Hyper-V live migration works well within Windows environments, but it has its limits. Cross-platform migrations, heterogeneous hardware, and large-scale data center transitions often require more than what built-in tools can offer.

For organizations that need a more flexible and reliable migration solution, i2Migration provides a unified platform built for complex enterprise environments.

Key Features of i2Migration

1. 1. • Zero-Downtime Migration: i2Migration uses a combination of block-level and file-level replication to migrate entire systems without interrupting production workloads — no scheduled maintenance windows required.
      • Cross-Platform Support: Supports physical-to-virtual, virtual-to-virtual, and physical-to-cloud migrations across heterogeneous environments, including local servers, VMware, and public cloud platforms.
      • Hardware-Agnostic Migration: Handles migrations across different hardware generations and server models. Supports BIOS-to-UEFI conversion and automatic driver injection to ensure the system boots successfully after migration.
      • Unstructured Data Migration: Moves large-scale NAS and file-based data with built-in integrity validation using hash comparison and byte-level verification — ensuring nothing is lost or corrupted in transit.
      • Secure Data Transfer: All transfers are protected with AES or SM4 encryption, with support for bandwidth control, compression, and resume-from-breakpoint to handle long-distance or unstable network conditions.
      • Built-in Validation: End-to-end dataset verification with automatic correction, rollback support, and point-in-time recovery ensures data integrity throughout the migration process.

Hyper-V live migration is a powerful built-in tool, but it is designed for Windows-centric environments with consistent infrastructure. When migrations span different platforms, legacy systems, or large volumes of unstructured data, i2Migration by Info2soft provides the flexibility, security, and validation that native tools lack.

FAQ

Q1: Can Hyper-V live migration work without a cluster?

Yes. Shared-nothing live migration allows you to move a running VM between two standalone Hyper-V hosts with no shared storage or cluster membership required. Both hosts need to be on the same domain and have live migration enabled in Hyper-V Settings.

Q2: Can Hyper-V live migration be enabled only on a domain-joined computer?

Not necessarily. Live migration between standalone hosts can use CredSSP authentication without a domain, but this is less secure and requires credential delegation to be configured manually. For most enterprise environments, domain membership with Kerberos authentication is the recommended approach.

Q3: What is the difference between live migration and quick migration?

Live migration keeps the VM running throughout the process by synchronizing memory before the final cutover, resulting in no perceived downtime. Quick migration pauses the VM, saves its state to disk, and resumes it on another node, resulting in a brief service interruption. Quick migration is only available in clustered environments.

Q4: How to enable Hyper-V live migration?

Open Hyper-V Manager, go to Hyper-V Settings, and select Live Migrations. Check Enable incoming and outgoing live migrations, choose your preferred authentication protocol, and specify the network interfaces to use for migration traffic. Both the source and destination hosts need to be configured this way.

Conclusion

Hyper-V live migration is a mature and capable feature that allows IT teams to move running VMs between hosts without service interruption. Whether you are using shared storage in a clustered environment, migrating between standalone servers with shared-nothing live migration, or relocating virtual disks with storage live migration, Hyper-V provides a method to fit most infrastructure scenarios.

Getting it right comes down to preparation — compatible hardware, consistent network configuration, and the right authentication setup will determine whether migrations run smoothly or fail at the first attempt.

For environments that go beyond Windows-native infrastructure, or where cross-platform flexibility, automated validation, and heterogeneous hardware support are needed, a dedicated solution like i2Migration can fill the gaps that built-in tools leave behind.