I assume you activated EVC when the VMs were running? EVC does not update the VMs during operation. Only at startup do the VMs realize which EVC mode and which CPU features are set.
Have you tried to power off and power on again the affected VMs? After that they should have the same EVC mode as the cluster and be able to use all functions of Westmere.
No I have not rebooted the virtual machine, so why did only two stay at nehalem and the other three went to westmere? My next step is to take the evc mode to sandy bridge once I have resolved this issue
Okay I guess someone did reboot those machines since evc mode was enabled and the still come up in the nehalem generation