suse host virtualbox does not reach USB devices

Hi!

I am using Suse 13.2 host and Virtualbox 4.3.18.

All virtmachine are working and the guest additions are installed and the extension pack is installed for virtualbox.
It seems that the suse does not give the list of USB devices to the virtual machine.
When i want to add an USB device the asnwer is - ther is no reachable device - hovewer a lot of USB devise is in the system.

I used this version of Virtualbox with suse 13.1, it has worked good.

Please find the bug and fix it.

Thanks, muro

Which VirtualBox?
The one from virtualbox.org, or the one included in openSUSE?

Please find the bug and fix it.

There probably is no bug.
In openSUSE’s packages USB pass-through is disabled by default because of the security risks it imposes.

To enable it, copy /usr/lib/udev/rules.d/60-vboxdrv.rules to /etc/udev/rules.d/, open it in a text editor and remove the comment characters (‘#’) at the beginning of the last 4 lines.

You also need to describe exactly what is the USB device you’re trying to connect to. In most cases, the Guest doesn’t access the hardware device directly… The HostOS should recognize the device, and then a virtual device can be created that accesses the hardware.

So, examples of this include

  • Hard drives. The HostOS needs to mount and see the partitioned and formatted disk, then you can create a virtual disk on that drive
  • NICs. The HostOS needs to detect, configure and be able to use the NIC, then a Linux Bridge Device can be created that points to the interface pointing to the NIC. Then, you can configure that LBD in the Guest properties and create a wired network interface in your Guest (regardless what type of network is on the Host).

The only USB device mentioned in this Forum I can remember where a User needed direct USB access was a fingerprint reader for logging into the system.

TSU

I also have this problem, and the solution suggested here does not work for me. I use USB programmers like SiLab, ST Link2 etc, and none of these register is VBox, but is available in opensuse 13.2, not even the mouse, keyboards etc.

lsusb gives …
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 006 Device 002: ID 0483:3748 STMicroelectronics ST-LINK/V2
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 003: ID 0d8c:0001 C-Media Electronics, Inc. Audio Device
Bus 004 Device 002: ID 09da:0006 A4 Tech Co., Ltd Optical Mouse WOP-35 / Trust 450L Optical Mouse
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

ST-LINK/V2 is available, but the VBox devices says I don’t have any USB attached ?

/etc/udev/ content is
KERNEL==“vboxdrv”, NAME=“vboxdrv”, OWNER=“root”, GROUP=“root”, MODE=“0600”
KERNEL==“vboxdrvu”, NAME=“vboxdrvu”, OWNER=“root”, GROUP=“root”, MODE=“0666”
KERNEL==“vboxnetctl”, NAME=“vboxnetctl”, OWNER=“root”, GROUP=“root”, MODE=“0600”
SUBSYSTEM==“usb_device”, ACTION==“add”, RUN+=“/usr/share/virtualbox/VBoxCreateUSBNode.sh $major $minor $attr{bDeviceClass}”
SUBSYSTEM==“usb”, ACTION==“add”, ENV{DEVTYPE}==“usb_device”, RUN+=“/usr/share/virtualbox/VBoxCreateUSBNode.sh $major $minor $attr{bDeviceClass}”
SUBSYSTEM==“usb_device”, ACTION==“remove”, RUN+=“/usr/share/virtualbox/VBoxCreateUSBNode.sh --remove $major $minor”
SUBSYSTEM==“usb”, ACTION==“remove”, ENV{DEVTYPE}==“usb_device”, RUN+=“/usr/share/virtualbox/VBoxCreateUSBNode.sh --remove $major $minor”

I noted that my opensuse13.1 does not have the “vboxdrvu” ,and it is also 10-vboxdrv.rules

The USB is enabled in settings/USB enable USB Controller,as well as the USB 2.0 (EHCI) controller.

I installed the VBox extention, and is running VBox 4.3.20 r96996.
I also did the
/etc/init.d/vboxdrv setup
but no USB device

Abny suggestions, this vbox image worked like a charm in 13.1 , and was exported/imported in opensuse 13.2

Hi,

You can find out your usb devices via VBoxManage.

VBoxManage list usbhost

Also make sure the user is a member of the

vboxusers

group

Is there any other Virtualbox package installed?

zypper se -si virtual vbox

Hi,

or

zypper se -si "*virtualbox*"

or

rpm -qa "*[Vv]irtual[Bb]ox*"

Add user to group:

sudo usermod -a -G vboxusers $USER

Uncomment lines in /etc/udev/rules.d/60-vboxdrv.rules, just in case:

printf '%s
’ ‘g/^#SUBSYSTEM/s/^#//’ w | ed -s /etc/udev/rules.d/60-vboxdrv.rules

Copy rules:

sudo cp -v /etc/udev/rules.d/60-vboxdrv.rules /usr/lib/udev/

Reload rules or restart:

sudo udevadm control --reload-rules

Reload driver:

sudo systemctl restart vboxdrv.service

In my case the problem occurred because the file did not exist /usr/lib/udev/60-vboxdrv.rules

Hi,

Most of that part is written in the wiki

:wink:

1 Like

Sorry, here it is.https://en.opensuse.org/VirtualBox

Hi,

The forums moderators comment was most helpful. In my case the virtualbox client from Oracle wasn’t connecting to the USB devices.
The /etc/udev/rules.d/60-vboxdrv.rules where correct but the 60-vboxdrv.rules where missing in /usr/lib/udev/rules.d/. Just coping the file at the last mensioned folder solved the problem. Of course it has to be done as Super User.:slight_smile:

As the saying goes: “There are many roads leading to Roma” or the more cruel english “There are many ways to skin a cat”:wink:

Cheers

This BUG wasted HOURS of my time in troubleshooting.

What arrogence to cripple the expected behaviour of an application without warning the user of the hack or providing a quick one-button fix to set it right.

Connecting to USB devices that have Windows-only software IS EXACTLY WHY MOST PEOPLE USE VIRTUAL BOX.

Hi
You posted in an exactly one year old thread, a lot of water has passed under the bridge since then… If that’s still present in the current release of VirtualBox, then suggest you raise a bug, else use an alternative, eg KVM (no drivers needed to compile, just works!).

Note it is well known and documented that VBox dos not support USB out of the box for years. It was a way to get Corporate users to pay since the fix is proprietary and only licensed free for personal use.

1 Like