I'm having trouble migrating any Hyper-V VMs between my servers. This is frustrating because it used to work just fine! Now, every time I try, I get the error message: 'the hardware on the destination computer is not compatible with the hardware requirements of this virtual machine.' I've already set the VMs to 'compatibility mode' and ensured they're powered down before attempting the transfer, but I'm still stuck with the same error.
All my hosts are running Windows Server 2019, and while most of the VMs are on 2019 too, I do have a few on 2012 R2. The physical server hardware is all Intel, though not identical across hosts. For example, one host has:
- 2 Processors Installed:
- Intel64 Family 6 Model 85 Stepping 4 at ~2095 MHz
While another host has:
- 2 Processors Installed:
- Intel64 Family 6 Model 106 Stepping 6 at ~2793 MHz.
I also read about using 'bcdedit' to set Hyper-V to 'classic' mode, but that requires a restart. Authentication isn't the issue, as we've consistently used Kerberos with Delegation without changes. I feel like there's just a new setting I might be missing. Any suggestions?
5 Answers
I usually try the basic troubleshooting steps suggested online. Like, removing the NIC from the VM and attempting the migration again often does the trick for me! Worth a shot!
You should check for a setting that allows VM migration even for mismatched processors. There's documentation on that feature; it might resolve your issue!
Have you done any recent BIOS or firmware updates? If anything changed around the time the migrations stopped working, that could be the culprit.
I had a similar problem and found that different update levels on my servers caused issues with live migrations. Try putting each server into maintenance mode and running Windows Updates to make sure they're all on the same version!
Sometimes the issue could be with the network settings. If the NICs are named differently or the configurations vary between your hosts, that might be causing the hang-up. Just something to check!
Thanks for the suggestion, but I already reconfigured for compatibility mode and it didn't fix the problem.