Opened 15 years ago
Closed 14 years ago
#7093 closed defect (fixed)
Windows (all?) guests cannot access USB devices due to lacking group-write permission on device
Reported by: | pablo | Owned by: | |
---|---|---|---|
Component: | USB | Version: | VirtualBox 3.2.6 |
Keywords: | Cc: | ||
Guest type: | Windows | Host type: | Linux |
Description
Howdy,
I noticed my Guest (Windows 7) was no longer able to access the USB devices on my Host. I'm not sure when this regression occurred because it's not a frequent activity.
I checked the permissions in /dev/bus/usb' for
group vboxusers' and found all the devices didn't have write' permission. Once I manually
chmod g+w' the devices, the Guest gained access.
I confirmed that 10-vboxdrv.rules' is in
/etc/udev/rules.d' ...
Please let me know if other information is required.
I'm heading out on vacation this Friday for a week ... just a heads up. :)
Thx a lot!
Change History (3)
comment:1 by , 15 years ago
comment:2 by , 15 years ago
Hi Michael,
Renaming 10* to 50* did the trick - see below.
And you're correct, my host O/S is `openSUSE' .... I should have mentioned it. Sorry.
Thank you for the quick turn-around. I'll manually change my VM's.
ROOT-root@zoom-1002-[usb]: find . -group vboxusers | xargs ls -la crw-rw-r-- 1 root vboxusers 189, 0 2010-07-01 06:01 ./001/001 crw-rw-r-- 1 root vboxusers 189, 128 2010-07-01 06:01 ./002/001 crw-rw-r-- 1 root vboxusers 189, 130 2010-07-01 06:01 ./002/003 crw-rw-r-- 1 root vboxusers 189, 256 2010-07-01 06:02 ./003/001 crw-rw-r-- 1 root vboxusers 189, 257 2010-07-01 06:02 ./003/002 crw-rw-r-- 1 root vboxusers 189, 384 2010-07-01 06:02 ./004/001 crw-rw-r-- 1 root vboxusers 189, 512 2010-07-01 06:02 ./005/001 crw-rw-r-- 1 root vboxusers 189, 513 2010-07-01 06:02 ./005/002 crw-rw-r-- 1 root vboxusers 189, 640 2010-07-01 06:02 ./006/001 crw-rw-r-- 1 root vboxusers 189, 768 2010-07-01 06:02 ./007/001 crw-rw-r-- 1 root vboxusers 189, 769 2010-07-01 06:02 ./007/002 crw-rw-r--+ 1 root vboxusers 189, 770 2010-07-01 06:02 ./007/003 crw-rw-r-- 1 root vboxusers 189, 771 2010-07-01 06:02 ./007/004
comment:3 by , 14 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
Should properly work with VBox 4.0.10.
Can you try renaming 10-vboxdrv.rules to start with a 50? This is needed on some (especially SUSE) systems.