Unable to restore this guest the target host does not support cpuid faulting

[IgorEremeev]

Hi,

A virtual machine in VMware Workstation 12 has been stoped on  a machine that has a CPU Intel Core i5 3210M. Then this VM was tried to be started on a different machine that has a CPU

Intel i7-8750H. But the start operation did not work. There was a message dialogue box with a messages.VT-D enable Intel Virtualization-Enable

[daphnissov]

Of course, you can't do that. If you suspend a VM it needs to be resumed on the same CPU type, not another. You can shut it down and power it up on another, however.

[IgorEremeev]

I turned off the machine completely and wanted to turn it on on another device(i7-8750H),but displays an error that is higher.I didn't find a similar error in Google.Only on MacOS,on Windows not found

[daphnissov]

Then you need to check the BIOS and ensure all necessary virtualization extensions are enabled on the new host.

[IgorEremeev]

[daphnissov]

Browse to the home folder of this VM and take a screenshot of all the files listed.

[IgorEremeev]

You mean like I have a virtual machine looks in the media?

[daphnissov]

I mean find the folder on your workstation where these VM files are all located and take a screenshot of all of them. This is from the host side, not inside the VM.

[IgorEremeev]

Please tell me how to do it?Is it in the temp\Vmware folder ?

[IgorEremeev]

Log

[a_p_]

According to the log file, the VM tries to resume from a checkpoint.

2019-04-28T12:42:54.325+02:00| vmx| I125: CPT: Restoring checkpoint Z:\ForPPV_2.0\MrBright-Snapshot366.vmsn

2019-04-28T12:42:54.330+02:00| vmx| I125: DUMPER: Restoring checkpoint version 8.

2019-04-28T12:42:54.342+02:00| vmx| I125: guestCpuFeatures = 0x203d

2019-04-28T12:42:54.342+02:00| vmx| I125: Msg_Post: Error

2019-04-28T12:42:54.342+02:00| vmx| I125: [msg.cpuid.noCpuidFaultingSupport] Unable to restore this guest. The target host does not support CPUID faulting.

2019-04-28T12:42:54.342+02:00| vmx| I125: ----------------------------------------

2019-04-28T12:42:56.876+02:00| vmx| I125: Msg_Question:

2019-04-28T12:42:56.876+02:00| vmx| I125: [msg.checkpoint.restore.cpufail] An error occurred while restoring the CPU state from file "Z:\ForPPV_2.0\MrBright-Snapshot366.vmsn".

2019-04-28T12:42:56.876+02:00| vmx| I125: [msg.checkpoint.restore.error] An error caused the restore operation to fail. Cancel the restore operation and correct the error, or discard the snapshot's state and power off.  The saved snapshot will not be affected.

2019-04-28T12:42:56.876+02:00| vmx| I125: ----------------------------------------

2019-04-28T12:42:58.709+02:00| vmx| I125: MsgQuestion: msg.checkpoint.restore.error reply=0

What you may try is to rename the mentioned .vmsn file to see whether this resets the VM's state.

However, due to the huge number of snapshots, I strongly recommend that you only modify things after backing up everything!

André

[IgorEremeev]

Rename in the program itself or in the program files?

[a_p_]

It's the .vmsn file in the VM's folder, that's mentioned in the log file, i.e. "Z:\ForPPV_2.0\MrBright-Snapshot366.vmsn"

André

[IgorEremeev]

I want to try with this snapshot, I don't need it in case of an error, can you tell me the snapshot number that needs to be changed?

[a_p_]

Looking at the VM's current vmware.log file, the associated file to this snapshot it  "Z:\ForPPV_2.0\MrBright-Snapshot514.vmsn".

André

[IgorEremeev]

I changed the name of the file Z: \ ForPPV_2.0 \ MrBright-Snapshot514.vmsn to Z: \ ForPPV_2.0 \ MrBright-Snapshot514Test.vmsn

[a_p_]

I did create a VM to see whether I can reproduce the issue.

Please rename the .vmsn file back to its original name. Then see whether a Snapshot .vmem file exists (same name, just with the .vmem extension).

Renaming the "MrBright-Snapshot514.vmem" file should result in a few error messages, when you try to go to this snapshot, but should allow you to discard the VM's power state.

André

[IgorEremeev]

I changed the name back, but the error remained, nothing was created instead of this file. Is there a send log?

[a_p_]

Please run

dir *.* /one > filelist.txt

from the command line in the VM's folder, and attach the resulting filelist.txt to a reply post.

André

[IgorEremeev]

Filelist