Moved vm's to a new location but won't launch the vm

[dbyy]

Hi folks,

I was using vmware workstation Player v 17.1 for several weeks now and it worked fine until this morning.

I moved a vm to a new location on a M2.SSD (from a regular SSD).

I opened  the vm file (a WIn10 guest) on the new location in vm player but it won't launch the virtual machine.

(File -> Open a Virtual Machine (CTRL-O))

No message, no hint. the vm player just quit silently.

Is there a way to resolve that problem?

Any help is much appreciated.

HOST OS is Linux Mint v20.3

Guests: Win10

[dbyy]

Some additional discoveries.

the vmware.log file in the vm's folder shows an entry saying "/usr/lib/vmware/settings": No such file or directory."

And this directory is really missing. I seems to be it has to be removed by "something" because it was working before.

I'm wondering whether it would help to uninstall vmplayer but leave the virtual-machine intact.

I also installed a totally new vm (Linux) from the source ISO and this vm is also not launching. It shows the same behavior as the 'moved' vm's before.

I'm quite puzzled.

Cheers

[a_p_]

>>> "/usr/lib/vmware/settings": No such file or directory."

That's more of a statement, than an error. Are there any other hints in the vmware.log?

André

[dbyy]

well,

I'm assuming it's complaining about it therefor it was expecting it to be there.

And I assumed there might be a connection between this log entry and the failure to launch the vm(s).

For better information I will attach the log file to this posting.

Thanks

[Technogeezer · Accepted solution]

The log is indicating that the VM is failing to power on because AMD-V is not enabled in the BIOS. Could you double check that? 

[dbyy]

The BIOS had an option called SVM mode (CPU virtualization).

That was disabled, I changed the settings to 'enabled' and that did the trick.

The vm's are now being launched again.

Many thanks.