Yo Motherboard

Trouble with Live Migration in Hyper-V: Need Help!

September 12, 2025 5 answers
Asked by TechWiz42
I'm working on setting up a new Hyper-V environment for around 40 VMs, and I have two hosts that work fine for live migrations. However, the third host I've added isn't cooperating at all. I've set all VMs to allow migration to hosts with different processors. When I attempt to migrate a VM, it looks like it's processing but eventually just halts without any error messages, leaving the VM stuck on its original host. This issue occurs with all VMs, across different networks. I've updated all the hosts to the latest Windows patches. We have a Dell R650 and two Dell R940 hosts. The hosts with successful migrations don't have any BIOS settings changed, but I'm unsure if the new one does. Any suggestions on how to resolve this? Thanks!
Hyper V live migration server management System Operations virtualization VM migration

Answers

VMmasterX
Are you attempting to migrate multiple VMs at once? Ensure that your Hyper-V settings for concurrent migrations are correctly configured. You should only try migrating one VM at a time while resolving the issue.
Reply to this answer
ServerGuru91
Have you tried powering down the VM and migrating it to the R650 using Quick Migrate? Also, can you share the CPU specs for the R650 and both R940s? It’s essential to check if the Hyper-V settings for migration and NUMA are consistent across all three hosts.
Reply to this answer
SysAdminAce
Have you verified that ‘Migrate to a physical computer with a different processor version’ is enabled? I ran into a similar issue before and enabling that setting helped.
Reply to this answer
CloudNinja77
Good point! Do your other hosts have enough RAM to support all the VMs if they migrate over? I also suggest checking the Event Viewer under Microsoft -> Windows -> Hyper-V-VMMS -> Admin. Look for Event IDs 21502, 21024, or 21022 to see if there are any migration failure logs.
Reply to this answer
HyperVChampion
Do you happen to have a TPM configured with encryption enabled? Also, double-check that you've exported the host guardian certificates from the other nodes and imported them to the new node. If needed, create a host guardian certificate on the new node and export it to the others.
Reply to this answer

Add your answer

Answers are reviewed before publication.

Related Discussions