Super User is a question and answer site for computer enthusiasts and power users. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I recently had my system crash while it was running OSX Lion in a VMWare VM (VMWare Workstation 8; I use the VM to do iOS development without needing to actually buy/use a Mac).

The OSX VM is tempermental enough on a good day, but upon trying to restart it after the crash it promptly started greeting me with some very unhelpful "Failed to lock file" error messages that completely prevented the VM from booting.

Any suggestions on how to fix this?

share|improve this question

migrated from Aug 3 '12 at 15:12

This question came from our site for professional programmers interested in conceptual questions about software development.

up vote 8 down vote accepted

The problem in my case was that the unclean shutdown of the VM had left behind a number of "lock" files in the filesystem. The error message says what specific lock file is causing the problem, though it does stop at the first lock it encounters. So if you fix one lock and then continue to get a similar message, check to see where the new lock that it's complaining about is.

I ended up having to track down 4 or 5 "*.lck" files scattered across a couple different locations in my filesystem. Deleting (or, if you're paranoid like me, moving to a new location) all of these lock files allowed the VM to reboot. It took a couple of tries for the reboot to actually take. As I mentioned, the VM is tempermental even under the best of circumstances.

Also note that there should be a "vmware.log" file that should also contain useful information about which lock file is causing the problem, and possibly any number of other issues that may be preventing the VM from starting. In my case this file was located in the same filesystem directory as the VM's primary virtual disk file ("*.vmdk").

Further information is available here:

share|improve this answer

Here's my experiences with this subject.

The solution was understood at the sight and study of few generated folders and lck files from its last session. That's a reason for keeping logs.

  • Copy the .lck file in the DNS.vmx.lck/M32944.lck

  • Paste in the DNS.vmdk.lck/folder

  • You will see another .lck file, M648383.lck

  • Rename M32944.lck to M648383.lck (cut M648383.lck to desktop and rename)

Give it a try if you encounter a situation with VMPlayer when it crashes on every start. It could happen if you don't shut it down properly e.g. if you use Taskmanager to shut it down.

share|improve this answer

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .