I have a problem about hyper-v failover cluster live migration. Originally i have a Windows Server 2012R2 hyper-v failover cluster with 3 node members (2xR420 1XR430). The live migration works perfect between the nodes. Our company buy 2 R440 server and a new storage and we bulid a new Windows Server 2019 hyper-v failover cluster. After migrate VM's to the new cluster we destroyed the old cluster and reinstall the R430 to Windows Server 2019. Next step we add the R430 to the new cluster.
node1 (R440): Intel® Xeon® Silver 4116 Processor
node 2 (R440): Intel® Xeon® Silver 4116 Processor
node3 (R430): Intel® Xeon® Processor E5-2640 v2
If I try live migraton from node 1 or node 2 to node 3 live migration failed:
Live migration of 'VMNAME' failed.
Virtual machine migration operation for 'VMNAME' failed at migration destination 'NODE03'. (Virtual machine ID 63AFF93A-13F7-40B9-8C4A-32B9E6801448)
The virtual machine 'VMNAME' is using processor-specific features not supported on physical computer 'NODE03'. To allow for migration of this virtual machine to physical computers with different processors, modify the virtual machine settings to limit the processor features used by the virtual machine. (Virtual machine ID 63AFF93A-13F7-40B9-8C4A-32B9E6801448)
Processor compatibility is already turned on every VM!!
If I turned off VM I can migrate to node3. After offline migration I turend on VM on node3 (R430) I can move the VM between all nodes but if I restart VM node1 or node2 live migration to node3 fail again.
All nodes is updated with SUU and the OS is up to date.