virtualbox.org

cableghost2 wrote:how do I discover how my config is and how do I change it?

As I mentioned above, I don't use 64bit Windows, so I cannot give you detailed instructions.

cableghost2 wrote:I will note, I receive the install hardware dialogs when connecting fresh USB devices to my host...why would they be silenced when using VB?

Perhaps because the driver certificates in the VBox drivers are not among your trusted providers. I hope by now that I've gotten across the fact that the driver in question is not "the" driver for the device, it's a VirtualBox filter driver for that device.

If I might suggest that the issue may be because of the VMware filters being installed? I have tested VMware and VirtualBox together and found many issues that caused conflicts including Video drivers, & Network drivers. With VMw installed and looking at the VBox settings it appeared that the VBox drivers were actually tied to the VMw drivers instead of the host.

Admittedly I have not tested this (VBox with VMw installed) in regards to USB, but I know for a fact that USB can be a really big issue in Windows. There are a lot of apps and drivers that can cause a conflict. Mine turned out to be a HP printer. The extra software installed was the issue in my case and not the specific print driver. The fact that you have a lock-up indicates the drivers are being loaded but accessing reserved memory, Etc (IMHO).

mpack wrote:Perhaps because the driver certificates in the VBox drivers are not among your trusted providers.

This makes sense. Unfortunately, I have Win 7 HP, which does not have 'Local Group Policy', so I'm not certain how to check otherwise.

Perryg wrote:If I might suggest that the issue may be because of the VMware filters being installed? I have tested VMware and VirtualBox together and found many issues that caused conflicts including Video drivers, & Network drivers. With VMw installed and looking at the VBox settings it appeared that the VBox drivers were actually tied to the VMw drivers instead of the host.

This isn't the issue. I only installed VMware after the VB incident, so no VMware drivers were installed at the time.

Perryg wrote:Admittedly I have not tested this (VBox with VMw installed) in regards to USB, but I know for a fact that USB can be a really big issue in Windows. There are a lot of apps and drivers that can cause a conflict. Mine turned out to be a HP printer. The extra software installed was the issue in my case and not the specific print driver.

This makes sense. Is there a way to test what driver may be conflicting with the VB USB filter drivers, w/o uninstalling software/devices?

Perryg wrote:The fact that you have a lock-up indicates the drivers are being loaded but accessing reserved memory, Etc (IMHO).

On the same principle...how may I determine which IRQ VB USB filter drivers need, and then maybe I can visually see via Device Manager what other device is occupying that IRQ?

I use MS sysinternals suite to track down issues in Windows.

I believe I've figured out the root of the problem...sound. Since VB sound is virtualized, I don't believe it's possible to use USB speakers, and my headset (Savi W740) base is USB-connected.

How I determined this...Plantronics updated the software drivers and assuming that would be it, I restarted the VM with the headset connected with the appropriate VM filter selected. The VM recognized my headset, however, when I attempted to make my headset the default sound for Skype, the VM froze.

There seems to be a general issue with sound hardware and USB, there has been few topics lately about this.
You can also find 2 opened bugs for this kind of stuff : Ticket #11215 and Ticket #11314