Click here to Skip to main content
11,478,174 members (68,311 online)
Click here to Skip to main content

Tagged as

Virtualbox on OpenSUSE 13.1: vboxdrv troubles and troubleshooting

, 25 Jul 2014 CPOL 4.5K
Rate this:
Please Sign up or sign in to vote.
I installed Virtualbox on my openSUSE 13.1 system using the sudo zypper in virtualbox command. This installed Virtualbox and I created a Windows 7 VM in it. All seemed fine. I updated the system later and found Virtualbox reluctant to start. It simply said Kernel driver not installed (rc=-1908)&#822

I installed Virtualbox on my openSUSE 13.1 system using the

sudo zypper in virtualbox

command. This installed Virtualbox and I created a Windows 7 VM in it.

All seemed fine. I updated the system later and found Virtualbox reluctant to start. It simply said

Kernel driver not installed (rc=-1908)”

AND

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 information attached. This package contains the symbol versions for the standard kernels. Installing this package before compiling kernel modules outside of the kernel source tree adds symbol version information in these modules. Modules without symbol version information can only be loaded on exactly the kernel version for which they were compiled. Modules with symbol version information can also be loaded into more recent kernels as long as none of the symbols exported by the kernel changes. (This provides a reasonable level of confidence but does not guarantee that the module will still work.)

Once this was done, I ran the

sudo /etc/init.d/vboxdrv setup

again and everything worked.

License

This article, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Share

About the Author

msiyer
Software Developer HCL Technologies
India India
My name is M Sreekant. We South Indians have long names. My name, when completely expanded, is Mohan Sreekant Iyer. I like to be called "msiyer" due to economical considerations. You know what I mean Wink | ;)

I am a robot, a DNA replicator, made of chemical compounds. I try very hard to override nature's programming. A robot that knows, is a robot that seeks to know more.

I believe, any system or structure can be dissected by he who is curious enough. One day mankind will find loopholes in the laws of Physics that govern the cosmos, probably with my help. That will be the greatest day in my life or afterlife.
Follow on   Google+   LinkedIn

Comments and Discussions

 
-- There are no messages in this forum --
| Advertise | Privacy | Terms of Use | Mobile
Web03 | 2.8.150520.1 | Last Updated 25 Jul 2014
Article Copyright 2014 by msiyer
Everything else Copyright © CodeProject, 1999-2015
Layout: fixed | fluid