geerlingguy/ansible-for-devops

VirtualBox error: The machine is already locked by a session

sangammis opened this issue · 2 comments

sangammis commented

$ vagrant up scriptbox
Bringing machine 'scriptbox' up with 'virtualbox' provider...
==> scriptbox: Checking if box 'geerlingguy/centos7' version '1.2.27' is up to date...
==> scriptbox: Clearing any previously set forwarded ports...
==> scriptbox: Clearing any previously set network interfaces...
==> scriptbox: Preparing network interfaces based on configuration...
scriptbox: Adapter 1: nat
scriptbox: Adapter 2: hostonly
==> scriptbox: Forwarding ports...
scriptbox: 22 (guest) => 2222 (host) (adapter 1)
==> scriptbox: Running 'pre-boot' VM customizations...
==> scriptbox: Booting VM...
There was an error while executing VBoxManage, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.

Command: ["startvm", "5b3fa4f2-c6ec-4b11-bc27-972959a39875", "--type", "headless"]

Stderr: VBoxManage.exe: error: The machine 'BashScripts_scriptbox_1711194524335_50351' is already locked by a session (or being locked or unlocked)
VBoxManage.exe: error: Details: code VBOX_E_INVALID_OBJECT_STATE (0x80bb0007), component MachineWrap, interface IMachine, callee IUnknown
VBoxManage.exe: error: Context: "LaunchVMProcess(a->session, sessionType.raw(), ComSafeArrayAsInParam(aBstrEnv), progress.asOutParam())" at line 881 of file VBoxManageMisc.cpp

saghosh8 commented

The error message indicates that the VirtualBox VM is already locked by a session, meaning that it might be running or in some intermediate state. To resolve this issue, you can try the following steps:

Step-by-Step Solution

  1. Check VirtualBox GUI:

    • Open the VirtualBox application on your machine.
    • Look for the BashScripts_scriptbox_1711194524335_50351 VM.
    • Check if it is running or in a paused state. If it is, you might want to shut it down or reset it.

  2. Stop the VM:

    • If the VM is not responding in the VirtualBox GUI, you can use the command line to forcefully stop it.
    VBoxManage controlvm "BashScripts_scriptbox_1711194524335_50351" poweroff
    • Alternatively, you can list all running VMs and their states:
    VBoxManage list runningvms
    • To list all VMs:
    VBoxManage list vms

  3. Remove the Lock:

    • If the VM is still locked, you may need to remove the lock manually.
    • Navigate to the VirtualBox VMs directory (usually located in ~/VirtualBox VMs or C:\Users\<your_username>\VirtualBox VMs).
    • Locate the folder corresponding to your VM (BashScripts_scriptbox_1711194524335_50351).
    • Look for any lock files (.lck) and remove them.

  4. Restart Vagrant:

    • After ensuring the VM is no longer locked, try to start the VM again using Vagrant.
    vagrant up scriptbox

  5. Destroy and Recreate the VM (if the above steps do not work):

    • As a last resort, you can destroy the VM and recreate it.
    vagrant destroy scriptbox
vagrant up scriptbox

Summary of Commands

# Check running VMs
VBoxManage list runningvms

# Power off the problematic VM
VBoxManage controlvm "BashScripts_scriptbox_1711194524335_50351" poweroff

# Destroy and recreate the VM using Vagrant (if needed)
vagrant destroy scriptbox
vagrant up scriptbox

Following these steps should help you resolve the issue with the locked VirtualBox VM.

Intertranslations commented

I kindly request a moderator to change the title of the issue. Please help is hardly a suitable title.

  • 👍1