Today, I want to talk to you about the problem of migrating from standalone Hyper-V to a Hyper-V cluster using the shared direct transfer feature in Windows Server 2012 R2 that I recently encountered.
As you already know, Shared Nothing Live Migration is a new feature introduced in Windows Server 2012 that allows you to migrate virtual workloads in real time in a cluster-free environment.
To learn more, check out:
Ok, so once this is explained, I will continue and describe the problem. My environment consisted of two Hyper-V 2012 (not a cluster) and 4 Hyper-V 2012 R2 (Cluster) and some virtual loads. Simply call them HV-01, HV-02, HV-03 and so on …
While upgrading the remaining Hyper-V servers from 2012 to 2012 R2, I couldn’t move any virtual machine in real time. The direct transition between HV-02 (no cluster) and HV-03 (cluster) failed.
When I made a direct transfer, I received:
Virtual machine transfer failed at transfer source.
Connection to host HV03 failed: The connection attempt failed because the connected part did not respond correctly after a certain time, or the connection failed because the connected host could not respond. (0x8007274C)
The first thing I did was check if I can ping from HV02 to HV03 and back.
Another thing was to check if Live Migration is on HV02 if logged in Hyper-V settings. It was.
The third thing was to check if Live Migration is on HV03 if logged in Hyper-V settings. It was.
Did you see any difference between them Hyper-V settings with devices HV02 and HV03?
Incoming direct transitions is set to HV02 Use any available network for live streaming, but with HV03 it is set to Use these IP addresses for real-time transmission, so live migration fails.
Adjust the network subnet in Hyper-V settings HV02 to match the Live Migration network with HV03, and here:
Hopefully this will help you if you experience the same symptoms.
Enjoy your day!