ROSA Linux Bugzilla – Bug 5216
Last modified: 2016-02-20 17:10:30 MSK
I install Virtualbox, create a disk, switch to the rt kernel, reboot and the virtualbox dont work:
"The virtual machine 'GNOME 3' has terminated unexpectedly during startup with exit code 1 (0x1).
"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
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."
When i reinstall virtualbox dont solve this the issue, /etc/init.d/vboxdrv setup is not installed.
Steps to Reproduce:
1. Install virtualbox with dkms
2. Switch to kernel-nrj-realtime-latest and restart
3. Create a disk (ROSA 64, in my case)
4. Launch virtualbox and then the virtual OS.
(I preconfigure the settings, like 3D acceleration and the live iso for the virtual IDE drive, before i install the rt kernel)
nrj-realtime kernel is actually a strange beast, far from realtime at all. It is not recommended to use it.
For these reasons, this kernel flavour was moved to Contrib some months ago and support for it is low priority.
Officially supported flavours, which are now in Main repo:
* nrj-desktop-pae (i586)
* nrj-laptop-pae (i586)
If the problem persists with these kernels, please let us know here.
And by the way, please check that the appropriate kernel-nrj-realtime-devel package is installed.
If it is, then DKMS build log for VBox drivers is also needed to see what is going on.
Is this issue is still valid with modern kernels?
Note that in the original report you looked for /etc/init.d/vboxdrv; this is wrong, we use /etc/init.d/virtualbox service. It is a part of virtualbox package.
So if you still experience any issues, please launch
# /etc/init.d/virtualbox start
The root of the problem is that either dkms failed to build driver for nrj-runtime kernel or you have another virtualization system (e.g., qemu/kvm) loaded that prevented vboxdrv from load.
Marking as "worksforme" for now since we don't have a reproducer.