Custom Query (16363 matches)
Results (1945 - 1947 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #9923 | obsolete | Machine stopped (VMX_INVALID_GUEST_STATE) | ||
| #9927 | obsolete | guestcontrol exec with --wait-stderr or --wait-stdout hangs the VBoxManage process and prevents further execs | ||
| Description |
I just upgraded from 4.0.x to 4.1.6 and noticed that my scripts that start internet explorer in the windows VM started hanging (don't if executed from terminal even ctrl-c has no effect, only kill -9 helps). What's even worse is that no new commands can be executed in the vm until the process originally started in the vm dies. Upon a closer look, I realized that it was --wait-stderr and --wait-stdout flags that caused this issue after removing them the process doesn't hang any more. My original command: {{
}} after removing the two flags, the process doesn't hang any more and everything works just like in 4.0.x |
|||
| #9929 | obsolete | Menu shows "Pause" but VM is suspended | ||
| Description |
I was running a couple of Solaris 10 VMs on a Windows Vista host. One of them was downloading data from the Internet (actually, doing a Solaris 11 Auto install into a "disk drive" that was dynamically growing.) Whilst doing the the host disk became full, and a VB popup appeared saying the system was suspended until you cleared some space. fair enough... I cleared some space. When I went to the Machine Menu in the VBox GUI, it was displaying "Pause" not "Resume". This was incorrect. When I clicked "Pause" the system resumed execution. |
|||

