Live Migration in Failover Cluster problem - event 21502

Question

Hi All,

I have an eternal problem with Live Migration between two types of processors. I have two types of processors in a cluster. One server is not too old (maybe 2-3 years old) and another the new.

Server 01: RX2540M7R1 2x INTEL(R) XEON(R) SILVER 4509Y @ 2.6GMHz

Server 02: RX2540M5R4 2x Intel(R) Xeon(R) Silver 4208 CPU @ 2.10GHz

Microsoft HA does not work.

System generates Event 21502

The virtual machine 'VMNAME' is using processor-specific features not supported on physical computer 'HOSTNAME'. 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 4042C215-8ED5-40E2-A3A4-32B2D0D46E8A)

Of course Processor compatibility is on.

System Windows Server 2022 Datacenter.

Is there some document where I can check processor compatibility for Live Migration in Microsoft Failover Cluster?

Is anybody who resolved this problem?

Answer 1

Hello,

Based on my understanding of your issue, I suggest you open PowerShell and run the following command to check compatibility.

Compare-VM -Name <vm_name> -DestinationHost <host_name>

Note: From left to right, the bold parts replace the VM and destination host names respectively.

You can refer to the following link:

Troubleshoot live migration issues - Windows Server | Microsoft Learn

Best Regards

Zunhui

Answer 2

Thanx for reply.

Incompatibilities : {21026, 24004}

I did this before. I forgot that.

I escalated this to Fujitsu but support does not want to help and suggest to talk with Microsoft support.

HP support resolved the problem with 21026 but his solution was concerted by differences in system software (2019/2022)

Of course, I tried to change the BIOS version, drivers, and reinstalled systems, but it wasn't enough.

Anyway, I still have not resolved this.

Answer 3

Hi，

Thank you for your reply. I suggest you update the host system patch to the latest version and the BIOS firmware version to the latest version or the same version to see if this problem can be solved.

Best Regards

Zunhui