Custom Query (16363 matches)
Results (2380 - 2382 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #11186 | obsolete | Guest aborts after xsane fails to access scanner on USB | ||
| Description |
Host: Slackware 14.0 64 bit. (have seen error with Slackware 13.37 64 bit host as well) Guest is also running Slackware 14.0 64 bit. If I try to run xsane on the guest, sometimes it will work the first time. However, afterwards if I disconnect the USB and then reconnect the USB under the Devices menu and then try to start up xsane, it will give a message indicating it failed to connect to the scanner. (Failed to open device 'brother2:bus2;dev3':Invalid argument. After a minute or so, the guest will abort. I do not see this error with a Slackware 13.37 64 bit guest. I also do not see this error if I run xsane on the Slackware 14.0 64 bit physical machine or the host machine either. In logs included, xsane failed to connect the first time through. I first saw this error with VirtualBox 4.2.0. I've upgraded to VirtualBox 4.2.4 and still see the same error. |
|||
| #11188 | obsolete | USB drive. | ||
| Description |
I would like to request the feature of an optional popup box to ask you which vm if any you want the USB Drive to show in. |
|||
| #11189 | obsolete | Error reading from process error when launching application on guest machine | ||
| Description |
I have Win7x64 installed on Host and Guest machine. When I start any application on client side using guestcontrol Ex.:VBoxManage guestcontrol "D:\VMS\VM_TWO\VM_TWO.vbox" execute --image "c:\Windows\System32\calc.exe" --username "uname" - -password "pass" --wait-exit --wait-stdout VBoxService at client side starts using at least 50% of processor time. After 20-35 seconds I have next error. Ex.: VBoxManage.exe: error: Reading from process "c:\Windows\System32\calc.exe" (PID 2524) failed: VERR_TIMEOUT. But on client side launched application continue working (in that case it's calc.exe) and VBoxService no use processor any more. When I use guestcontrol without --wait-stdout, I dont have this error and VBoxService dont use processor so much. In my case I need to use --wait-stdout. Do you have any suggestion, how I can fix this problem. I have the same problem with version 4.2.4 Log file attached. Thanks, Mike |
|||

