linux-headers-3.8.0-14-lowlatency won't allow virtualbox modules to build

[elguavas]

when trying to install virtualbox with these headers installed dkms fails to build the virtualbox drivers.

virtualbox installs normally with the current generic kernel headers.

trying to install virtualbox throws this error:

Setting up linux-headers-3.8.0-14-lowlatency (3.8.0-14.9) ...
Examining /etc/kernel/header_postinst.d.
run-parts: executing /etc/kernel/header_postinst.d/dkms 3.8.0-14-lowlatency /boot/vmlinuz-3.8.0-14-lowlatency
Error! Bad return status for module build on kernel: 3.8.0-14-lowlatency (x86_64)
Consult /var/lib/dkms/virtualbox/4.2.10/build/make.log for more information.

contents of /var/lib/dkms/virtualbox/4.2.10/build/make.log on build failure:

DKMS make.log for virtualbox-4.2.10 for kernel 3.8.0-14-lowlatency (x86_64)
Wed Apr 10 12:19:43 EST 2013
make: Entering directory `/usr/src/linux-headers-3.8.0-14-lowlatency'
make: Makefile: No such file or directory
make: *** No rule to make target `Makefile'. Stop.
make: Leaving directory `/usr/src/linux-headers-3.8.0-14-lowlatency'

[Daniel van Vugt (vanvugt)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 821816, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.

[elguavas (elguavas.)]

this bug wasn't a duplicate, since as i pointed out the regular kernel headers built the virtualbox modules just fine and it only affected the lowlatency headers.

in any case today my lowlatency headers were updated to 3.8.0-17 and the bug is fixed. so whether this is a duplicate or not it can be closed.

[Kaj Ailomaa (zequence)]

Could you please try the latest kernel release (3.8.0.18.8). there's a fix for broken header links, so a good chance your problem will be solved by this.

[elguavas (elguavas.)]

yes i already reported above that this was fixed with the new lowlatency
headers and the bug could be closed.

On 13/04/13 03:32, Kaj Ailomaa wrote:
> Could you please try the latest kernel release (3.8.0.18.8). there's a
> fix for broken header links, so a good chance your problem will be
> solved by this.
>

[Kaj Ailomaa (zequence)]

I think probably what fixed your problem was that you installed generic headers, and then the links from -lowlatency headers wold work. See https://bugs.launchpad.net/ubuntu/+source/linux-lowlatency/+bug/1165259.

The fix only landed with 3.8.0-18. But, I'll just assume the header linkage fix also fixed your problem, and will mark this as a duplicate.