This morning when I went to open my virtual machine (WS6.0), I got the following error:
Could not open virtual machine: C:\VM\Windows Server 2003 Enterprise Edition.vmx. This virtual machine appears to be in use.
I booted just this morning, so nothing else can be using it - I also verified that it wasn't running in the task manager. Is there anything I can do to get this back up?
I have the same problem,
where can i find the guest's folder??
The error message should say something like:
Could not open virtual machine: C:\VM\Windows Server 2003 Enterprise
Edition.vmx. This virtual machine appears to be in use.
which tells you where the VM is located.
I am having the same problem with Backtrack2. Does anyone have an answer to this issue?
I just booted up and it gave me this same error.
"Virtual machine appears to be in use"
I've experienced this problem too. After shutting down normally, when I booted up my PC all of my VM tabs were gone (seen this in 4.x & 5.x dont know why). Usually the solution is just to re-open the VM - but this does not work with 6.0. Even VMs not used for weeks failed 'in use'.
I have found 2 workarounds to the problem:
\- Rename your .VMX file & do a File, open
\- Rename / Delete the .LCK directory in the VM's folder.
Anyone know what the LCK directory is for??
A thousand thanks, sir! I have a number of Wksta 5.5 virtual machines that I have hundreds of hours of testing on. I was getting extremely frustrated until I searched the forums and found your post. Thanks again!
>Anyone know what the LCK directory is for??
Newer methods used by Workstation 6, instead of the older lock files. I'm not sure of the reasoning... you can search for some threads where KevinG posted some explanations of this if you're really interested.
Is there any important information in the .lck files that is worth keeping to help restore a VM that might have been damaged? My host locked up and I had to cold boot it, which left the .lck files in place and kept the VM from restarting.
I assume these lock files only contain transient info, but it would be good to know if they are worth saving...
Look at the filesize - there is no useful information stored in them.
They are created when VM opens a vmx or vmdk file so that a second VMware-instance knows that it should not open the file too.
Often VMware does not clean up properly and so sometimes you got to delete them manually.
When attempting to logoff a win2K VM, the VM crashed and I have been unable to restart the VM. There are no lck files, but I still receive the message about the machine being in use.
I found the lck files and folder. Took me a while to find them in the Roaming VM cache folder.
Message was edited by:
When I had that problem, I had copied my VM's to a drive with more disk space, but forgot to delete the old ones and redirect the VMWare client to look in the new location. I inadvertently thought I was using the VM from the new location when I was actually using the old one (where the lck files were). I'd double check that this isn't your case.