I'm working on upgrading our 10-node Windows 2019 Hyper-V cluster to 2022. I started the process by evicting one node and successfully upgraded its OS to 2022. After adding it back to the cluster, I encountered a warning about the mixed OS versions, which I expected, but the cluster validation passed without problems. The real issue is that live migration of VMs has stopped functioning entirely; it fails to migrate to the new 2022 node and even back to the other existing 2019 nodes. I found that removing the 2022 node resolves the migration issue. The shared storage is accessible on the new node, and the network settings are consistent across all nodes, so I'm at a loss for what else to investigate. The error displayed is a standard live migration failure with no error code. Any insights or suggestions for troubleshooting would be appreciated!
3 Answers
Last year, we did a similar upgrade and had no problems migrating. Might be worth reviewing how your cluster is set up compared to ours.
I’m not much help either, but from what I remember, having different OS versions can really mess with failover clustering! We plan to migrate to Hyper-V soon too, and I expect we'll hit similar issues because of the hardware differences.
Make sure to confirm your migration settings—check all the networking protocols like SMB and TCP, as well as authentication settings like Kerberos and CredSSP. Also, verify if your storage settings are correct for MPIO or iSCSI. It seems strange that adding one new node would cause all migrations to fail.
Related Questions
Can't Load PhpMyadmin On After Server Update
Redirect www to non-www in Apache Conf
How To Check If Your SSL Cert Is SHA 1
Windows TrackPad Gestures