- Check whether enough resources (CPU, RAM) are available at the destination host
- Make sure all nodes in the cluster follow same naming standard for vSwitches
- Check NUMA spanning is enabled or not. If NUMA spanning is disabled, VM must fit entirely within a single physical NUMA node or the VM will not start or be restored or migrated
- Constrained delegation should be configured for all servers in the cluster if you are using Kerberos authentication protocol for live migration
- Check live migration setting is enabled on Hyper-V settings
- Verify Hyper-V-High-Availability logs in event viewer
- Finally check cluster debug log (Get-Clusterlog -timespan) in C:\Windows\Cluster\Reports\Cluster.log
Saturday, July 9, 2016
Troubleshooting Live Migration issues on Hyper-V
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment