Live Migration Issues following Upgrades

Question

Hey,

Got a bit of a strange problem, hoping somebody else has come across it and has a fix.

So i had three Server 2016 Hyper V (call them HV01, HV02, HV03), all in a failover cluster, with a shard SAS SAN.

Took HV03 out the cluster and replaced it with a Server 2019 server, added it to the cluster with no issues in the validation report.

Not able to migrate VM to new host, so i upgraded the two 2016 boxes to 2019 (in place) upgraded the cluster level so now all servers on 2019, no issues with the validation report, all using intel processors and all VM settings in processors are set with compatibility ticked.

Not able to migrate VM from the upgraded 2016-2019 box to the new 2019 box, but i can migrate between the other to boxes with no issues, if i shut down a VM i can do a quick migration no problem to the new box and it will start and work perfectly fine, but i cant migrate it back then to the other two boxes

I have upgraded the configuration version to 9 and that doesn't make a difference.

Does anybody have any thoughts on the cause of this please, I'm thinking processor compatibility issues, but reading up Microsoft say so long as they are the same manufactures (they are all intel) then that shouldn't cause an issue.

Any help would be very much appreciated.

Thanks

Answer 1

Hello,

Hello, Is there any error message when you migrate? If so, please reply here. I suggest you open the event log to see if there is any related error message. You can also refer to the following link for troubleshooting:

Troubleshoot live migration issues - Windows Server | Microsoft Learn

Best Regards

Zunhui

Answer 2

Morning,

Many thanks for your response, there are minimal messages in the event log, it basically reports

Hyper-V_High-Availability Event ID:- 21502 - Live Migration of "" Failed

Hyper-V-VMMS Event ID:- 21026 0 Virtual machine migration operation for "" failed at migration destination

They give basic generic errors, nothing that when i have a search around gives any define reason why this would happen.

Thanks

Answer 3

Hi ,

I suggest you to try to change the live migration setting option to TCP on both source and destination side to see if it can solve the problem, refer to the following:

1. Open the Hyper-V Manager of both nodes.
2. Click hyper-V settings. expand Live migrations. select advanced features, and select TCP/IP in Performance options.

You can also try the method in the link I provided above.

Best Regards

Zunhui