[SOLVED] VirtualBox < 3.1.4 module build fails on 2.6.33 kernel

rpedrica · 03-04-2010, 07:49 AM

I had an issue with the module build for vbox 3.1.2 breaking on the latest kernel ( /etc/rc.d/rc.vboxdrv setup ). Apparently the issue is that a kernel header (autoconf.h ) has changed its location in the module tree and hence the issue.

2 options:

1. upgrade to 3.1.4
2. create a symlink as follows

cd /usr/src/linux/include/linux
ln -s ../generated/autoconf.h autoconf.h

Robby

carltm · 03-04-2010, 04:41 PM

Thanks for posting this, Robby.

If you look, there is a way to mark this post as being "solved." Please do
that so searchers will know that you've found the solution.

smoooth103 · 03-04-2010, 08:51 PM

Thanks Robby! Was looking for that exact solution -- worked great.

cwizardone · 03-04-2010, 11:01 PM

I just reinstall stable Slackware64-13 with the 2.6.29.6 kernel and I'm having the same problem with VirtualBox 3.1.4.

rpedrica · 03-05-2010, 12:40 AM

Carltm - I thought I'd done this - my bad!

Quote:

Originally Posted by carltm

Thanks for posting this, Robby.

If you look, there is a way to mark this post as being "solved." Please do
that so searchers will know that you've found the solution.

cwizardone: W.r.t. 2.6.29.x earlier versions of vbox should work fine - I was running 3.1.2 for some time on that kernel. What is the exact error/problem

cwizardone · 03-05-2010, 10:34 AM

Quote:

Originally Posted by rpedrica

...cwizardone: W.r.t. 2.6.29.x earlier versions of vbox should work fine - I was running 3.1.2 for some time on that kernel. What is the exact error/problem

The VirtualBox documentation says,"...The version numbers of the header ﬁle packages must be the same as that of the kernel you are using."

So I took a look and while the version number is the same, the header name does not include "_64", while the kernel name has the full "x86_64".
I don't know if that is the problem, but I'm going to rename the file and find out.

cwizardone · 03-05-2010, 06:04 PM

Well, I decided to install the latest kernel, headings, source, and modules and that went well and everything, but VB works.
So I then tried the rpedrica's fix, but that still didn't help.
Here is the VB install log:

Code:

VirtualBox 3.1.4 r57640 installer, built 2010-02-12T19:37:27Z.

Testing system setup...
System setup appears correct.

Installing VirtualBox to /opt/VirtualBox

Output from the module build process (the Linux kernel build system) follows:

make KBUILD_VERBOSE=1 -C /lib/modules/2.6.33/build SUBDIRS=/tmp/vbox.0 SRCROOT=/tmp/vbox.0 modules
/usr/src/linux-2.6.33/arch/x86/Makefile:81: stack protector enabled but no compiler support
test -e include/generated/autoconf.h -a -e include/config/auto.conf || (		\
	echo;								\
	echo "  ERROR: Kernel configuration is invalid.";		\
	echo "         include/generated/autoconf.h or include/config/auto.conf are missing.";\
	echo "         Run 'make oldconfig && make prepare' on kernel src to fix it.";	\
	echo;								\
	/bin/false)
mkdir -p /tmp/vbox.0/.tmp_versions ; rm -f /tmp/vbox.0/.tmp_versions/*
make -f scripts/Makefile.build obj=/tmp/vbox.0
  gcc -Wp,-MD,/tmp/vbox.0/linux/.SUPDrv-linux.o.d  -nostdinc -isystem /usr/lib64/gcc/x86_64-slackware-linux/4.4.3/include -I/usr/src/linux-2.6.33/arch/x86/include -Iinclude  -include include/generated/autoconf.h -D__KERNEL__ -Wall -Wundef -Wstrict-prototypes -Wno-trigraphs -fno-strict-aliasing -fno-common -Werror-implicit-function-declaration -Wno-format-security -fno-delete-null-pointer-checks -O2 -m64 -mno-red-zone -mcmodel=kernel -maccumulate-outgoing-args -DCONFIG_AS_CFI=1 -DCONFIG_AS_CFI_SIGNAL_FRAME=1 -pipe -Wno-sign-compare -fno-asynchronous-unwind-tables -fno-omit-frame-pointer -fno-optimize-sibling-calls -pg -I/lib/modules/2.6.33/build/include -I/tmp/vbox.0/ -I/tmp/vbox.0/include -I/tmp/vbox.0/r0drv/linux -D__KERNEL__ -DMODULE -DRT_OS_LINUX -DIN_RING0 -DIN_RT_R0 -DIN_SUP_R0 -DVBOX -DRT_WITH_VBOX -DVBOX_WITH_HARDENING -DCONFIG_VBOXDRV_AS_MISC -DRT_ARCH_AMD64 -DVBOX_WITH_64_BITS_GUESTS  -DMODULE -D"KBUILD_STR(s)=#s" -D"KBUILD_BASENAME=KBUILD_STR(SUPDrv_linux)"  -D"KBUILD_MODNAME=KBUILD_STR(vboxdrv)"  -c -o /tmp/vbox.0/linux/SUPDrv-linux.o /tmp/vbox.0/linux/SUPDrv-linux.c
/usr/libexec/gcc/x86_64-slackware-linux/4.4.3/cc1: error while loading shared libraries: libgmp.so.10: cannot open shared object file: No such file or directory
make[2]: *** [/tmp/vbox.0/linux/SUPDrv-linux.o] Error 1
make[1]: *** [_module_/tmp/vbox.0] Error 2
make: *** [vboxdrv] Error 2

End of the output from the Linux kernel build system.
Installation successful

Any help greatly appreciated.
Thanks.

brianL · 03-05-2010, 06:09 PM

I've just updated VirtualBox (PUEL version) to 3.1.4 on Slack64 using the 2.6.29.6 generic kernel with no problems.

rpedrica · 03-06-2010, 01:19 AM

cwizardone: you seem to have hit an issue with libgmp that some others have had in the latest updates:

Quote:

error while loading shared libraries: libgmp.so.10: cannot open shared object file: No such file or directory

Check that this package is installed but perhaps best is to reinstall it - note there have been some issues surrounding this package so make sure you get the absolute latest updates for current ( gmp was released Mar 1 and aaa_elflibs was released Mar 2 for eg. ) . My version is:

gmp-5.0.1-x86_64-1

I did notice that my package did not have an explicit link to libgmp.so.10 but a scan ( ls -al libgmp* ) of /usr/lib64 shows it is fine:

/usr/lib64/libgmp.so.10 -> libgmp.so.10.0.1

Do check this. Strange I also found libgmp.so.10.0.1 in the aaa_elflibs package ... perhaps one of the packagers can comment?

cwizardone · 03-06-2010, 10:06 AM

rpedrica,
Thanks for all your help.
At this point I'm done fiddle *&#$ing around with 'current.'
I reinstalled Slackware64-13 'stable' and that's it. No more messing around.
After the re-install, yet again, this time I installed VirtualBox *before*
installing the multilib files and the installation was successful. Then
I installed the multilib files and now everything works.

So it is stable and Xfce from now on. The kids over at KDE have burned that bridge. I'll use XP before I'll put KDE 4.xx on my machine again.
I did update a few applications from the current directory and they are working well, as they have in the past. For example, the most recent Thunderbird, GIMP, Firefox, etc. BTW, I've found the package of Opera 10.10, from the Salix repository to be the best version of Opera I've used to date.
Thanks, again, for your help.

rpedrica · 03-07-2010, 01:00 AM

cwizardone: sounds like you're happy and that's the most important. Pity though as -current is where the fun is ... ; ) I still have some odds and ends with KDE now and again but overall it's more than usable as a daily platform. Especially in 4.4.x form.

cwizardone · 03-07-2010, 01:18 AM

Quote:

Originally Posted by rpedrica

...I still have some odds and ends with KDE now and again but overall it's more than usable as a daily platform. Especially in 4.4.x form.

Only if you disable the evil triplets.

gtludwig · 03-29-2010, 07:23 AM

I'm having problems with this on -current

Code:

root@cpc-5564:~# uname -orimv
2.6.33 #2 SMP Sun Mar 7 11:35:55 CST 2010 x86_64 AuthenticAMD GNU/Linux

Code:

root@cpc-5564:~# /etc/rc.d/rc.vboxdrv setup
Stopping VirtualBox kernel module ...done.
Removing old VirtualBox netadp kernel module ...done.
Removing old VirtualBox netflt kernel module ...done.
Removing old VirtualBox kernel module ...done.
Recompiling VirtualBox kernel module ...done.
Starting VirtualBox kernel module ...failed!
  (modprobe vboxdrv failed. Please use 'dmesg' to find out why)

Code:

gtl@cpc-5564:/usr/src/linux/include/linux$ ls -la autoconf.h
lrwxrwxrwx 1 root root 23 2010-03-29 08:54 autoconf.h -> ../generated/autoconf.h

Error is the same pointed out by cwizardone...

VirtualBox is 3.1.4 r57640.

Thanks in advance,
gtludwig