Hyper-V Live Migration - Processor Compatibility

[PinkFloyd]

Hi All,

Does anyone have much experience around live migrations in Hyper-V between slightly different CPUs? From what I can make out the Processor Compatibility option is more intended for differences in revisions and or feature sets. Should it be needed for 2 cpus of the same series, but a different clockspeed? For example a Xeon e5520 (2.26GHz) and an e5540 (2.53GHz) - for reference I'm looking at Server 2012R2 with a plan to migrate to 2016 at a later date.

I believe this shouldn't be an issue and all that will be seen from the VM's perspective is the clockspeed effectively dropping as if it were under less load.

I'm struggling to find any concrete answers on this! Anyone else able to share their experience?

Thanks!

 

[Deleted member 138126]

Try it? It will either work or it won't. Depends on a surprisingly large number of things, so what better than let the actual Hypervisor check and tell you whether it is possible or not? The clock speed is not the issue (it is irrelevant). It is about the features that each generation of CPU makes available, and whether or not the VM is making use of them.

 

[nutcase]

I forget the actual proc numbers but I migrated from an ML330 G6 to a DL388 Gen8 without issue. VMs were server 2012 R2.

 

[PinkFloyd]

Well I'd have tried it if I could have done so easily, not got the hardware in a position I can actually do any testing hence asking whether anyone else had tried!
If the clock speed is irrelevant it shouldn't be an issue. Will find out in the coming weeks I guess, can always use the processor compatibility if needed.

Environment isn't for anything too vital so can workaround issues as needed really. Will be a means to properly test out 2016 before anything