VirtualBox

Ticket #8579 (new defect)

Opened 3 years ago

Last modified 14 months ago

VBoxManage: error: The machine 'oracle_vb1' is already locked by a session

Reported by: silvex Owned by:
Priority: major Component: other
Version: VirtualBox 4.0.4 Keywords: sles 10 sp3
Cc: Guest type: Linux
Host type: Linux

Description (last modified by frank) (diff)

I started my vbox from gui. I then did a init 0 in the vm and it is grey out in the gui. I tried the commands below. How do I unlock this Vm without rebooting the host ? The vm does not show in the procs list either. I am runing VirtualBox-4.0-4.0.2_69518_sles10.1-1.x86_64.rpm

The host is a SLES 10 SP3 Linux cms-dev04 2.6.16.60-0.59.1-smp #1 SMP Thu Jan 14 18:30:10 UTC 2010 x86_64 x86_64 x86_64 GNU/Linux

[code]

# vboxmanage startvm oracle_vb1 VBoxManage: error: The machine 'oracle_vb1' is already locked by a session (or being locked or unlocked) VBoxManage: error: Details: code VBOX_E_INVALID_OBJECT_STATE (0x80bb0007), component Machine, interface IMachine, callee nsISupports Context: "LaunchVMProcess(a->session, sessionType.raw(), env.raw(), progress.asOutParam())" at line 362 of file VBoxManageMisc.cpp

# vboxmanage startvm oracle_vb1 --type headless VBoxManage: error: The machine 'oracle_vb1' is already locked by a session (or being locked or unlocked) VBoxManage: error: Details: code VBOX_E_INVALID_OBJECT_STATE (0x80bb0007), component Machine, interface IMachine, callee nsISupports Context: "LaunchVMProcess(a->session, sessionType.raw(), env.raw(), progress.asOutParam())" at line 362 of file VBoxManageMisc.cpp

# vboxmanage discardstate oracle_vb1 VBoxManage: error: The machine 'oracle_vb1' is already locked for a session (or being unlocked) VBoxManage: error: Details: code VBOX_E_INVALID_OBJECT_STATE (0x80bb0007), component Machine, interface IMachine, callee nsISupports Context: "LockMachine(a->session, LockType_Write)" at line 404 of file VBoxManageMisc.cpp

# vboxmanage list vms "oracle_vb1" {28c0eb22-8893-4ce7-b5e7-57611914024b} <<<< this is the one "locked". "laxdev001" {541200f0-456d-4d7f-8746-a732b4f14df3} "laxdev002" {5f8fd40b-7243-4063-9026-03aaa77a155a} "laxdev003" {0db035fe-4af1-409a-983d-1140952c722a} "laxdev004" {72c390be-64e5-4fcf-87b4-7881e76cc904} "laxdev005" {c28e57d2-1a43-459c-8e20-aebb7b8174fd}

# ps -ef | grep virtualbox root 7834 7704 0 Feb28 pts/1 00:52:04 /usr/lib/virtualbox/VirtualBox root 7849 1 0 Feb28 ? 00:33:46 /usr/lib/virtualbox/VBoxXPCOMIPCD root 7855 1 0 Feb28 ? 01:08:19 /usr/lib/virtualbox/VBoxSVC --auto-shutdown root 14836 7855 2 Mar01 ? 08:11:09 /usr/lib/virtualbox/VirtualBox --comment laxdev001 --startvm 541200f0-456d-4d7f-8746-a732b4f14df3 --no-startvm-errormsgbox root 15483 7855 1 Mar08 ? 02:34:15 /usr/lib/virtualbox/VirtualBox --comment laxdev002 --startvm 5f8fd40b-7243-4063-9026-03aaa77a155a --no-startvm-errormsgbox root 19706 19602 0 09:08 pts/0 00:00:00 grep virtualbox root 24475 7855 1 Mar09 ? 02:12:00 /usr/lib/virtualbox/VirtualBox --comment laxdev003 --startvm 0db035fe-4af1-409a-983d-1140952c722a --no-startvm-errormsgbox root 28853 7855 1 Mar10 ? 01:29:45 /usr/lib/virtualbox/VirtualBox --comment laxdev004 --startvm 72c390be-64e5-4fcf-87b4-7881e76cc904 --no-startvm-errormsgbox

code

Attachments

VBox.log Download (92.5 KB) - added by silvex 3 years ago.
VBox.log.1 Download (93.4 KB) - added by silvex 3 years ago.

Change History

Changed 3 years ago by silvex

Changed 3 years ago by silvex

comment:1 Changed 3 years ago by Perryg

Adding name to track resolution

comment:2 Changed 14 months ago by anentropic

I have exactly the same problem. I have tried the various vboxmanage commands above with identical symptoms. I am using VirtualBox via Vagrant 1.0.6

Also:

$ vboxmanage controlvm "215a836e-6efe-49d5-b844-9df9accc46b7" poweroff
VBoxManage: error: The virtual machine is being powered down
VBoxManage: error: Details: code VBOX_E_INVALID_VM_STATE (0x80bb0002), component Console, interface IConsole, callee nsISupports
Context: "PowerDown(progress.asOutParam())" at line 168 of file VBoxManageControlVM.cpp

vboxmanage --version reports:

4.1.12_Ubuntur77245

seems no obvious way to kill the box?

comment:3 Changed 14 months ago by frank

  • Description modified (diff)

anentropic, there were a lot of bug fixes since version 4.1.12. Please update to 4.1.24 or even better to 4.2.6 and try again.

Note: See TracTickets for help on using tickets.

www.oracle.com
ContactPrivacy policyTerms of Use