Hyper-V Failover Cluster

Mohamed Ahmed 0 Reputation points
2023-01-16T07:12:31.3033333+00:00

I have 6 servers with same specifics and connected to same storage and same OS version
3 of them vms can migrate without any problem another 2 nodes the vm not migrate.

1- I enabled the option of CPU compatibility but same error still
2- when the vms is off it can migrate, but when on I can't migrate to another 2 nodes.

Hyper-V
Hyper-V
A Windows technology providing a hypervisor-based virtualization solution enabling customers to consolidate workloads onto a single server.
2,530 questions
Windows Server Clustering
Windows Server Clustering
Windows Server: A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.Clustering: The grouping of multiple servers in a way that allows them to appear to be a single unit to client computers on a network. Clustering is a means of increasing network capacity, providing live backup in case one of the servers fails, and improving data security.
956 questions
0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Eric Siron 1,251 Reputation points MVP
    2023-01-17T20:20:30.2433333+00:00

    It would help to know the error. Are you sure it's upset about the CPUs? Have you tried Compare-VM to see exactly what it doesn't like?

    Run the Cluster Validation Wizard to see if it yields clues. The article was written for 2012 era hosts but the only thing that's changed is the depth of the validation checks. Skip the storage checks so that your guests stay online.

    If the CPUs are different, then the CPU compatibility setting is not a magic bullet. There's no easy way to know in advance (unless the CPUs are from different manufacturers). Sometimes processors have substantial differences that can't be masked away. The Cluster Validation Wizard should at least warn about this.

    If you know that they have the same CPUs and you're certain that it's a CPU problem, then most likely this is due to a mismatch of BIOS or Windows Update levels. I don't know of anything major that's happened recently that makes this likely, though. The fixes for Spectre and Meltdown type exploits required the hosts to be fully patched and power cycled (not just restarted) and then for the guests to fully patched and "power" cycled (not just restarted). Any mismatch across a cluster and Live Migrations will fail. The Cluster Validation Wizard should detect mismatched patch levels but it won't know about power cycle status. However, those fixes were long enough ago that it seems unlikely that anyone would still be encountering problems with them unless something is REALLY out of date.

    0 comments