Microsoft Windows 2022 Server with 3 hosts with Hyper V and Cluster but Quick migration works but not Live

Question

We are running with 3 physical hosts with Windows 2022 Datacenter and a Lenovo SAN DE4000.

The physical hosts are identical, same physical specs, all drivers, bios,... are updated.

Hyper V and Cluster are setup on the servers. Running a Quick migration works without issue. However, Live migration failed.

Running a compare-vm return no error but Path, SnapshotPatch,... there is nothing, I mean it is empty.

Only the top 3 lines are filled.

Network management is used as well for the migration.

Did anyone have the same issue?

Answer 1

Hi,

To troubleshoot the live migration issue, you can follow these steps:

1. Check Virtual Switch Configuration: Ensure that the virtual switch used by the VM exists on all nodes and has the same name and settings. Open the Hyper-V Manager console, select Virtual Switch Manager, and verify the virtual switch configuration.

2. Verify Cluster Network Configuration: Ensure that the cluster network is configured correctly and that Allow cluster network communication on this network is selected. Run the following PowerShell cmdlet to check the cluster network:

Get-ClusterNetwork

Make sure the network is available for the operation.

3. Check Cluster Node Ownership: Verify that the specified cluster node is the owner of the group or a possible owner. Use the following PowerShell cmdlets to check the owner node:

Get-clusterResource -name "Virtual Machine VM1" | Get-clusterOwnerNode
Get-clusterResource -name "Virtual Machine Configuration VM1" | Get-clusterOwnerNode

Alternatively, use the Failover Cluster Manager to check the advanced policies and ensure all nodes are selected.

4. Firewall and Antivirus Settings: Ensure that the necessary TCP ports (6600 and 3343) are open and listening on both sides. Check the firewall settings and antivirus exclusions. Run the following cmdlet to check the ports:

netstat -ano | findstr /I /C:"6600"

5. Network Management: Ensure that the network management settings are correctly configured for migration. If using a stretched VLAN, ensure it includes all nodes of the cluster.

Answer 2

Hi Ian,

Thank you for the reply. See below answer:

1. Check Virtual Switch Configuration, yes we have same name and same on each HyperV server.

2. Verify Cluster Network Configuration, Result return with Cluster Network for all are up, different metric and different Role. See below:

Cluster Network 1 Up 70240 ClusterAndClient

Cluster Network 2 Up 30080 Cluster

Cluster Network 3 Up 79840 ClusterAndClient

3. Check Cluster Node Ownership, come back with error, see below:

PS C:\Windows\system32> Get-clusterResource -name xxxx | Get-clusterOwnerNode

Get-clusterResource : An error occurred opening resource 'xxxx'.

At line:1 char:1

• Get-clusterResource -name xxxx | Get-clusterOwnerNode

• 
      + CategoryInfo          : ObjectNotFound: (:) [Get-ClusterResource], ClusterCmdletException
  
      + FullyQualifiedErrorId : ClusterObjectNotFound,Microsoft.FailoverClusters.PowerShell.GetResourceCommand
  
  

Try as well with the VM Name between " and same result.

4. Firewall and Antivirus Settings: see below result from each host:

C:\Windows\system32>netstat -ano | findstr /I /C:"6600"

TCP 172.12.20.120:6600 0.0.0.0:0 LISTENING 3832

C:\Windows\system32>netstat -ano | findstr /I /C:"6600"

TCP 172.12.20.100:6600 0.0.0.0:0 LISTENING 3344

C:\Windows\system32>netstat -ano | findstr /I /C:"6600"

TCP 172.12.20.110:6600 0.0.0.0:0 LISTENING 3820

5. Network Management: yes, the management is the one used as well for migration.

Answer 3

Sorry about the point 3, it is showing the 3 Hypervisor as Owner nodes.