Solution to vmware failure caused by forced power failure

First, warn you not to force shutdown at will. vmware is a software with a complex mechanism. It is easy to see various situations.

A virtual machine works just like a real computer. For example, you can install an operating system, install applications, and access network resources. For you, it is only an application running on your physical computer, but for applications running on a virtual machine, it is a real computer. Therefore, when you evaluate software in a virtual machine, the system may crash. However, the only thing that crashes is the operating system on the virtual machine, not the operating system on the physical computer, with the "Undo" function of the virtual machine, you can immediately restore the status of the virtual machine to the status before installing the software. A friend crashes when running a virtual machine. After forced shutdown, the original virtual system that has not been properly shut down cannot be started normally. Why can this problem be caused?Virtual Machine crashWhat about it? To address this problem. Next we will learn how to solve it.The VM cannot be started..

Solution:

Delete the % Virtual Machine name %. vmx. lck folder or files in the folder in the corresponding virtual machine directory.

When we open the task manager, we will find two important processes: vmware.exeand vmware-vmx.exe. The virtual system running in supervisor and interpretation of various commands and operations are our most common VMware user interface. This program can be re-imported to open multiple at the same time.

Because VMware workstationis rewritable, to avoid errors caused by multiple open vmware.exe operations on the same virtual system at the same time, each VMware opens the corresponding virtual machine tab and checks whether the root directory of the virtual machine has *. vmx. lck folder and verify the file. If the file contains a valid uuid (universal unique identifier), you cannot open the tab of the Virtual Machine and the following error message appears:

After taking Ownership, the following message is displayed:

If no valid file exists, the file is generated in the root directory of the VM *. vmx. lck folder, and generate a folder containing uuid *. lck file, open the Virtual Machine tab, and receive the display information from the main program.

You can edit the *. lck file in notepad. It contains uuid = {a string of letters and numbers}, and uuid is a universal Unique Identifier, which is Unique. In this case, only one vmware.exe can display the main program and operate on the virtual machine. Lck is short for lock, that is, locking the requested resource.

When the VMware virtual machine is running, three files are generated under the corresponding virtual machine directory *. vmx. lck ,*. vmdk. lck ,*. vmem. lck folder, which contains *. the file named by lck. * .Vmx.lckis generated along with the opening of the vmware.exe tab. The other two are about the use of Virtual Disks and memory, which are generated along with the running of the virtual system. If you shut down vmware.exe to run the VM in the background, the *. vmx. lck folder will disappear and the other two will not.

When a virtual machine tab is opened in vmware.exe, *. vmsd. lck folder. It is estimated that this is generated when data is initially sent to prevent multiple Shell programs from simultaneously requesting to open the virtual machine.

Follow these steps to delete the *. vmdk. lck and *. vmem. lck folders may be damaged due to an error ".

Do not be discouraged. It may be because your disk drive is damaged. Shut down vmware and restart your physical machine. Note that it is a real physical host.

During restart, do not skip disk check and repair.

Try opening *. vmx again, right?

I have to say that if you were smart and used notepad to edit the *. vmx file, you cannot open *. vmx from vmware. You need to right-click *. vmx to open it with a virtual machine.