Comment # 3 on bug 1208941 from
(In reply to Larry Rainey from comment #2)
> file exists on my system - it is no longer in /etc/udev/rules.d
> 
> /usr/lib/udev/rules.d/60-vboxdrv.rules
> 
> 
> # cat /usr/lib/udev/rules.d/60-vboxdrv.rules
> KERNEL=="vboxdrv", NAME="vboxdrv", OWNER="root", GROUP="vboxusers",
> MODE="0660"
> KERNEL=="vboxdrvu", NAME="vboxdrvu", OWNER="root", GROUP="vboxusers",
> MODE="0660"
> KERNEL=="vboxnetctl", NAME="vboxnetctl", OWNER="root", GROUP="vboxusers",
> MODE="0660"
> SUBSYSTEM=="usb_device", ACTION=="add",
> RUN+="/usr/lib/virtualbox/VBoxCreateUSBNode.sh $major $minor
> $attr{bDeviceClass}"
> SUBSYSTEM=="usb", ACTION=="add", ENV{DEVTYPE}=="usb_device",
> RUN+="/usr/lib/virtualbox/VBoxCreateUSBNode.sh $major $minor
> $attr{bDeviceClass}"
> SUBSYSTEM=="usb_device", ACTION=="remove",
> RUN+="/usr/lib/virtualbox/VBoxCreateUSBNode.sh --remove $major $minor"
> SUBSYSTEM=="usb", ACTION=="remove", ENV{DEVTYPE}=="usb_device",
> RUN+="/usr/lib/virtualbox/VBoxCreateUSBNode.sh --remove $major $minor"


Hi Larry,

ah, didn't know this. File exists in that folder also on my system:

# cat /usr/lib/udev/rules.d/60-vboxdrv.rules
KERNEL=="vboxdrv", NAME="vboxdrv", OWNER="root", GROUP="vboxusers", MODE="0660"
KERNEL=="vboxdrvu", NAME="vboxdrvu", OWNER="root", GROUP="vboxusers",
MODE="0660"
KERNEL=="vboxnetctl", NAME="vboxnetctl", OWNER="root", GROUP="vboxusers",
MODE="0660"
#SUBSYSTEM=="usb_device", ACTION=="add",
RUN+="/usr/lib/virtualbox/VBoxCreateUSBNode.sh $major $minor
$attr{bDeviceClass}"
#SUBSYSTEM=="usb", ACTION=="add", ENV{DEVTYPE}=="usb_device",
RUN+="/usr/lib/virtualbox/VBoxCreateUSBNode.sh $major $minor
$attr{bDeviceClass}"
#SUBSYSTEM=="usb_device", ACTION=="remove",
RUN+="/usr/lib/virtualbox/VBoxCreateUSBNode.sh --remove $major $minor"
#SUBSYSTEM=="usb", ACTION=="remove", ENV{DEVTYPE}=="usb_device",
RUN+="/usr/lib/virtualbox/VBoxCreateUSBNode.sh --remove $major $minor"


But, the popup, which asks, if I want to have the USB Passthrough enabled or
disbaled is occuring for every start of VirtualBox. Is this the expected
behavior?


You are receiving this mail because: