- 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
Showing posts with label Live migration. Show all posts
Showing posts with label Live migration. Show all posts
Saturday, July 9, 2016
Troubleshooting Live Migration issues on Hyper-V
How Live Migration works on Hyper-V
1.Live migration setup
- Source host creates TCP connection with destination host
- VM configuration data is transferred to destination host
- A skeleton VM is setup at destination host
- Physical memory is allocated to that VM
- In-state memory (working set) of the VM will be transferred first
- Default page size is 4 KB
- All utilized pages will be copied to destination
- Modified pages are tracked by source and marked as being modified
- Several iteration of copy process will take place
- VM is then registered and the device state is transferred
- Less modified pages implies fast migration
- Total working set is copied to destination
- Till this step VM at destination host is not online
- Now the VM is completely migrated and running on destination host
- Message is sent to physical network switch causes it to relearn MAC address of migrated VM
Subscribe to:
Posts (Atom)