Custom Query (16363 matches)
Results (2305 - 2307 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #10944 | obsolete | USB support problem with VB 4.2 | ||
| Description |
OS: Mac OSX 10.7.4 and last VB 4.2 with extension pack
Desc.:
After update to last version I was lost possibility to connect any USB devices.
All trail to connection end with same error messages like this: <<< start error message >>> Failed to attach the USB device Prolific Technology Inc. USB-Serial Controller D [0400] to the virtual machine lsd. USB device 'Prolific Technology Inc. USB-Serial Controller D' with UUID {d9e08bc1-1d2f-4452-927d-e59ec81e9e4e} is busy with a previous request. Please try again later.
Result Code: NS_ERROR_INVALID_ARG (0x80070057)
Component: HostUSBDevice
Interface: IHostUSBDevice {173b4b44-d268-4334-a00d-b6521c9a740a}
Callee: IConsole {db7ab4ca-2a3f-4183-9243-c1208da92392}
<<< end of error message >>> On VB 4.1 I have no problem - I try reinstall VB, extension and so on but without success. Michal Janicek |
|||
| #10952 | obsolete | Cannot uninstall virtualbox | ||
| Description |
I cannot uninstall VB. It always rolls back and I'm left with an old version. I start the uninstall process from windows "Uninstall software". Version: v4.1.8 r75465 I followed these steps: https://www.virtualbox.org/wiki/MSI_Logging And this is the C:\windowns\inf\setupapi.app.log that seems to fail: >>> [SetupInstallServicesFromInfSectionEx - VBoxNetFlt.ndi.Remove.Services]
>>> Section start 2012/09/17 18:47:35.234
18:47:35.234 cmd: C:\Windows\system32\MsiExec.exe -Embedding F280C8CD7A43D7E817F49E80E2761645 M Global\MSI0000
<<< Section end 2012/09/17 18:47:35.234
<<< [Exit status: FAILURE(0xe0000101)]
|
|||
| #10959 | obsolete | XP VM freezes host on Linux kernel 3.5. Fine on 3.4. | ||
| Description |
Running Sabayon Linux 10 on a 12 proc 24G box, which normally would be running Kernel 3.5 about now... but after upgrading to 3.5, reinstalling VB modules, and starting an XP VM... VB will hang my system; no blank screen, just frozen. This has occured with 4.1.20 as well as 4.2. I have managed to boot a very simple XP session and bring it back down (I have yet to see how long it can run before freezing the box tho) but one XP VM in particular, my most important one go figure, will consistantly hang the system with the windoze status bar still going. Main differences between the 2 VMs are CPU: 2 vs 8, Mem: 2G vs 8G and USB access to a card reader. Backing off to 3.4 and everthing works great. Nothing in the logs. I'm befuddled. |
|||

