Quantcast
Channel: High Availability (Clustering) forum
Viewing all articles
Browse latest Browse all 6672

Unable to migrate from new HyperV 2016 host in failover cluster error 21502 and 1069

$
0
0

I have a two node HyperV 2016 Failover Cluster. Both hosts are Dell PowerEdge R610s. I just added another host (Dell PE R620). The existing hosts have Xeon E5-2430 2.50GHz procs. The new host has Xeon E5-2690 2.90GHz procs. 

I've changed my VM CPU settings by enabling "Migrate to a physical computer with a different processor version", but when I try to Live migrate I get error 21502:

The virtual machine 'Win10test' is using processor-specific features not supported on physical computer 'CLUSTER1'. 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. 

When I Quick migrate it moves to one of the existing hosts, but fails with error 1069:

Cluster resource 'Virtual Machine Win10test' of type 'Virtual Machine' in clustered role 'Win10test' failed. The error code was '0xc0370029' ('Cannot restore this virtual machine to the saved state because of hypervisor incompatibility. Delete the saved state data and then try to start the virtual machine.').


Viewing all articles
Browse latest Browse all 6672

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>