virtualbox.org

I have some issues when trying to connect a Realtek 8152 USB 2.0 to Ethernet adapter to the guest.

I'm using Virtualbox 5.0.6 on a Windows 10 x64 host.
USB adapter has the latest drivers available from Realtek site installed in the host.
Virtualbox 5.0.6 extensions are installed, and I've performed the test by enabling USB 2.0 controller or USB 3.0 controller and connecting the device to USB 2.0 and USB 3.0 ports with the same results.

I connect the USB adapter in Windows, and it is correctly recognized as an Ethernet interface.

When I connect the USB to the Virtual Machine (Linux host), at first the adapter is disconnected from Windows, then a Virtualbox USB device appears. But, just after that, the Virtualbox USB device disappears and the device is re-connected to Windows as a CD-ROM drive.

I've previously used that device with Virtualbox and it got recognized well in the guest. But now it seems there is something wrong with the drivers and I always get the behaviour described above.

Is it possible to force the Virtualbox USB device to be reinstalled? (like if it was the first time you plug the device and Windows installs the Virtualbox USB drivers). I've tried removing and uninstalling all the Virtualbox USB devices from Windows device manager but with no result.

Thanks.

Generally you don't install an ethernet adapter directly to the GUEST, it's obvious from your post that you have done so previously.

Normally you connect an ethernet adapter only to the HOST, then setup a virtual NIC in the guest and bind the hosts adapter to it with one of the methods like bridged, NAT or Host only - depending on your needs.

If you really need / want to do this try setting a USB FILTER for the device rather than just allowing it to connect by selection form the guests device list. if you already have done so then I guess I am out of options.

Perhaps you are just starting out on this Windows 10 host and VB 5.X. Something has either changed with the way the Windows host handles the hardware or with VB in the way it presents hardware. Regardless, at least try and get the NIC to work by binding a virtual NIC to it through the HOST to make sure it's going to work with this combination of OS / software.

In this particular case I need the Linux guest to recognize the adapter as a USB device since I have to test it that way, I can't set up a virtual NIC.

If I set a USB filter it is the same case, I can see a virtualbox device being plugged, but it is then disconnected and connected to the host as a CD-ROM drive.

But after some tests, I've found a workaround to make it work (probably the way it initially worked):
[*]Reset to the previous driver version (10.1.330.2015) in Windows.
[*]Set the VM USB controller to 2.0.
[*]Let the VM guest start and then connect the device via right-click menu (do not set a filter!).

Then the VM Linux guest recognizes the device as a USB to Ethernet adapter. If after all those steps I disconnect the device and then reconnect it (via right-click in Virtualbox USB icon), then it will fail again by being recognized as a CD-ROM.

So, although that is a specific workaround, I just wanted it to work so it is OK now.

Thanks.