The above message comes when trying to power on a VM. The message indicates that the VM has earlier been running on a cpu (at a differrent host server) with a maximum higher MHz rate and that resource allocation was defined for this VM while running on that host.

If you connect the viclient directly to the ESX(i) host instead of the vCenter Server, the error message is slightly different:

Editing the resource setting of such a VM that was allocated out of range of the current server is not always possible so you might need to either move the VM back to a server that supports higher MHz rates or to edit the VM's config file manually.

If you choose to edit the config file manually you will first need to unregister the VM from vCenter, then open the file from a console session, remove the resource allocation lines, and then register the VM in vCenter again.