I inherited support of a 2016 Hyper-V cluster of four hosts, using a SAN for storage. Given the number of VMs and their CPU/memory requirements, it was obvious that the cluster needed to grow.
Stood up the new host, matched up permissions, set up constrained delegation, allowed unencrypted WinRM/WMI, added to cluster.
If I build a VM on the new node and start it, I'm unable to live migrate it to the other nodes. I get the "processor-specific features" message despite having ticked the CPU compatibility checkbox.
However, if I shut that VM down, quick migrate it to another node and turn it back on, I can then live migrate it back and forth between the new node and the old nodes all day long.
Can someone suggest where to look to straighten this out? Thanks in advance for any help!
CPU DETAILS:
As the new host is, well, newer than the preexisting hosts, the CPUs are newer.
Host 1 - Intel64 Family 6 Model 79 Stepping 1
Hosts 2-4 - Intel64 Family 6 Model 62 Stepping 4
Host 5 - Intel64 Family 6 Model 85 Stepping 7