Opened 14 years ago
Closed 10 years ago
#9650 closed defect (obsolete)
VBoxManage guestcontrol hangs on execute
Reported by: | Branan | Owned by: | |
---|---|---|---|
Component: | guest control | Version: | VirtualBox 4.1.2 |
Keywords: | Cc: | ||
Guest type: | other | Host type: | other |
Description (last modified by )
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 ... ^C^C^C
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.
Attachments (1)
Change History (10)
by , 14 years ago
comment:1 by , 13 years ago
Component: | other → guest control |
---|
comment:2 by , 13 years ago
Confgirm this. This happens for me too, and only cure is to restart the guest.
comment:6 by , 12 years ago
Description: | modified (diff) |
---|---|
Resolution: | → fixed |
Status: | new → closed |
There were many changes in guest execute in VBox 4.2. Please reopen if still relevant with VBox 4.2.4.
comment:7 by , 12 years ago
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 by , 12 years ago
Resolution: | fixed |
---|---|
Status: | closed → reopened |
comment:9 by , 10 years ago
Resolution: | → obsolete |
---|---|
Status: | reopened → closed |
VBox.log