virtualbox-dkms 4.2.10-dfsg-0ubuntu2: virtualbox kernel module failed to build

[Jim Cromie]

happens once at startup.
Im not using it, and dont recall trying to set it up either,
so it could be a broken default config, but thats worth reporting too.

it looks a lot like the same bug #...1816, but that was on v11.x, Im on v13.04

ProblemType: Package
DistroRelease: Ubuntu 13.04
Package: virtualbox-dkms 4.2.10-dfsg-0ubuntu2
Uname: Linux 3.9.0-chumly-dd2-12070-g8cbc95e i686
ApportVersion: 2.9.2-0ubuntu8
Architecture: i386
DKMSKernelVersion: 3.9.0-chumly-dd2-12555-g2dbd3ca
Date: Fri May 10 12:45:31 2013
InstallationDate: Installed on 2011-02-23 (807 days ago)
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
MarkForUpload: True
PackageArchitecture: all
PackageVersion: 4.2.10-dfsg-0ubuntu2
SourcePackage: virtualbox
Title: virtualbox-dkms 4.2.10-dfsg-0ubuntu2: virtualbox kernel module failed to build
UpgradeStatus: Upgraded to raring on 2013-04-30 (10 days ago)
VirtualBox.ModInfo:

[Jim Cromie (jim-cromie)]

OK - heres more info/context.

As originally reported, its a popup when booting a kernel built from source.
It (the same popup) also happened just now, when I installed another new built-from-src kernel.

run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 3.11.0-rc7-chb-00007-g11cf33a /boot/vmlinuz-3.11.0-rc7-chb-00007-g11cf33a
run-parts: executing /etc/kernel/postinst.d/dkms 3.11.0-rc7-chb-00007-g11cf33a /boot/vmlinuz-3.11.0-rc7-chb-00007-g11cf33a
Error! Bad return status for module build on kernel: 3.11.0-rc7-chb-00007-g11cf33a (i686)
Consult /var/lib/dkms/virtualbox/4.2.10/build/make.log for more information.

SO, looking at that logfile, DKMS cant find the .config.

jimc@chumly:~/projects/lx/build-chb$ more /var/lib/dkms/virtualbox/4.2.10/build/make.log
DKMS make.log for virtualbox-4.2.10 for kernel 3.11.0-rc7-chb-00007-g11cf33a (i6
86)
Thu Aug 29 08:55:44 MDT 2013
  HOSTCC scripts/basic/fixdep
  HOSTCC scripts/kconfig/conf.o
  SHIPPED scripts/kconfig/zconf.tab.c
  SHIPPED scripts/kconfig/zconf.lex.c
  SHIPPED scripts/kconfig/zconf.hash.c
  HOSTCC scripts/kconfig/zconf.tab.o
  HOSTLD scripts/kconfig/conf
scripts/kconfig/conf --silentoldconfig Kconfig
***
*** Configuration file ".config" not found!
***
*** Please run some configurator (e.g. "make oldconfig" or
*** "make menuconfig" or "make xconfig").
***
make[7]: *** [silentoldconfig] Error 1
make[6]: *** [silentoldconfig] Error 2
  SYSHDR arch/x86/syscalls/../include/generated/uapi/asm/unistd_32.h
  SYSHDR arch/x86/syscalls/../include/generated/uapi/asm/unistd_64.h
  SYSHDR arch/x86/syscalls/../include/generated/uapi/asm/unistd_x32.h
  SYSTBL arch/x86/syscalls/../include/generated/asm/syscalls_32.h
  HOSTCC arch/x86/tools/relocs_32.o
  HOSTCC arch/x86/tools/relocs_64.o
  HOSTCC arch/x86/tools/relocs_common.o
  HOSTLD arch/x86/tools/relocs
make[5]: *** No rule to make target `include/config/auto.conf', needed by `inclu
de/config/kernel.release'. Stop.
make[4]: *** [all] Error 2
jimc@chumly:~/projects/lx/build-chb$

I suspect that the problem is that the kernel is built with
     make O=../build-chb
and that DKMS doesnt know to find the build symlink

$ ls -l /lib/modules/3.11.0-rc7-chb-00007-g11cf33a/build
lrwxrwxrwx 1 root root 32 Aug 29 08:55 /lib/modules/3.11.0-rc7-chb-00007-g11cf33a/build -> /home/jimc/projects/lx/build-chb

I'll rebuild a new kernel w/o the O=../build-foo, and test that theory, RSN.

[Jim Cromie (jim-cromie)]

scratch that theory.

[Gianfranco Costamagna (costamagnagianfranco)]

should be fixed now