Today I want to talk to you about a problem while moving from Standalone Hyper-V to Hyper-V Cluster using Shared Nothing Live Migration in Windows Server 2012 R2 that I recently encountered.
As you already know, Shared Nothing Live Migration is a new functionality introduced in Windows Server 2012, that allows you to live migrate the virtual workloads in a non-cluster environment.
If you would like to know more, please have a look at:
Ok, so having this explained, I will go ahead and describe my problem. My environment consisted of 2 Hyper-V 2012 (Non-cluster) and 4 Hyper-V 2012 R2 (Cluster) with some virtual workloads split up between them. Let’s simply call them HV-01, HV-02, HV-03 and so on…
While I am upgrading my remaining Hyper-V Hosts from 2012 to 2012 R2, I couldn’t live migrate any virtual machine. The live migration between HV-02 (Non-cluster) To HV-03 (Cluster) failed.
When performing the live migration, I got:
Virtual machine migration operation failed at migration source.
Failed to establish a connection with host HV03: A connection attempt failed because the connected part did not properly respond after a period of time, or establish connection failed because connected host has a failed to respond. (0x8007274C)
The first thing I did, was to check if I could ping from HV02 to HV03 and back.
The second thing was to check if Live Migration on HV02 if checked in Hyper-V Settings. It was.
The third thing was to check if Live Migration on HV03 if checked in Hyper-V Settings. It was.
Did you see any difference between Hyper-V settings on HV02 and HV03?
The Incoming live migrations is set on HV02 to Use any available network for live migration, however on HV03 it is set to Use these IP addresses for live migration, therefore the live migration is failing.
Adjust the network subnet under Hyper-V settings on HV02 to match the Live Migration network on HV03 and here you go:
Hope this will help you if you encounter the same symptoms.
Enjoy your day!