Ticket #9650 (reopened defect)

Opened 3 years ago

Last modified 10 months ago

VBoxManage guestcontrol hangs on execute

Reported by: Branan Owned by:
Priority: major Component: guest control
Version: VirtualBox 4.1.2 Keywords:
Cc: Guest type: other
Host type: other

Description (last modified by frank) (diff)

Example session:

VBoxManage --nologo guestcontrol 'Uru Build Server' execute --image 'C:\windows\notepad.exe' \
 --username buildbot --password password --wait-stdout --verbose
Waiting for guest to start process ...
Process 'C:\windows\notepad.exe' (PID: 2104) started
Waiting for process to exit ...

Once I close notepad (or the process terminates on its own), VBoxManage does not end, instead it just hangs at "Waiting for process to exit ...". SIGINT has no effect on VBoxManage at this point.

If I kill the VBoxManage process and try to run a new instance of it, it will hang at "Waiting for guest to start process ..." (as if some sort of lock was never released by the killed process?). No process is ever launched in the VM. As far as I can tell, this can't be fixed without restarting the VM.

The VM is pretty lightweight - currently the only program installed is Visual Studio.


VBox.log Download (100.3 KB) - added by Branan 3 years ago.

Change History

Changed 3 years ago by Branan


comment:1 Changed 3 years ago by frank

  • Component changed from other to guest control

comment:2 Changed 20 months ago by SamuraiJack

Confgirm this. This happens for me too, and only cure is to restart the guest.

comment:3 Changed 20 months ago by SamuraiJack

My VBox version is 4.1.18, host is Ubuntu 12.04, guest Windows 7

comment:4 Changed 20 months ago by SamuraiJack

comment:5 Changed 20 months ago by SamuraiJack

comment:6 Changed 17 months ago by frank

  • Status changed from new to closed
  • Resolution set to fixed
  • Description modified (diff)

There were many changes in guest execute in VBox 4.2. Please reopen if still relevant with VBox 4.2.4.

comment:7 Changed 11 months ago by insecure

The problem still occurs with VirtualBox 4.2.12 (Host: Windows 7 32-Bit, vbox 4.2.12; Guest: Debian 32-Bit, vbox additions 4.2.12).

Furthermore the problem does not seem to be related to #10616 unlike mentioned in previous comments.

comment:8 Changed 10 months ago by insecure

  • Status changed from closed to reopened
  • Resolution fixed deleted
Note: See TracTickets for help on using tickets.
ContactPrivacy policyTerms of Use