Opened 13 years ago
Closed 10 years ago
#10616 closed defect (obsolete)
guestcontrol execute hangs after snapshot
Reported by: | orval | Owned by: | pentagonik |
---|---|---|---|
Component: | guest control | Version: | VirtualBox 4.1.16 |
Keywords: | Cc: | ||
Guest type: | Linux | Host type: | Mac OS X |
Description
Since 4.1.12 VBoxManage hangs when using guestcontrol execute after a snapshot has been taken.
I am running OS X 10.7.3. The guest is CentOS 5 64-bit with the latest additions.
Here is an example:
$ VBoxManage guestcontrol snaptest execute --username=root --password=snaptest --verbose --wait-stdout --image /bin/ls -- -c 'xyz' Waiting for guest to start process ... Process '/bin/ls' (PID: 7) started Waiting for process to exit ... Exit code=2 (Status=2 [successfully terminated], Flags=0) $ VBoxManage snapshot snaptest take s1 --pause 0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100% $ VBoxManage guestcontrol snaptest execute --username=root --password=snaptest --verbose --wait-stdout --image /bin/ls -- -c 'xyz' Waiting for guest to start process ... Process '/bin/ls' (PID: 8) started Waiting for process to exit ...
This never returns. If I log in to the guest and restart vboxadd and vboxadd-service, then it works again.
Attachments (2)
Change History (7)
by , 13 years ago
comment:2 by , 13 years ago
Owner: | set to |
---|---|
Status: | new → assigned |
Took a quick peek into the log you provided -- there's no hint what went wrong after the snapshot has been taken. I'll have to try to reproduce this myself in order to debug this issue further.
comment:3 by , 12 years ago
I have been seeing this as well. I'm currently using Mac OS 10.7.5 and VirtualBox 4.2.10.
comment:4 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):
- start VM
- vboxmanage guestcontrol exec works
- take snapshot
- vboxmanage guestcontrol exec does not work
Starting the VBoxService in the guest with -vvvv does not show anything when using the execute command, just as if the guest service is not even noticed.
After closing the VM and restoring the snapshot, the execute command works again!
comment:5 by , 10 years ago
Resolution: | → obsolete |
---|---|
Status: | assigned → closed |
Could you please also provide debug logs of VBoxService running on the guest?
To start VBoxService in debug mode with verbose logging on a Linux guest:
As root, do a:
# /etc/init.d/vboxadd-service stop
# VBoxService -vvvv --logfile /tmp/VBoxService.log
This will start VBoxService in background, logging to /tmp/VBoxService.log. After the issue appeared again, please provide the logfile located in /tmp/VBoxService.log on the guest.
Thanks!