Cannot Power On Virtual Machine after Manual Move to another ESX host
Posted on 2014-10-24
I moved a VM from one ESXi 5 host to another using Veeam Backup and Replication's "File Copy" process. I believe this is the old FastSCP product now integrated into Veam BR 7. I used this procedure to copy the VM's Datastore folder over to the new server so that I would retain the snapshots that are on the VM. NOTE: Everything is LOCAL storage - no ability to vMotion.
The procedure seemed to work ok, but as a test I deleted one of the snapshots from the new location. I received the following error (Truncated):
" The virtual machine requires hardware features that are unsupported or disabled on the target host" ... "If possible, use a cluster with EVC enabled" ....
While trying to recreate the issue (which I can), I also once received the following error:
An error was received from the ESX host while powering on VM DSL-01 xxx 1.
An error occurred while restoring the CPU state from file "/vmfs/volumes/50be2de1-afba3b5a-f1ee-6cae8b66f46e/DSL-01 xxx/DSL-01 xxx-Snapshot1.vmsn".
The features supported by the processors in this machine are different from the features supported by the processors in the machine on which the checkpoint was saved. Try to resume the snapshot on a machine where the processors have the same features.
The VM originated from a host with a XEON E5606 processor and was moved to a host with a XEON E5620 processor. Is this a CPU incompatibility issue? If so, is there a solution or workaround?
I know snapshots are evil, but the intent is to try and save them. If that's not possible, would an Export/Import of an OVF template cause issues if I moved a VM between the same two hosts due to the Procs being different on each of them?
Thanks in advance for your assistance!