remo408
Contributor
Contributor

Message:The features supported by the processor(s) in this machine are different from the features supported by the processor(s) in the machine on which the snapshot was saved.

Hi,

I copied the entire VMWare image from one system to another and now i am trying to open that image from a VMworkstation already installed on the machine. I was able to open the image but when i am trying to switch b/w snap shots a window with following message is popped up

The features supported by the processor(s) in this machine are different from the features supported by the processor(s) in the machine on which the snapshot was saved. You may attempt to resume this virtual machine, but doing so may result in unpredictable behavior. Do you wish to try to resume this virtual machine?

when i tried to proceed it prompted an error window:

Error encountered while trying to restore the state of group monitorLate from file "E:\VMware\WC626\PTC_Base_Config\Windows XP Professional-Snapshot32.vmsn".

When i clicked ok on the above window . it prompted an another message :

The virtual machine was unable to power on after restoring the snapshot. The virtual machine will be left in a suspended state ready to resume from the snapshot.

I am not sure on how to proceed furthur

Any help is highly appreciated

0 Kudos
18 Replies
continuum
Immortal
Immortal

Kill the suspended state - if you don't know how to do that - post filelisting including size and date

___________________________________

description of vmx-parameters:

VMware-liveCD:

Do you need support with a recovery problem ? - send a message via skype "sanbarrow"
0 Kudos
remo408
Contributor
Contributor

Windows XP Professional-Snapshot32.vmsn Size:17.1 MB created:Friday, August 22, 2008, 2:21:17 PM Modified:Thursday, April 17, 2008, 12:42:53 PM

Windows XP Professional.vmx Size:3KB Created:Friday, August 22, 2008, 2:23:36 PM Modified:Today, August 28, 2008, 1:35:44 PM

Is this what you are expecting?

And also can you provide me a brief idea on why is it prompting:

The features supported by the processor(s) in this machine are different from the features supported by the processor(s) in the machine on which the snapshot was saved. You may attempt to resume this virtual machine, but doing so may result in unpredictable behavior. Do you wish to try to resume this virtual machine?

Thanks...

0 Kudos
RDPetruska
Leadership
Leadership

It is prompting you because the VM is in a suspended state when you copied it from a PC with one processor family to a PC with a different processor family. When you resume a VM, Workstation needs to load the CPU registers with the values from the suspend file, and if the CPU has changed to one in a different family, there may be registers not present in the new one, or the old one - leaving the VM in a potentially unstable state.

0 Kudos
continuum
Immortal
Immortal

please run inside the VMs directory in a cmd

dir > postme.txt

Hot snapshots - ehmm meaning snapshots that were taken while the VM is running - can only be restored on a host that uses the same CPU as that host where the snapshot was taken.

In your case the two CPUs are to different

___________________________________

description of vmx-parameters:

VMware-liveCD:

Do you need support with a recovery problem ? - send a message via skype "sanbarrow"
0 Kudos
remo408
Contributor
Contributor

RDPetruska & Continuum

Thanks for your quick response. Is there a way to come accross this issue. What should have been done while moving stuff from one machine to another to have a safe transfer of these files?

FileListing details uploaded

0 Kudos
continuum
Immortal
Immortal

>What should have been done while moving stuff from one machine to another to have a safe transfer of these files?

Do not use hot snapshots - power down the VM before taking snapshot.

You got a complex snapshot - can you post screenshot of snapshotmanager ?

___________________________________

description of vmx-parameters:

VMware-liveCD:

Do you need support with a recovery problem ? - send a message via skype "sanbarrow"
0 Kudos
remo408
Contributor
Contributor

Screen shot of snapshot manager attached

0 Kudos
remo408
Contributor
Contributor

Screenshot of snaphot manager attached

Both zip & rar format are attached.

Thanks...

0 Kudos
continuum
Immortal
Immortal

This VM has 10 snapshots and the last 8 of them were taken while the VM was running Smiley Sad

Don't do that - if you know that you have to move the VM !

Add this line to the vmx and try again to resume

checkpoint.disableCpuCheck = "true"

Before adding the line - make sure you exit Workstation

___________________________________

description of vmx-parameters:

VMware-liveCD:

Do you need support with a recovery problem ? - send a message via skype "sanbarrow"
0 Kudos
remo408
Contributor
Contributor

I was never planning to move this VM from one machine to another but it's due to space constraints i have to do that .

I added the line to the vmx file and it still prompt's the same error

I checked the vmx file and the line i saved is removed. It's happening when i am reverting back to the oldsnapshot. I would assume that it's getting the default settings for the old snapshot and that's the reason the vmx file is changing to it's old settings.

So is this expected behavior or am i doing something wrong

Thanks.

0 Kudos
remo408
Contributor
Contributor

Would adding this line to vmx file fix issue while taking snapshots in future or would it fix the issue when switching to old snapshots because i see that if i try to switch to old snapsahot thats overwriting VMX file where i added the following line:

checkpoint.disableCpuCheck = "true"

Thanks

0 Kudos
continuum
Immortal
Immortal

It may help - but keep in mind that when you resume a VM with a "false" CPU -it will very likely crash at once.

If you really need to move VMs with snapshots between hosts with different CPUs the only safe way is to use cold snapshots.

Sorry - I had hoped to look into your case more deeply but I am simply to tired from work - and the chance to mess it up is to high unless i am fully awake Smiley Sad

Ulli

___________________________________

description of vmx-parameters:

VMware-liveCD:

Do you need support with a recovery problem ? - send a message via skype "sanbarrow"
0 Kudos
remo408
Contributor
Contributor

So any workaround that would let me switch back to my old snapshots?

And how were you able to figure out that there were 8 snaqpshots which are taken when the machine was running?

Would proceeding from here by taking coldsnapshots will work?

What would be your suggestion for me now because i can't go back and poweoff all the snapshots and delete the suspended once but this way i might lose my work right?

0 Kudos
CVCNetwork
Contributor
Contributor

I upgraded to vSphere 4 last night (3 hosts).

After upgrading, any vm that was suspended during the upgrade would not start with ''The features supported by the processor(s) in this machine......" error.

As noted above I added

checkpoint.disablCpuCheck="true"

to each affected vm's VMX file and the started perfectly.

Thanks again

0 Kudos
JohnnyLeung
Contributor
Contributor

i tried to added checkpoint.disablCpuCheck="true" on the vmx file, but it does no help, anyone have some good solution?

I cannot do anything on that VM now, neither power on nor change any settings there.

thanks.

0 Kudos
WoodyZ
Immortal
Immortal

@JohnnyLeung I'll assume your working with a VM that has Snapshots and was copied to a different system then it was created on.  I'd suggest, if possible, deleting the Snapshots via the Snapshot Manager.  Or use vmware-vdiskmanager to create a new .vmdk from the existing on while pointing to the snapshot.vmdk that is the current one in the .vmx configuration file and then either swap the virtual disks out or create a new VM from the new .vmdk file.

0 Kudos
JohnnyLeung
Contributor
Contributor

yes, the VM is with snapshot.

what I have done is in esxi 4.1 update 1, originally having 2 esxi hosts, and I shut down all guest OS (some of them with snapshot), and added 1 extra host to the cluster. But at that time, I need to downgrade the Vmotion EVC mode a level because of the hardware are not exactly the same.

After added the host, there was not problems and warnings. but when I tried to revert a VM with snapshot, it failed...then that VM cannot be start anymore.

Any chance that I can keep the snapshot and make the VM available again? I cannot shut down the host again as it is in production environment.

your help is highly appreciate. thank you.

0 Kudos
WoodyZ
Immortal
Immortal

@JohnnyLeung  You're posting to the wrong forum! Smiley Wink  You can select the appropriate one from the list at: VMTN Forums

0 Kudos