FS#38314 - [virtualbox] Failed to open /dev/vboxdrvu

Attached to Project: Community Packages
Opened by Atanas Zhelev (zmeYski) - Monday, 30 December 2013, 00:01 GMT
Last edited by Sébastien Luttringer (seblu) - Saturday, 04 January 2014, 04:42 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Sébastien Luttringer (seblu)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
The error message "Failed to open "/dev/vboxdrvu", errno=13, rc=VERR_VM_DRIVER_NOT_ACCESSIBLE" is printed in VBoxSVC.log file.
It looks like vboxdrv.ko kernel module, when loaded, now creates another node in dev namely /dev/vboxdrvu, permissions are 0600. According to a svn log entry the permissions should be 0666.

Linux installers: Move the udev rule execution order from 10 to 60. The reason for having it at 10 was to allow other rules to overwrite these rules, mainly permissions of the USB devices. This is not longer necessary (we are using /dev/vboxusb for a long time now) and we need to take care that certain systems like EL6 don't reset the permissions of /dev/vboxdrvu -- the unrestricted device -- back to 0600 (we want 0666 here).

Link:
https://www.virtualbox.org/browser/vbox/trunk/src/VBox/Installer/linux/installer-common.sh
http://code.metager.de/source/history/virtualbox/src/VBox/Installer/linux/rpm/VirtualBox.tmpl.spec

Arch's 10-vboxdrv.rules file needs some adjustments.

Additional info:
* package version(s) - virtualbox 4.3.6-1, virtualbox-host-modules 4.3.6-2


Steps to reproduce:
Run a VM, check the log file.
This task depends upon

Closed by  Sébastien Luttringer (seblu)
Saturday, 04 January 2014, 04:42 GMT
Reason for closing:  Fixed
Additional comments about closing:  virtualbox-4.3.6-2

Loading...