Overriding the file lock? (b5)

B

Bill

Bit poster
I apologize if this has come up in a previous thread, but I couldn't find anything about it. Since installing beta 5, whenever I start up Workstation, I get a warning that the .pvs file for my VM is already in use and asks if I want to override the lock. I'm the only one using it, so I know it's not open, and the message comes up whether I quit the program properly before opening it again, or whether it was force quit/crashed.

If I override the lock, it doesn't seem to cause any problems, but it'll still produce that error message the next time I start the program.

Is this happening for anyone else?
 
I haven't noticed it being a problem for me. I have only gotten the warning about the virtual machine being in use if it is in use, or if Parallels didn't shut down cleanly.
The lock file is in the same directory as your .pvs file, and is named .<vmname>.pvs.lock. Before launching parallels, you can see if the file exists and if you get a warning from parallels. If the file does exist, you can use lsof to look and see if there really is a process that is using it, or if it's just a stale lock file: sudo lsof | grep pvs.lock
 
You must log in or register to reply here.
Back
Top