VirtualBox

Ticket #10087 (closed defect: worksforme)

Opened 2 years ago

Last modified 19 months ago

no USB avaiable with non root user

Reported by: fcorades Owned by:
Priority: major Component: other
Version: VirtualBox 4.1.8 Keywords: usb issue ubuntu 10.04 LTS
Cc: Guest type: other
Host type: Linux

Description (last modified by michael) (diff)

Linux 2.6.32-37-generic #81-Ubuntu x86_64 GNU/Linux

Ubuntu 10.04.3 LTS

#################################################################

Regression : no more USB avaiable with non root user

#################################################################

user@amdx4:~$ VBoxManage list usbhost Host USB Devices: <none> user@amdx4:~$

#################################################################

Everythings fine with root: root@amdx4:/home/user# VBoxManage list usbhost Host USB Devices:

UUID: 2ea2d6d8-d2bd-40b6-b3c4-246897911278 VendorId: 0x0424 (0424) ProductId: 0x4063 (4063) Revision: 1.136 (01136) Manufacturer: Generic Product: Ultra Fast Media Reader SerialNumber: 000000264001 Address: sysfs:/sys/devices/pci0000:00/0000:00:12.2/usb1/1-5/1-5.1/1-5.1.1//device:/dev/vboxusb/001/024 Current State: Busy

UUID: 9c7fc249-ebef-4257-9d48-4d85040658fd VendorId: 0x0463 (0463) ProductId: 0xffff (FFFF) Revision: 0.1 (0001) Manufacturer: EATON Product: ELLIPSE SerialNumber: 000000000 Address: sysfs:/sys/devices/pci0000:00/0000:00:12.1/usb4/4-1//device:/dev/vboxusb/004/006 Current State: Busy

UUID: 31bebc1c-f4d8-4657-aaac-9bf056530009 VendorId: 0x046d (046D) ProductId: 0xc517 (C517) Revision: 56.16 (5616) Manufacturer: Logitech Product: USB Receiver Address: sysfs:/sys/devices/pci0000:00/0000:00:12.0/usb3/3-2/3-2.2//device:/dev/vboxusb/003/003 Current State: Busy

UUID: c4a760c8-a13e-4c7d-b6c2-c5838f92df0d VendorId: 0x10d5 (10D5) ProductId: 0x55a4 (55A4) Revision: 1.0 (0100) Manufacturer: No brand Product: 4 Port KVMSwicther SerialNumber: 3´ò Address: sysfs:/sys/devices/pci0000:00/0000:00:12.0/usb3/3-2/3-2.3//device:/dev/vboxusb/003/004 Current State: Busy

UUID: 30f5c2e3-461d-4e73-aa72-1afb3d0f026c VendorId: 0x1307 (1307) ProductId: 0x0330 (0330) Revision: 1.0 (0100) Manufacturer: Generic Product: Mass Storage Device SerialNumber: 00000000000006 Address: sysfs:/sys/devices/pci0000:00/0000:00:12.2/usb1/1-5/1-5.3//device:/dev/vboxusb/001/023 Current State: Busy

root@amdx4:/home/user#

#################################################################

Permissions are ok: user@amdx4:~$ id uid=1000(user) gid=1000(user) groups=4(adm),20(dialout),21(fax),24(cdrom),25(floppy),26(tape),29(audio),30(dip),44(video),46(plugdev),104(fuse),106(lpadmin),112(netdev),121(admin),122(sambashare),125(vboxusers),1000(user)

Try almost everything including changes in : /etc/udev/rules.d/10-vboxdrv.rules /dev ---> drwxr-x--- 5 root vboxusers 100 2011-12-26 11:14 vboxusb fstab hal (...and more, nothing seem to work)

Change History

comment:1 follow-up: ↓ 3 Changed 2 years ago by michael

What does

$ ls -lR /dev/vboxusb

say? If it doesn't work as user then as root.

comment:2 Changed 2 years ago by frank

  • Priority changed from blocker to major

comment:3 in reply to: ↑ 1 Changed 2 years ago by fcorades

/dev/vboxusb:Replying to michael:

What does

$ ls -lR /dev/vboxusb

say? If it doesn't work as user then as root.


as user:

user@amdx4:~$ ls -lR /dev/vboxusb
/dev/vboxusb:
total 0
drwxr-x--- 2 root vboxusers 80 2012-01-29 08:31 001
drwxr-x--- 2 root vboxusers 80 2012-01-29 08:32 002
drwxr-x--- 2 root vboxusers 80 2012-01-29 07:56 003
drwxr-x--- 2 root vboxusers 60 2012-01-29 07:56 004

/dev/vboxusb/001:
total 0
crw-rw---- 1 root vboxusers 189, 9 2012-01-29 08:31 010
crw-rw---- 1 root vboxusers 189, 10 2012-01-29 08:31 011

/dev/vboxusb/002:
total 0
crw-rw---- 1 root vboxusers 189, 129 2012-01-29 07:56 002
crw-rw---- 1 root vboxusers 189, 132 2012-01-29 08:32 005

/dev/vboxusb/003:
total 0
crw-rw---- 1 root vboxusers 189, 258 2012-01-29 07:56 003
crw-rw---- 1 root vboxusers 189, 259 2012-01-29 07:56 004

/dev/vboxusb/004:
total 0
crw-rw---- 1 root vboxusers 189, 385 2012-01-29 07:56 002

comment:4 Changed 2 years ago by michael

  • Description modified (diff)

Then another couple of things you could try:

$ ls -ld /dev/vboxusb
$ ls -l /sys/bus/usb/devices

Or if you want to go for the big machinery the following should give a more detailed look into what is happening: terminate all running VirtualBox processes (VirtualBox, VBoxSVC) and do

$ strace -f -o VBoxSVC.strace VBoxSVC

and run the VBoxManage command again. Attach the file VBoxSVC.strace which is produced.

Last edited 2 years ago by michael (previous) (diff)

comment:5 Changed 19 months ago by frank

  • Status changed from new to closed
  • Resolution set to worksforme

No response, closing.

Note: See TracTickets for help on using tickets.

www.oracle.com
ContactPrivacy policyTerms of Use