Network priority fallback configuration for live migration

Question

Experiencing intermittent packet loss on a dedicated live migration network is causing active VM migrations to abort, leaving target virtual machines in a critical, unrecoverable state. I need to configure migration network priority fallback paths using PowerShell. The goal is to ensure that when the primary migration network becomes unstable, the system automatically switches to a secondary path without interrupting ongoing migrations.

Is there an advanced PowerShell configuration or registry adjustment that can help stabilize Live Migration under these conditions? Windows Server environment ?

Answer 1

Hello,

Live Migration aborts under packet loss because the migration channel is bound to a single network path. When that path becomes unstable, the migration session cannot fail over mid‑stream. To stabilize this, you need to configure migration network priorities so that Hyper‑V uses multiple dedicated networks and automatically falls back when the primary path is degraded.

In Windows Server, this is done with PowerShell using Set-VMHost and Set-VMHostMigrationNetwork. First, enumerate all available migration networks with Get-VMHostMigrationNetwork. Then assign priorities:

powershell

Set-VMHost -VirtualMachineMigrationEnabled $true -VirtualMachineMigrationAuthenticationType CredSSP
Set-VMHostMigrationNetwork -NetworkName "LM-NIC1" -Priority 1
Set-VMHostMigrationNetwork -NetworkName "LM-NIC2" -Priority 2

Here, LM-NIC1 is the primary migration network, and LM-NIC2 is the fallback. Hyper‑V will attempt to use the highest priority network first, but if it becomes unavailable, it will switch to the next. This configuration does not interrupt ongoing migrations; the migration channel is re‑established over the secondary path.

There is no registry tweak required—Microsoft explicitly supports this via PowerShell. The key is to ensure both NICs are dedicated to migration traffic and not shared with cluster heartbeat or CSV traffic. Also confirm that QoS policies are not throttling SMB Direct, since Live Migration uses SMB over RDMA when available.

In practice, enabling multiple migration networks with explicit priorities is the only supported way to achieve seamless fallback. Registry changes to RPC or SMB timeouts will not prevent aborts under packet loss; only migration network redundancy ensures continuity.

I hope you've found something useful here. If it helps you get more insight into the issue, it's appreciated to accept the answer. Should you have more questions, feel free to leave a message. Have a nice day!

Domic Vo.

Answer 2

There is no supported advanced PowerShell or registry setting in the provided documentation that enables automatic in-flight Live Migration fallback from one migration network to another when the primary path becomes unstable.

Supported configuration focuses on:

1. Restricting or selecting which cluster networks Live Migration can use In Failover Cluster Manager:
   • Networks > Live Migration Settings
   • Check only the networks intended for Live Migration.
   In PowerShell, exclude specific networks from Live Migration:

      $VMResourceType = Get-ClusterResourceType -name "Virtual Machine"
      $ExcludedNetwork = Get-ClusterNetwork -Name "Cluster Network 1"
      $VMResourceType | Set-ClusterParameter -Name MigrationExcludeNetworks -Value $ExcludedNetwork.Id
   

   To allow only one named migration network, use:

      Get-ClusterResourceType -Name "Virtual Machine" |
        Set-ClusterParameter -Name MigrationExcludeNetworks -Value ([String]::Join(";",(Get-ClusterNetwork | Where-Object {$_.Name -ne "Migration_Network"}).ID))
   

2. Setting Live Migration network priority/order on Hyper-V hosts The Add-VMMigrationNetwork cmdlet supports a -Priority parameter for adding a migration network on one or more virtual machine hosts.
3. Using SMB as the Live Migration performance option consistently across cluster nodes

      $ClusterNodes = (Get-ClusterNode).name
      Set-VMHost -ComputerName $ClusterNodes -VirtualMachineMigrationPerformanceOption SMB
   

   This must be configured consistently on all cluster nodes.
4. Isolating Live Migration traffic from other cluster traffic Recommended network isolation for a Hyper-V failover cluster is:
   • Live migration: allow cluster network communication, but clear Allow clients to connect through this network.
   • Keep Live Migration traffic away from the cluster communication network by using Live Migration Settings.
5. Collecting diagnostics for packet loss or migration aborts Useful commands include:
   • Get-ClusterLog -UseLocalTime -Destination <Path>
   • Get-WinEvent -LogName "Microsoft-Windows-Hyper-V-VMMS/Admin"
   • Get-WinEvent -LogName Microsoft-Windows-Hyper-V-Worker-Admin
   • Get-NetAdapter
   • ipconfig /all

If migrations are aborting during packet loss, the supported path is to stabilize and isolate the migration networks, configure the allowed migration networks explicitly, and use SMB consistently across nodes. The provided documentation does not describe a registry-based fallback mechanism for seamless automatic switchover during an active migration.

---

References:

• Control Live Migration SMB Bandwidth control cluster-wide
• Troubleshooting guide: Hyper-V virtual machine live migration
• Network recommendations for Hyper-V in a failover cluster
• Add-VMMigrationNetwork