Ticket #12229 (closed defect: worksforme)
Oracle Linux 6.4 and VB 4.3 problems
|Reported by:||ceejayemm||Owned by:|
I have just built a new PC running Oracle Linux 6.4 (64 bit) in Desktop mode. I then installed VirtualBox v4.3 using the latest VB .rpm installation kit for OL-6. All installation kits were downloaded today from the download pages on the Oracle and VB websites on the basis that the latest VB release would have been tested on the latest OL release. The installations went fine with no errors during the installations and I have been able run up VB and configure a test VM without any problems. When I try to run the new test VM however then VirtualBox immediately stops with the error:
VirtualBox - Error in suplibOsinit
Kernel driver not installed (rc = -1908)
The VirtualBox Linux kernel driver (vboxdrv) is either not loaded or there is a permissions problem with /dev/vboxdrv. Please reinstall the kernel module by executing
as root. (plus a load of stuff about DKMS packages).
If I try to run the setup file detailed in the error message I get (in /var/log/vbox-install.log):
./routines.sh: line 343: /etc/init.d/vboxautostart-service: No such file or directory ./routines.sh: line 343: /etc/init.d/vboxballoonctrl-service: No such file or directory ./routines.sh: line 343: /etc/init.d/vboxweb-service: No such file or directory VirtualBox 4.3.0 r89960 installer, built 2013-10-15T11:37:43Z.
Testing system setup... Could not find the Linux kernel header files - the directories
/lib/modules/2.6.39-400.209.1.el6uek.x86_64/build/include and /usr/src/linux/include do not exist.
Please install the GNU compiler. Giving up due to the problems mentioned above. Makefile:183: * Error: unable to find the sources of your current Linux kernel. Specify KERN_DIR=<directory> and run Make again. Stop.
How can I fix this installation please ? Will simply installing the GNU compiler and rerunning the setup process resolve this issue ?
I would have attached a VBox.log file however this log file has NOT been created for this test VM!
I have search the User Forums and although there are several similar reports of this error these doesn't appear to be a fix available via this route.