Workstation 6.5 - Dell replaced a faulty motherboard and now I cannot restore vm's. Getting this error

[JoshFink]

I'm getting the following error when I try to restore my VM's. Nothing should have changed. It's just a new motherboard.

Here is the error message I'm getting:

The virtual machine you are attempting to restore is using the NX/ED CPU feature, but your host does not support it.

Error encountered while trying to restore the state of group monitorLate from file "C:\Virtual Machines\XP\Windows XP Professional.vmss".

Any ideas?

This is an important VM so I'm hoping someone can help me out quickly.

Thanks

Josh

[continuum · Accepted solution]

Delete "C:\Virtual Machines\XP\Windows XP Professional.vmss".

Then you can start the VM again

___________________________________

description of vmx-parameters:

VMware-liveCD:

[JoshFink]

Will that delete my suspended state? I really would rather not lose all the data that is in there between my last snapshot and my suspended state.

Thanks

Josh

[continuum]

Yes - the suspended state will be lost.

This is the same as if a real machine would be hard shutoff by pulling the plug.

You will only lose file that were just open while you suspended the VM on the different host you used before.

Thats the only way - unless you somewhere have an exact copy of your original system.

___________________________________

description of vmx-parameters:

VMware-liveCD:

[JoshFink]

Thanks.. Any clue what would cause this?

Josh

[continuum]

Sure - you have effectively moved the VM from a host which enables features XY of your CPU to a host which enables different features.

The mainboard change is the reason for this.

The changes might be very small only - but they are large enough to prevent a resume.

Maybe you just use slightly different BIOS-settings than before ...

___________________________________

description of vmx-parameters:

VMware-liveCD:

[Scissor]

Is VT not enabled in the BIOS of your replacement motherboard (when it was enabled on your old motherboard)? If not and you enable it, make sure to power off and back on again (a reboot isn't enough).