Hello Ravinder,
Thank you for posting your question on the Microsoft Windows Forum.
The following are plausible explanations and recommendations to address your query regarding the Live Migration failure after upgrading your failover cluster.
1. Why does Quick Migration work but Live Migration fails?
Here are the key differences and reasons:
- Virtual Switch Configuration Live Migration requires identical virtual switch names and configurations across all nodes. Quick Migration does not enforce this strictly.
- CPU Compatibility Live Migration checks for CPU feature compatibility between source and destination nodes. Quick Migration bypasses this by pausing and restarting the VM.
- Saved State or Checkpoint Issues Live Migration cannot handle certain saved states or checkpoints. Quick Migration pauses the VM and resumes it, avoiding this issue.
- Storage Access Permissions Live Migration requires full access to VM storage paths on both nodes. Quick Migration is more lenient.
- Cluster Service Synchronization After upgrading, some cluster services or configurations may not be fully synchronized, affecting Live Migration.
2. What steps should be taken to resolve the issue?
Please follow these steps:
- Enable CPU Compatibility Go to Hyper-V Manager → VM Settings → Processor → Enable “Migrate to a physical computer with a different processor version”.
- Remove Saved State or Checkpoints Shut down the VM → Delete saved state → Start VM → Retry Live Migration.
- Synchronize Virtual Switches Ensure all nodes have identical virtual switch names and configurations.
- Verify Storage Permissions Confirm that all nodes have full access to the VM storage paths.
- Run Compatibility Check via PowerShell
Compare-VM -Name "Your_VM_Name" -DestinationHost "Target_Node"
This command will identify any incompatibilities preventing Live Migration.
- Review Event Logs Check FailoverClustering logs in Event Viewer for Event IDs such as 1069, 1205, or 21502.
Hope the above information is helpful!