virtualbox.org

Hello,

I've gone through the forums, and there seems to have been many topics about USB 2.0 on VB. However, from what I can tell, the later versions of VB have all but fixed this...

However, I cannot get it to work on Windows 7 (which is the only OS I currently run VB on)...

USB works just fine using USB 1.1, but if I enable the USB 2.0 controller, it does not work.

Windows 7 x64 host, Windows XP/32 guest.

Is there something that I'm just not doing right, or does this not work?

Thanks for the help.

-ET

You need to check you MB chipset. It sounds like you only have support for USB 1.1
You should be able to see the Boot screen or from system information from inside Win 7

Perryg wrote:You need to check you MB chipset. It sounds like you only have support for USB 1.1
You should be able to see the Boot screen or from system information from inside Win 7

USB 2.0 works fine on the host system. Only in the VM does it not work... When I enable USB 2.0 in the VM and connect a USB device to the VM, It's unable to connect it up. Just kinda sits there. If I try to connect it again, it tells me the device is busy...

Has anyone confirmed that USB 2.0 works with Win7 as the host? I'm running an Win7 RC on a Core2Duo Processor, on an Intel BLKDP35DPM main board...

-ET

I experienced the same. USB is working with 2.0 disabled. When USB 2.0 is enabled, selecting a USB device does nothing except changing its state from "busy" to "captured" (without a "check mark" in front of the device name).

I'm using windows7RC x64 host, ubuntu 9.04 x86 guest. i7 920 cpu.

Perhaps it's an W7 issue. Keep in mind that not all features work properly in this version. It's possible USB is one of them. There is a driver used for this, so that might be the problem. Some users have also noted that USB2 didn't work on their VM, while they failed to mention which update level they have. XP before SP1a doesn't support USB 2.0. Always keep the Guest up to date with patches and updates.

As for the Ubuntu Guest, I have no idea. It should work. What does lsusb say? You might want to open a new topic in Linux Guests if it goes too far off topic.

Sasquatch wrote:Perhaps it's an W7 issue. Keep in mind that not all features work properly in this version. It's possible USB is one of them. There is a driver used for this, so that might be the problem. Some users have also noted that USB2 didn't work on their VM, while they failed to mention which update level they have. XP before SP1a doesn't support USB 2.0. Always keep the Guest up to date with patches and updates.

This is why I posted this here. I was wondering if anyone had usb2 working with W7 as the host.

-ET

ps, The Guest is XP SP2. The only update I did was to do the required patches to run windows update (genuine validation, BITS, etc), and I installed the updated windows installer. Since the zune is the only thing that this VM does, then there was no need to install anything else. This software ran just fine, including USB2, on the exact same setup (installed using the same CD) on a regular machine. The USB2 problem only showed up when I moved it to a VM...

I forgot to mention that the USB2 issues from others didn't involve Windows 7. Are you sure that your XP VM is at least SP1a, SP2 or 3 preferred. Well, even all that, it still doesn't explain why it won't grab the device when you select USB2. Have you tried a Linux liveCD on that VM? It won't touch the system on it, only boot Linux from cd. You can then see if devices are passed through properly with USB2 enabled.

I personally never got USB to work properly. It takes some doing to make it work but it does with USB2. Anyways I am going to take the time to make a general statement. For a couple of weeks I have been part of a VMWare beta for the upcoming version of VMWare Workstation and it has worked alot better for me (even though it is a debug version). Beyond that I can say nothing of it's functionality (NDA -- sorry) but this bit is true for all versions. VMWare handles USB devices by sending a signal to the OS to stop the device which forces unmounting it in most cases. Then it has the OS scan for the device again but makes it run the device through the filter (like how VirtualBox does now). The difference is that it doesn't ever seem like VirtualBox sends the signal to Windows to stop the device so that the OS knows to transfer it to the VM. Just a thought.