after "vagrant package" failed due to out of disk memory, machine is locked (VBOX_E_INVALID_OBJECT_STATE), cannot start or stop

[andi_the_meier]

I started a "vagrant package" session which should export the current VM into a vagrant box file. During packaging, C: ran out of space so the "vagrant package" did not finish.

After that, I reclaimed some space on C:, so there are again 32 GB free.

But now, the VBox VM seems to be in some invalid state:

Try to start using "vagrant up"

Command: ["sharedfolder", "add", "74bccde8-54d2-435e-8903-d0afd00c83f2", "--name", "opt_vagrant", "--hostpath", "F:/Docker/vagrantMESDAT"]

Stderr: VBoxManage.exe: error: The machine 'DockerHost' is already locked for a session (or being unlocked)
VBoxManage.exe: error: Details: code VBOX_E_INVALID_OBJECT_STATE (0x80bb0007), component MachineWrap, interface IMachine, callee IUnknown
VBoxManage.exe: error: Context: "LockMachine(a->session, LockType_Write)" at line 1012 of file VBoxManageMisc.cpp

Try to start in VirtualBox GUI

Doesn't work, all "Start/Stop/Resume"... commands are disabled (greyed out).

Try to start with VBoxManage.exe

List VMs:

C:\Program Files\Oracle\VirtualBox>vboxmanage list vms
"DockerHost" {74bccde8-54d2-435e-8903-d0afd00c83f2}
"UbuntuWiki" {bb5c61dc-92c2-46e4-80e6-49c69b87ac4d}

Try to start VM "DockerHost":

C:\Program Files\Oracle\VirtualBox>VBoxManage.exe startvm DockerHost
VBoxManage.exe: error: The machine 'DockerHost' 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(), env.raw(), progress.asOutParam())" at line 589 of file VBoxManageMisc.cpp

Try to poweroff:

C:\Program Files\Oracle\VirtualBox>VBoxManage.exe controlvm DockerHost poweroff
VBoxManage.exe: error: Machine 'DockerHost' is not currently running

[andi_the_meier]

VBox Log file (before vagrant package - after that there no log files anymore)

[Frank Mehnert]

If you disk ran out of space then VirtualBox was apparently not able to save the complete state. The state is part of files residing on the hard disk. If the files cannot be written due to short in disk space, some state is lost.

Modern desktop systems warn the user before the disk space is completely used.

[andi_the_meier]

Thanks for your answer. After these bad news, I tried something:

Interestingly (and luckily for me!) after upgrading from VirtualBox 5.0.0 to 5.0.12, I was able to start the VM - without any problems!

Seems like not all was lost and 5.0.12 did a better job of dealing with this orkus state.

=> Problem solved by updating.