virtualbox.org

I started out with the latest version (4.3.4). It installed from win7 x64 iso correctly once, but started to return "bootmgr is corrupt " or guru mediation errors, so I went back to 4.2. It installed no problem, but when I attempted to connect usb2 devices it said "USB device is busy with a previous request". I havent tried all my usb 2 stuff yet, but I did try 2 different ones. Filter, no filter, EHCI enabled/disabled, same diff.

It seems there is some collision, but where and of what I have no clue.

I dont need to access the virtual machine more than once every 2-3 months, so if there is a solutionm involving win8 safe mode I can definitely live with that.

Many thanks in advance

Joe

Phil_Graves wrote:Filter, no filter, EHCI enabled/disabled, same diff.

Hardly "same diff". EHCI == USB2, so disabling it doesn't seem like a useful way to test a USB2 device. It must be enabled, and you should have a filter too, and plug the device in after the guest has booted and reached its desktop. Also you must install the extension pack on your host, with version matching the main VBox app version.

Try Googling for "busy with a previous request".

Ok, at the very least thank you for a formal procedure, I will test this in a few hours. I have in fact installed extension pack on the client. Let me ask this; if I did not do it the way you described the first time, is it possible that I screwed up the guest?

Also, does it matter if the usb device is connected when the host boots?

No, if the guest has never recognized the device then it can't have made any permanent decision about it either - so just get the connection procedure right and it should work ok.

No, it doesn't matter that the device is connected to the host when it boots. It should however be disconnected from the host before you boot the guest, especially the first time (before the redirection filter is installed).

same story. A question; the guest machine resides on a (different) usb volume. Does it need to be on the system volume?

I notice you say volume instead of drive. If you are trying to get the VM to own the drive it's located on - that will never work. The VM won't be able to access its own boot drive, since all such accesses go through the host.

If the volumes are on different drives then this shouldn't be relevant.

no, different drives. I came across the same-drive issue already.

Well then the issue is straightforward - the error message means that the host is already using the drive. Some time ago I wrote down my generic procedure (here) for mounting USB mass storage devices in Windows guests.