This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(246.4, 79%, 33%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMO%3C/text%3E%3C/svg%3E)
Hello,
I have a cluster with 4 hyper V.
I have 2 servers with a GenuineIntel Intel64 Family 6 Model 85 Stepping 4 processor,
and the 2 others with GenuineIntel Intel64 Family 6 Model 85 Stepping 7 processor.
Since i migrated my hyperV servers from 2016 to 2019, the live migration between the servers with differents processors failed. (error 21502).
The compatibility box is checked.
I would like some help.
Thanks.
This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Comments have been turned off. Learn more
Hi,
The processor compatibilty mode is enabled on each VM, and the cold migration is working.
Regards.
Up,
Any answers ?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(220.8, 52%, 31%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAK%3C/text%3E%3C/svg%3E)
I have the same ussue with DELL R440 and R650 on WS2022 Datacenter
Intel64 Family 6 Model 85 Stepping 4 Intel(R) Xeon(R) Silver 4110 CPU @ 2.10GHz
Intel64 Family 6 Model 106 Stepping 6 Intel(R) Xeon(R) Silver 4316 CPU @ 2.30GHz
BIOS settings are completely the same.
CPU copmatibility for live migration set for the vm.
Migration could be done in both directions, once VM started on 4110
In case VM started on 4316 it will not move to 4110, but will migrate to 4316.
Comapre-VM reponces with Incompatibilities : {21026, 24004} without additional info.
Any help will be apppreciated.
Any help ?