VMware Cloud Community
radman
Enthusiast
Enthusiast

Trouble after reverting to a snapshot following a vCenter "Migrate".

I have deployed a new vSphere 4 server, and migrated all my VMs to it via vCenter. All seemed well at first.

Now I've tried to resume an old snapshot in a 32-bit XP VM, and am getting this error:

"The vendor of the processor(s) in this machine is not the same as the vendor of the processor(s) in the machine in which checkpoint was saved"

I don't really care about the suspend state, I'd be happy to boot up fresh, but I appear to be stuck in suspend mode now with no obvious way out... The original ESX host is no longer available.

How can I get out of this situation, and boot up this machine?

Reply
0 Kudos
6 Replies
DSTAVERT
Immortal
Immortal

Powering off has no effect? Have you tried connecting directly to the Host with the vSphere Client?

-- David -- VMware Communities Moderator
Reply
0 Kudos
radman
Enthusiast
Enthusiast

Power off is disabled, both in the tools and LHS VM menus.

This is whether I connect directly to the ESX server or via vCenter.

I'm stuck in Suspend state somehow.

Reply
0 Kudos
a_p_
Leadership
Leadership

Without snapshots, you can just delete the latest vmss file. With snapshots this could be different.

If you are not sure, please post a list of files in the VM's folder (with names and time stamps)

André

Reply
0 Kudos
radman
Enthusiast
Enthusiast

Thanks, but I don't have any "vmss" files. My dir listing is attached.

Reply
0 Kudos
DSTAVERT
Immortal
Immortal

I would try restarting the management agents on the Host.

-- David -- VMware Communities Moderator
Reply
0 Kudos
a_p_
Leadership
Leadership

I would do the following:

  1. Backup the files (to be save in case something does not work)

  2. Delete the two vmsn files

  3. If the VM powers on and is ok, delete all snapshots using the snapshot manager

André

Reply
0 Kudos