VBox fail to run after kern update 2.6.33 to 2.6.33 [Solved]

Discussion for all VM - Installing, Software, Problems

Moderator: Moderators

VBox fail to run after kern update 2.6.33 to 2.6.33 [Solved]

Postby robjeffrey » Mon May 24, 2010 14:02

After yesterday's kernel update from 2.6.33 to 2.6.33 64bit, the vbox install fails with the message to run /etc/init.d/vboxdrv setup

Running that generates the following error log:

Code: Select all
make KBUILD_VERBOSE=1 -C /lib/modules/2.6.33-sabayon/build SUBDIRS=/tmp/vbox.0 SRCROOT=/tmp/vbox.0 modules
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/lib/gcc/x86_64-pc-linux-gnu/4.4.2/include -I/usr/src/linux-2.6.33-sabayon/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 -Os -m64 -mtune=generic -mno-red-zone -mcmodel=kernel -funit-at-a-time -maccumulate-outgoing-args -DCONFIG_AS_CFI=1 -DCONFIG_AS_CFI_SIGNAL_FRAME=1 -pipe -Wno-sign-compare -fno-asynchronous-unwind-tables -mno-sse -mno-mmx -mno-sse2 -mno-3dnow -Wframe-larger-than=2048 -fno-stack-protector -fno-omit-frame-pointer -fno-optimize-sibling-calls -Wdeclaration-after-statement -Wno-pointer-sign -fno-strict-overflow -fno-dwarf2-cfi-asm -fconserve-stack -I/lib/modules/2.6.33-sabayon/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/.tmp_SUPDrv-linux.o /tmp/vbox.0/linux/SUPDrv-linux.c
In file included from /tmp/vbox.0/include/VBox/types.h:34,
                 from /tmp/vbox.0/linux/../SUPDrvInternal.h:39,
                 from /tmp/vbox.0/linux/SUPDrv-linux.c:37:
/tmp/vbox.0/include/iprt/types.h:100:30: error: linux/autoconf.h: 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


I have made sure I have the newest kernel sources, re-run the make oldconfig && make prepare, even though the header files were already present.

I have also re-installed vbox kernel drivers and the binary for 3.2.0 - same issue.
Last time this happened, there was a binary update for the vbox kernel drivers as well, so I am not sure if there will be one this time as well (and just have to wait), or if I have to build from the sources (which isn't going so well with the above error).

I am continuing on and will post results as/if I find them.
robjeffrey
Young Hen
 
Posts: 21
Joined: Wed Feb 11, 2009 20:48

Re: VBox fail to run after kern update 2.6.33 to 2.6.33 - So

Postby robjeffrey » Mon May 24, 2010 21:08

The only solution that has worked was to download the full install directly from virtualbox.org.
After a reinstall and reboot, all is back to normal.
Still have no idea why make wasn't able to locate the needed headers, though.
robjeffrey
Young Hen
 
Posts: 21
Joined: Wed Feb 11, 2009 20:48

Re: VBox fail to run after kern update 2.6.33 to 2.6.33 [Sol

Postby wolfden » Mon May 24, 2010 23:41

no issues here, just tested it out on my amd64 entropy system

Where are you getting that error message? Sounds like you are mixing entropy and portage packages?
User avatar
wolfden
Sharecropper
 
Posts: 8824
Joined: Sat Jan 14, 2006 0:55
Location: Midwest USA

Re: VBox fail to run after kern update 2.6.33 to 2.6.33 [Sol

Postby robjeffrey » Tue May 25, 2010 17:32

The error above was from /var/log/vbox-install.log

It is possible I've mixed portage/entropy somewhere down the line, the system has been up for years following updates, etc. But a complete kernel, sources, and vbox re-install from entropy should have fixed that, no?

Let me know if I can supply you with more info (logs, system details, etc). Will be glad to help.
robjeffrey
Young Hen
 
Posts: 21
Joined: Wed Feb 11, 2009 20:48


Return to Virtual Managers

Who is online

Users browsing this forum: No registered users and 1 guest

cron