Forced to close after the virtual machine to solve the problem +

 

Tip Tip probably Vmware exclusively lock the configuration file fails, calm looked, if that is the literal meaning of understanding, because the process did not end the program on a lock problems caused.

Then I started to look for solutions we tried, in conclusion, it is divided into two factions:

1. Open the Task Explorer, VMware end all violence related processes

2. (or) under Ubuntu installation directory delete all the files and folders .lck

Note: when necessary to restart the computer

---

Solving mentality of:

All with VMware's first look at the process of "Task Manager" inside a running, terminate all violence; and then delete all files .ick Ubuntu directory below, OK, confidently open

Checked, this problem is easy to solve much, that violence should not be put off when closed are closed only, namely: vmware-related services are not enabled.

1) Select the icon to the desktop, right-click the computer mouse, the pop-up menu, click the button [Management]

2) management interface pops up, in the current interface, locate the [Services and Applications], click in front of the arrow, expand all options,

3) expansion options, click [Service] button,

4) The next pop-up interface [service], Find All the service vmware, vmware ensure that all services are open (about 5)

Reopen the virtual machine --------

OK, okay!

---

Individual lessons: personal feeling is shutdown process is right, but because I do not know which in the end lead to the lock, I could be wrong end of the process, because I remember I also did not find the "Task Manager" inside which process tutorial, I will simply violence fully closed, so it may appear "unable to connect MSK ..." kind of problem, computer right, "management", open to the open on the line (as detailed above).

 Forced to quit after a power failure or VMware virtual machine appear The virtual machine appears to be in u ...

 

        Today, running a virtual machine when the phenomenon appears crash, after forcibly closed, the original does not shut down the virtual system does not start properly, check the internet about problem solving.

        Solution:

        To the appropriate virtual machine VM directory delete% name% .vmx.lck folder or file to which

        In my humble opinion:

        我们打开任务管理器，会发现vmware.exe和vmware-vmx.exe两个重要的进程。其中vmware-vmx.exe是主程序，虚拟机在这个进程下运行；VMware.exe是外壳程序，负责显示vmware-vmx.exe中运行的虚拟系统并解释传送各种命令和操作，是我们最常用的VMware用户界面，该程序可重入即同时打开多个。

        因为VMware Workstation是可重入的，为了避免同一个虚拟系统同时被多个VMware.exe打开操作，造成错误，所以每个VMware打开相应的虚拟机选项卡时都会先检查该虚拟机根目录下是否有*.vmx.lck的文件夹并验证其中的文件，如果该文件中包含合法生成的uuid（通用唯一识别码），那么将无法打开该虚拟机的选项卡，并出现下面的错误提示：                    

        Take Ownership之后会出现以下提示：

        如果没有相应的合法文件，就会在该虚拟机根目录下生成*.vmx.lck文件夹，并在该文件夹下生成一个包含uuid的*.lck文件，打开虚拟机选项卡，并从主程序接收显示信息。

        这个*.lck文件可以用记事本编辑。里面是uuid={一串字母数字}，uuid是通用唯一识别码 (Universally Unique Identifier)，它的特点就是唯一性。为的是同时只有一个vmware.exe能接受主程序的显示，并对虚拟机操作。lck是lock的缩写，即对请求资源的锁定。

       VMware 虚拟机在运行时会在相应的虚拟机目录下生成三个文件*.vmx.lck，*.vmdk.lck，*.vmem.lck文件夹，里面包含以*.lck命名的文件。 其中的*.vmx.lck是伴随vmware.exe中选项卡的打开时生成的；另外两个是关于虚拟磁盘和内存的使用的，它们伴随着虚拟系统的运行而产生。如果关闭VMware.exe让虚拟机在后台运行，*.vmx.lck文件夹会消失另外两个则不会。

        在VMware.exe中打开某个虚拟机选项卡时，会短暂生成*.vmsd.lck的文件夹，估计这个是在最初传送数据（send data)时生成的，防止多个外壳程序同时请求打开虚拟机。