Still celebrating National IT Professionals Day with 3 months of free Premium Membership. Use Code ITDAY17

x
?
Solved

Cannot Power On Virtual Machine after Manual Move to another ESX host

Posted on 2014-10-24
3
Medium Priority
?
915 Views
Last Modified: 2016-02-25
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!
0
Comment
Question by:CipherUser
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2
3 Comments
 
LVL 123
ID: 40403028
Was this machine PAUSED ?

Moving a VM between servers with different CPU Generations, should not cause this issue.

But the message suggests the VM was in a paused STATE ?

or, WAS a snapshot created which ALSO snapshotted the MEMORY STATE!

It's ALSO a bad idea, to move VMs with snapshots attached, DELETE the SNAPSHOT (MERGE FIRST!) Do NOT just delete the file!

WHY OH WHY, are you want to maintain SNAPSHOTS, they are not backups!

You will be sorry! performance is poor!

See my EE Article....

HOW TO: VMware Snapshots :- Be Patient

It's possible you have the lecture already from me, because you are using my phrase "snapshots are evil!"

So either way, SNAPSHOTS have caught you out, because of the CPU generation mismatch!
0
 

Author Comment

by:CipherUser
ID: 40406628
Thanks Andrew for your answer.  Unfortunately, the snapshots are being used for version control in a dev environment.  I need to move a VM with the snapshots to a different host if at all possible.  What's the best/safest way to do this?  The snapshots that exist do (I believe) have memory snapshots as well.

Thanks for the additional clarification!
0
 
LVL 123

Accepted Solution

by:
Andrew Hancock (VMware vExpert / EE MVE^2) earned 2000 total points
ID: 40406637
This is the issue, the memory snapshot, if they did not have a memory snapshot, you would not have the issue.

or of you had HOSTS with the same Generation CPU.

Create a new Snapshot on the VM, but do not snapshot memory. (e.g. power down the VM!).

BUT, the fact you already have a memory snapshot, could make this awkward.

VMs are not designed to run on snapshots, they are not backups, and moving VMs with snapshots is not supported, and if you have a memory snapshot taken on a Gen1 CPU, it will not start on a Gen2 CPU etc

Could you re-do without the memory snapshot?

You could try removing the memory snapshot from the disk, and also remove entry from the VMX file, but this is unsupported, and you are not entering "hack my VM space!"
0

Featured Post

Fill in the form and get your FREE NFR key NOW!

Veeam® is happy to provide a FREE NFR server license to certified engineers, trainers, and bloggers.  It allows for the non‑production use of Veeam Agent for Microsoft Windows. This license is valid for five workstations and two servers.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Ransomware is a malware that is again in the list of security  concerns. Not only for companies, but also for Government security and  even at personal use. IT departments should be aware and have the right  knowledge to how to fight it.
In previous parts of this Nano Server deployment series, we learned how to create, deploy and configure Nano Server as a Hyper-V host. In this part, we will look for a clustering option. We will create a Hyper-V cluster of 3 Nano Server host nodes w…
Teach the user how to join ESXi hosts to Active Directory domains Open vSphere Client: Join ESXi host to AD domain: Verify ESXi computer account in AD: Configure permissions for domain user in ESXi: Test domain user login to ESXi host:
This Micro Tutorial steps you through the configuration steps to configure your ESXi host Management Network settings and test the management network, ensure the host is recognized by the DNS Server, configure a new password, and the troubleshooting…

715 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question