VMware Communities
kleinebu
Contributor
Contributor
Jump to solution

vmrun suspend/start and lock files

Hello.

We are running VMWare Workstation 14 Pro (Version 14.1.1) and are running a backup script on the weekend.

The script utilizes "vmrun suspend", after which we do the backup and then get the machine up again by running "vmrun start ... nogui".

On the machine the VMWare Workstation window is always opened and "vmrun suspend" seems to be fine, the Workstation will update the gui after running that command.

However we can't get the machine up again with "vmrun start". It says: Error: The file is already in use.

I figured out, that when I close the tab of the vm in the Workstation, then it works. But why am I not allowed to have the tab opened? The vm is suspended, so why is the opened tab a problem?

It seems that the error message is in regard to the existing of a .lck file.

While the vm is running, there is a .lck file. After suspending however there still is a .lck file (this time with a different name though).

Strange behaviour. All I want is to have Workstation open (with tabs...) and be able to use vmrun du suspend and start a machine.

0 Kudos
1 Solution

Accepted Solutions
Scillonian
Hot Shot
Hot Shot
Jump to solution

As long as you have a tab open to a VM a .lck lock file will exist. The .lck files exist to stop another instance of a VMware application from opening the VM. This is important when the VM is a Shared VM or the VM resides on a network location such as a NAS.

I don't know if this is scriptable but you could try suspending the VM, exit the GUI, run backup, resume VM, then restart GUI.

View solution in original post

0 Kudos
2 Replies
Scillonian
Hot Shot
Hot Shot
Jump to solution

As long as you have a tab open to a VM a .lck lock file will exist. The .lck files exist to stop another instance of a VMware application from opening the VM. This is important when the VM is a Shared VM or the VM resides on a network location such as a NAS.

I don't know if this is scriptable but you could try suspending the VM, exit the GUI, run backup, resume VM, then restart GUI.

0 Kudos
kleinebu
Contributor
Contributor
Jump to solution

That was my idea, too. I can exit the gui (workstation) before doing the backup and then restart it by script after the backup is done.

Thanks for your help.

0 Kudos