http://bugzilla.opensuse.org/show_bug.cgi?id=1037291 Bug ID: 1037291 Summary: VirtualBox fails to start VMs "Kernel driver not installed (rc=-1908)" and then VERR_SUPDRV_COMPONENT_NOT_FOUND Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: kernel-maintainers@forge.provo.novell.com Reporter: ingham@i-pi.com QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- This problem showed up in Tumbleweed within the last month. It was working fine before. After a fresh reboot, if I try to start a VirtualBox VM, I get this message: ----- Kernel driver not installed (rc=-1908) The VirtualBox Linux kernel driver (vboxdrv) is either not loaded or there is a permission problem with /dev/vboxdrv. Please reinstall the kernel module by executing '/sbin/vboxconfig' as root. where: suplibOsInit what: 3 VERR_VM_DRIVER_NOT_INSTALLED (-1908) - The support driver is not installed. On linux, open returned ENOENT. ----- There is no vboxconfig on my system. If I 'modprobe vboxdrv', then the error changes to: ----- Failed to open/create the internal network 'HostInterfaceNetworking-enp0s31f6' (VERR_SUPDRV_COMPONENT_NOT_FOUND). Failed to attach the network LUN (VERR_SUPDRV_COMPONENT_NOT_FOUND). One of the kernel modules was not successfully loaded. Make sure that no kernel modules from an older version of VirtualBox exist. Then try to recompile and reload the kernel modules by executing '/sbin/vboxconfig' as root (VERR_SUPDRV_COMPONENT_NOT_FOUND). Result Code: NS_ERROR_FAILURE (0x80004005) Component: ConsoleWrap Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed} ----- Other possibly useful information: $ uname -a Linux HQ-slmbp.us.ara.com 4.10.12-1-default #1 SMP PREEMPT Fri Apr 21 11:50:25 UTC 2017 (3043bd9) x86_64 x86_64 x86_64 GNU/Linux # locate vboxconfig # echo $? 1 # cat /etc/os-release NAME="openSUSE Tumbleweed" # VERSION="20170429" ID=opensuse ID_LIKE="suse" VERSION_ID="20170429" PRETTY_NAME="openSUSE Tumbleweed" ANSI_COLOR="0;32" CPE_NAME="cpe:/opensuse:tumbleweed:20170429" BUG_REPORT_URL="https://bugs.opensuse.org" HOME_URL="https://www.opensuse.org/" # lsmod | grep vb vboxdrv 458752 0 # rpm -qa 'kernel*' '[Vv]irtual[Bb]ox*' kernel-default-4.10.10-1.2.x86_64 kernel-macros-4.10.12-1.2.noarch kernel-firmware-20170404-1.1.noarch kernel-source-4.10.12-1.2.noarch kernel-source-4.10.10-1.2.noarch kernel-default-devel-4.10.12-1.2.x86_64 virtualbox-qt-5.1.18-2.3.x86_64 kernel-default-devel-4.10.10-1.2.x86_64 virtualbox-host-kmp-default-5.1.18_k4.10.12_1-2.3.x86_64 kernel-default-4.10.12-1.2.x86_64 kernel-devel-4.10.12-1.2.noarch kernel-devel-4.10.12-1.1.noarch kernel-source-4.10.12-1.1.noarch kernel-syms-4.10.12-1.1.x86_64 kernel-syms-4.10.12-1.2.x86_64 virtualbox-5.1.18-2.3.x86_64 kernel-devel-4.10.10-1.2.noarch # systemctl status vboxdrv Unit vboxdrv.service could not be found.

From journalctl: May 02 14:58:36 host.example.com kernel: vboxdrv: ffffffffc1344020 VMMR0.r0 May 02 14:58:36 host.example.com kernel: vboxdrv: ffffffffc0246020 VBoxDDR0.r0

Finally, if I change from bridged to NAT network, the system will start up. However, I sometimes need the bridged network. -- You are receiving this mail because: You are on the CC list for the bug.