Virtual Box VERR_VM_DRIVER_NOT_ACCESSIBLE error.

I saw this in the logs of both VB 4.3.30 and 5+:

Failed to open “/dev/vboxdrvu”, errno=13, rc=VERR_VM_DRIVER_NOT_ACCESSIBLE

Which based on this post (Ref) is caused by having the wrong permissions, resulting in:

ls -l /dev
 
crw------- 1 root root 10, 57 Oct 2 05:58 vboxdrv
crw------- 1 root root 10, 56 Oct 2 05:58 vboxdrvu
crw------- 1 root root 10, 55 Oct 2 05:58 vboxnetctl
drwxr-x--- 4 root vboxusers 80 Oct 2 05:58 vboxusb

The fix is to create /lib/udev/rules.d/20-virtualbox2.rules and add:

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"

Then restart the system and the permissions are now:

ls -l /dev
 
crw-rw---- 1 root vboxusers 10, 57 Oct 5 06:00 vboxdrv
crw-rw---- 1 root vboxusers 10, 56 Oct 5 06:00 vboxdrvu
crw-rw---- 1 root vboxusers 10, 55 Oct 5 06:00 vboxnetctl
drwxr-x--- 4 root vboxusers 80 Oct 5 06:00 vboxusb

I am not sure how correct this is by including vboxdrv, but it does prevent the errors in VB logs.

One thought on “Virtual Box VERR_VM_DRIVER_NOT_ACCESSIBLE error.

  1. Drey Tee

    Looks like you saved my day!
    I had a problem with randomly bad shutdown of VMs and a record in VM logs about device
    I gave 666 permissions and changed group to vbox but still had this error. After changing group to vboxusers error disappeared and shutdown/restart of every VM now doesn’t hang.
    I was really close)
    Thanks!

    Reply

Leave a Reply

Your email address will not be published. Required fields are marked *