4

Virtualbox on OpenSUSE 13.1: vboxdrv troubles and troubleshooting

 4 years ago
source link: https://msiyer.com/virtualbox-on-opensuse-13-1-vboxdrv-troubles-and-troubleshooting/
Go to the source link to view the article. You can view the picture content, updated content and better typesetting reading experience. If the link is broken, please click the button below to view the snapshot at that time.
neoserver,ios ssh client
Virtualization

Virtualbox on OpenSUSE 13.1: vboxdrv troubles and troubleshooting

msiyer

15 Apr 2014 • 1 min read

I installed Virtualbox on my openSUSE 13.1 system using the following command

sudo zypper in virtualbox

I created a Windows 7 VM. Everything worked. I updated the system later and found Virtualbox reluctant to start. It simply said

Kernel driver not installed (rc=-1908)”

WARNING: The vboxdrv kernel module is not loaded. Either there is no module available for the current kernel (3.5.0-18-generic) or it failed to load. Please recompile the kernel module and install it by sudo /etc/init.d/vboxdrv setup You will not be able to start VMs until this problem is fixed.

The kernel was definitely updated and the Dynamic Kernel Module Support (DKMS) did not work. If it had I would not have seen the above errors. I tried running

sudo /etc/init.d/vboxdrv setup

This failed. I understood from the logs that there was no make module installed on my system. I read further and understood that I was missing quite a lot of packages essential for compiling the driver. I did the following:

sudo  zypper install make gcc  gcc-c++ kernel-source kernel-syms

The log had mentioned about the KERN_DIR parameter(kernel directory) being indeterminate. This meant I needed the kernel-source package. kernel-syms(kernel symbols version) package is needed for the following reason:

Kernel symbols such as functions and variables have version informationattached. This package contains the symbol versions for the standard kernels.Installing this package before compiling kernel modules outside of thekernel source tree adds symbol version information in these modules.Modules without symbol version information can only be loaded onexactly the kernel version for which they were compiled. Modules withsymbol version information can also be loaded into more recent kernelsas long as none of the symbols exported by the kernel changes. (Thisprovides a reasonable level of confidence but does not guarantee that**the module will still work.)

Once this was done, I executed

sudo /etc/init.d/vboxdrv setup

Virualbox has no starting troubles now.


report

Recommend

About Joyk


Aggregate valuable and interesting links.
Joyk means Joy of geeK