On another issue, here is what happened, I got Live Migration up and running 9 months ago on a two monster 24-CPU Servers, a couple of days ago I received a call from that same client saying that they have added another 2 monster nodes to the cluster so it’s now a 4-Node Cluster.

Everything was cool except for the new added nodes do not accept any Live Migrated VMs from the old ones and vice versa, so Node 1 and 2 are (kind of) working alone and Node 3 and 4 are doing the same.

Everything was healthy! the only event being logged in Event Viewer was completely useless (you gotta appreciate my honesty):

Event ID: 21502
Source: Hyper-V High Availability
’Virtual Machine %1’ Live Migration did not succeed at the source

OR

Event ID: 21502
Source: Hyper-V High Availability
’Virtual Machine %1’ Live Migration did not succeed at the destination

well, either way that wasn’t helpful, but it gives you a hint where to start looking, the source VM or the destination

This is what appears in the Fail-Over Clustering Console

So what could possibly be wrong? Well, it turned out to be a silly issue that had to do with the Virtual Network Adapter name being not IDENTICAL due to a typo (a dash in the name was forgotten!), check this post for a few things to keep in mind when creating a Live Migration cluster.

When Hyper-V attempted to migrate to the nodes I created (Node 1 and Node 2) from the newly added nodes (Node 1 and Node 2), it couldn’t find the same network card to match its configuration (which is something it validates before migrating).

after sorting this out, the issue was resolved

I hope this helps!