I have just installed the kernel through the update manager. The kernel-default package is now 4.1.15-8.1 as are the associated devel packages.
Virtualbox now does not run a virtual machine with details:
The virtual machine 'Win7' has terminated unexpectedly during startup with exit code 1 (0x1).
| Result Code: | NS_ERROR_FAILURE (0x80004005)|
|---|---|
| Component: | MachineWrap|
| Interface: | IMachine {f30138d4-e5ea-4b3a-8858-a059de4c93fd}
|
It also provides a window called “VirtualBox - Error In suplibOsInit” with content:
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. If it is available in your distribution, you should install the DKMS package first. This package keeps track of Linux kernel changes and recompiles the vboxdrv kernel module if necessary.
where: suplibOsInit what: 3 VERR_VM_DRIVER_NOT_INSTALLED (-1908) - The support driver is not installed. On linux, open returned ENOENT.
There is no file ‘/sbin/vboxconfig’
I have run:
sudo /usr/sbin/rcvboxdrv setup
but this does not solve the problem returning:
Recompiling VirtualBox kernel module, NOT. It has been packaged. done
I have tried upgrading the VirtualBox packages using Yast but that did not help.
You probably just need to reload the module. I’ve run into that myself.
Something else that I noticed with the most recent VirtualBox update was
that one of my VMs said it needed a new extensions package. For some
reason, other VMs didn’t have that problem.
You also want to shut down any running VMs before running either a kernel
update or a VirtualBox update - otherwise, you end up not being able to
manage them.
You probably just need to reload the module. I’ve run into that myself.
Something else that I noticed with the most recent VirtualBox update was
that one of my VMs said it needed a new extensions package. For some
reason, other VMs didn’t have that problem.
You also want to shut down any running VMs before running either a kernel
update or a VirtualBox update - otherwise, you end up not being able to
manage them.
I had the same issue. I have left no stone unturned to apply all the combinations mentioned in this post. Alternatively, I gave it a try to have the virtualbox installed from their website instead of the Opensuse-provided one. It has luckily worked out of the box, and without any kernel rebuilding.