VirtualBox

Ticket #245 (closed defect: invalid)

Opened 7 years ago

Last modified 6 years ago

VBoxManage controlvm poweroff does not work when >= VBoxVRDP processes running

Reported by: thomasb Owned by:
Priority: major Component: other
Version: VirtualBox 1.3.8 Keywords:
Cc: Guest type: other
Host type: other

Description

I'm not able to poweroff my machines if there are more than two VBoxVRDP processes running. I will shortly summarize two test cases:

Working case

I have started VBoxSVC in a shell:

cd /opt/VirtualBox LD_LIBRARY_PATH=. ./VBoxSVC

In another shell I start a virtual box:

VBoxVRDP -startvm machine01

The machine boots up. To poweroff I issue:

VBoxManage controlvm isecom01 poweroff

This works perfectly, the VBoxVRDP process exits. Output of VBoxSVC is:

*********************************************
InnoTek VirtualBox XPCOM Server Version 1.3.8
(C) 2004-2007 InnoTek Systemberatung GmbH
All rights reserved.

Starting event loop....
[press Ctrl-C to quit]
Informational: VirtualBox object created (rc=00000000).
Informational: VirtualBox object deleted.

not working case

Now, again, I start a VBoxSVC process as described above. Also as described above I start VBoxVRDP. But this time, I start >= 2 different virtual boxes the same time.

As described above, I issue a poweroff command to one of the running virtual boxes. This gives no special output, but the VBoxVRDP process keeps on running. When I issue the poweroff a 2nd time, I get:

irtualBox Command Line Management Interface Version 1.3.8
(C) 2005-2007 InnoTek Systemberatung GmbH
All rights reserved.

[!] FAILED calling virtualBox->OpenExistingSession (session, uuid) at line 3860!
[!] Primary RC  = 0x80070005
[!] Full error info present: true , basic error info present: true
[!] Result Code = 0x80070005
[!] Text        = The machine 'machine02' does not have an open session
[!] Component   = Machine, Interface: IMachine, {fd443ec1-0009-4f5b-9282-d72760a66916}
[!] Callee      = IVirtualBox, {e1d95593-f579-4f47-b489-0b67181014e1}

So, well, I'm not able to poweroff my machine through VBoxManage. The only thing I can do is to either kill the VBoxVRDP process or press Ctrl-C in the shell.

Another interesting thing is the output of VBoxSVC:

*********************************************
InnoTek VirtualBox XPCOM Server Version 1.3.8
(C) 2004-2007 InnoTek Systemberatung GmbH
All rights reserved.

Starting event loop....
[press Ctrl-C to quit]
Informational: VirtualBox object created (rc=00000000).

Shouldn't I get a "object created" for every virtual box I start? And shouldn't I get a "object deleted" after the poweroff?

I tried to get rid of this error for a few hours now - but in any case, I wasn't able to proper poweroff my virtual boxes with VBoxManage in case I had >= 2 virtual boxes running...

Change History

comment:1 Changed 7 years ago by thomasb

As one further comment: When I issue the VBoxManage controlvm poweroff command, the following will be printed to ~/.VirtualBox/Machines/machine??/Logs/VBox.log:

00:03:57.909 ************** End of Guest state at power off ***************
00:03:57.909 Changing the VM state from 'RUNNING' to 'OFF'.
00:03:57.910 Changing the VM state from 'OFF' to 'DESTROYING'.
00:03:59.817 Changing the VM state from 'DESTROYING' to 'TERMINATED'.

So far, this looks allright - but the VBoxVRDP process is still running and not exited. Thus, I'm also not able to start the virtual box again. I have to terminate and restart VBoxSVC to be able to start that unproper poweroff-ed virtual box.

comment:2 Changed 7 years ago by thomasb

I was now able to solve the problem: I removed my ~/.VirtualBox/ and recreated it (by using my old .vdi files and creating a fresh VirtualBox configuration). Somehow, something inside my VirtualBox directory must have been broken.

I archived my old .VirtualBox directory. How could I further track this problem? I think it would be an improvement to have error messages indicating problems with .VirtualBox.

comment:3 Changed 6 years ago by frank

Could you attach the archived .VirtualBox directory?

comment:4 Changed 6 years ago by frank

  • Status changed from new to closed
  • Resolution set to invalid

No response for a long time, closing.

Note: See TracTickets for help on using tickets.

www.oracle.com
ContactPrivacy policyTerms of Use