Hyper-V 2019 Cluster Live Migration Fails (processor-specific features not supported)

Question

Live migration of 'Virtual Machine TEST_SERVER_1' failed.

Virtual machine migration operation for 'TEST_SERVER_1' failed at migration destination 'ClusterNode2'. (Virtual machine ID CECBEFEC-48E1-4B18-94A0-XXXXXXXXXXXXXX)

The virtual machine 'TEST_SERVER_1' is using processor-specific features not supported on physical computer 'ClusterNode2'. 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 CECBEFEC-48E1-4B18-94A0-XXXXXXXXXXXX)

Hi,

I have 3 hosts in a cluster, all the same spec hardware, CPU's, BIOS versions, and patch levels. Live migration between these hosts works fine.

I add a 4th host, also same spec, CPU's etc. and live migration does not work I receive the error above.

Running cluster validation report reports no errors.

I attempt to do a quick migration, this fails with an error as well (sorry I haven't saved this error). The virtual machine remains on the current host.

Finally I shutdown the VM running on host 1, 2 or 3... then I quick migrate to host 4. I power on the VM on host 4, it boots fine. I am now able to live migrate from host 4 to host 1,2,3 and from host 1,2,3 back to host 4.

I've just resolved this by shutting down every machine and doing the offline quick migrate across to host 4, power on, live migrate back. But I would like to know the reason for this occuring?

Everything I could find was the same between the hosts and host 4 is now working fine without any change made.

The VMs have a mix of cpu compatability checked and unchecked (although it shouldn't matter because they're the same spec/config server throughout).

Any ideas?

Many thanks,
Stefan

Answer 1

I have just migrated a new machine in from VMware to Host 3. Same problem. I can migrate to Host 1 or 2 without issues but trying to migrate to Host 4 fails.

So I shutdown, migrate offline to Host 4, power on, now the VM is able to move between all 4 hosts freely.

Answer 2

Hi,

Since the issue has been resolved, it's hard to find the root cause of it. Based on our experience, the possible cause might be the newly added Host hypervisorschedulertype hasn't set to "core". If the issue reoccurred, you may check it.

Thanks for your time!
Best Regards,
Anne

-----------------------------

If the Answer is helpful, please click "Accept Answer" and upvote it.

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Answer 3

Hi Anne,

Thanks for your reply! The scheduler type sounds possible as Host 1-3 had an earlier version of 2019. Host 4 was the December release of 2019. I'll run some checks and report back.

The link you posted had an error so I am reading up on it here : https://learn.microsoft.com/en-us/windows-server/virtualization/hyper-v/manage/about-hyper-v-scheduler-type-selection

After running the same checks again by the way the issue isn't resolved so if it isn't the scheduler type then we can investigate further.

I'll be in touch!

Many thanks,
Stefan

Answer 4

Very good article here on the scheduler types - https://learn.microsoft.com/en-us/windows-server/virtualization/hyper-v/manage/manage-hyper-v-scheduler-types

Answer 5

Hi Anne,

Unfortunately the issue is doesn't appear to be the scheduler type. All 4 hosts are 0x4 (Core) Scheduler type.

Any other ideas please?

Thanks,
Stefan