Can someone confirm or deny this observation:
We have a vSphere cluster with Intel Xeons E5-2667 and E5-2650, i.e. we are using EVC. When inquiring the CPU in a VM (e.g. "cat /proc/cpuinfo" in *NIX, "Get-WmiObject -Class Win32_Processor" in Windows), the information used to change when live migrating a VM between ESXen with different processors. You could run these commands in a loop and see the output suddenly change to the other value.
This does not happen any more. It seems that the CPU information that was valid when the VM started is now hard coded to the VM and does not change any more. We are currently debugging problems in a Solaris VM and we suspect that the OS makes its own assumptions about processor capabilities or uses features that are not flattened by EVC.
Did this behavior indeed change? Is this a feature or a bug introduced e.g. in the changes to alleviate the impact of Spectre/Meltdown? We are using the latest version of ESX 6.0U3, but I think I noticed this change three or four months ago.