Monday, February 15, 2016

Bigtop vagrant error message VirtualBox is complaining that the kernel module is not loaded.

[root@node4 vagrant-puppet-vm]# vagrant up
vagrant conf local repo enabled:  false
Adding output/ repo ? false
VirtualBox is complaining that the kernel module is not loaded. Please
run `VBoxManage --version` or open the VirtualBox GUI to see the error
message which should contain instructions on how to fix this error
sudo /etc/init.d/vboxdrv setup
[root@node4 vagrant-puppet-vm]# sudo /etc/init.d/vboxdrv setup
Stopping VirtualBox kernel modules                         [  OK  ]
Recompiling VirtualBox kernel modules                      [FAILED]
  (Look at /var/log/vbox-install.log to find out what went wrong)
[root@node4 vagrant-puppet-vm]# cat  /var/log/vbox-install.log
Makefile:185: *** Error: unable to find the sources of your current Linux kernel. Specify KERN_DIR= and run Make again.  Stop.
Makefile:185: *** Error: unable to find the sources of your current Linux kernel. Specify KERN_DIR= and run Make again.  Stop.
Makefile:185: *** Error: unable to find the sources of your current Linux kernel. Specify KERN_DIR= and run Make again.  Stop.
[root@node4 vagrant-puppet-vm]#
Install the required packages: 
[root@node4 2.6.32-573.18.1.el6.x86_64]# yum -y install cloog-ppl cpp gcc glibc-devel glibc-headers kernel-devel kernel-headers mpfr ppl glibc glibc-common libgcc libgomp
Set the KERN_DIR environment variable. 
[root@node4 2.6.32-573.18.1.el6.x86_64]# export KERN_DIR=/usr/src/kernels/2.6.32-573.18.1.el6.x86_64
Verify works: 
[root@node4 2.6.32-573.18.1.el6.x86_64]# /etc/init.d/vboxdrv setup
Stopping VirtualBox kernel modules                         [  OK  ]
Recompiling VirtualBox kernel modules                      [  OK  ]
Starting VirtualBox kernel modules                         [  OK  ]

No comments:

Post a Comment