Welcome, Guest. Please login or register.
Did you miss your activation email?

Author Topic:  Kernel 3.7.1 couldn't build module for virtualbox  (Read 21275 times)

Offline Geier0815

  • User
  • Posts: 586
Kernel 3.7.1 couldn't build module for virtualbox
« on: 2012/12/18, 08:47:56 »
Hi all,

d-u this morning install kernel 3.7.1 witch is not able to build the virtualbox-module.
Quote from: "make.log"
DKMS make.log for virtualbox-4.1.18 for kernel 3.7-1.towo-siduction-amd64 (x86_64)
Di 18. Dez 08:31:35 CET 2012
make: Entering directory `/usr/src/linux-headers-3.7-1.towo-siduction-amd64'
  LD      /var/lib/dkms/virtualbox/4.1.18/build/built-in.o
  LD      /var/lib/dkms/virtualbox/4.1.18/build/vboxdrv/built-in.o
  CC [M]  /var/lib/dkms/virtualbox/4.1.18/build/vboxdrv/linux/SUPDrv-linux.o
  CC [M]  /var/lib/dkms/virtualbox/4.1.18/build/vboxdrv/SUPDrv.o
  CC [M]  /var/lib/dkms/virtualbox/4.1.18/build/vboxdrv/SUPDrvSem.o
  CC [M]  /var/lib/dkms/virtualbox/4.1.18/build/vboxdrv/r0drv/alloc-r0drv.o
  CC [M]  /var/lib/dkms/virtualbox/4.1.18/build/vboxdrv/r0drv/initterm-r0drv.o
  CC [M]  /var/lib/dkms/virtualbox/4.1.18/build/vboxdrv/r0drv/memobj-r0drv.o
  CC [M]  /var/lib/dkms/virtualbox/4.1.18/build/vboxdrv/r0drv/mpnotification-r0drv.o
  CC [M]  /var/lib/dkms/virtualbox/4.1.18/build/vboxdrv/r0drv/powernotification-r0drv.o
  CC [M]  /var/lib/dkms/virtualbox/4.1.18/build/vboxdrv/r0drv/linux/assert-r0drv-linux.o
  CC [M]  /var/lib/dkms/virtualbox/4.1.18/build/vboxdrv/r0drv/linux/alloc-r0drv-linux.o
  CC [M]  /var/lib/dkms/virtualbox/4.1.18/build/vboxdrv/r0drv/linux/initterm-r0drv-linux.o
  CC [M]  /var/lib/dkms/virtualbox/4.1.18/build/vboxdrv/r0drv/linux/memobj-r0drv-linux.o
/var/lib/dkms/virtualbox/4.1.18/build/vboxdrv/r0drv/linux/memobj-r0drv-linux.c: In function ‘rtR0MemObjNativeMapUser’:
/var/lib/dkms/virtualbox/4.1.18/build/vboxdrv/r0drv/linux/memobj-r0drv-linux.c:1451:38: error: ‘VM_RESERVED’ undeclared (first use in this function)
/var/lib/dkms/virtualbox/4.1.18/build/vboxdrv/r0drv/linux/memobj-r0drv-linux.c:1451:38: note: each undeclared identifier is reported only once for each function it appears in
make[2]: *** [/var/lib/dkms/virtualbox/4.1.18/build/vboxdrv/r0drv/linux/memobj-r0drv-linux.o] Fehler 1
make[1]: *** [/var/lib/dkms/virtualbox/4.1.18/build/vboxdrv] Fehler 2
make: *** [_module_/var/lib/dkms/virtualbox/4.1.18/build] Fehler 2
make: Leaving directory `/usr/src/linux-headers-3.7-1.towo-siduction-amd64'


Moin Moin,

d-u installiert den Kernel 3.7.1 welcher nicht in der Lage ist das Module für virtualbox zu bauen. Also Augen auf!
Wenn Windows die Lösung ist...
kann ich dann bitte das Problem zurück haben?

Offline devil

  • Administrator
  • User
  • *****
  • Posts: 4.838
Kernel 3.7.1 couldn
« Reply #1 on: 2012/12/18, 08:59:19 »
und mit Version 4.2?

greetz
devil

jacmoe

  • Guest
RE: Kernel 3.7.1 couldn
« Reply #2 on: 2012/12/18, 09:00:07 »
They are working on it:

http://www.mail-archive.com/debian-bugs-dist@lists.debian.org/msg1086030.html

If I knew how to use deb diffs..

But it looks like a fix will be available in days.

Offline ayla

  • User
  • Posts: 1.744
Kernel 3.7.1 couldn't build module for virtualbox
« Reply #3 on: 2012/12/18, 09:08:40 »
Version 4.2.4 from Oracle was running fine with Kernel 3.7-0 and
is running fine too after dist-upgrade and Kernel 3.7-1 with no need to act on it.

greets ayla

Edit:

Short description how I installed it:

Code: [Select]
apt-get purge virtualbox
added:
Code: [Select]
deb http://download.virtualbox.org/virtualbox/debian wheezy contrib to one of my sources.list in /etc/apt/sources.list.d/
Code: [Select]
apt-get update
apt-get install virtualbox-4.2 dkms

The new installation has found my old guest system. I hadn't done anything else, except adding my user to group vboxusers in /etc/group, just works.

ahm... If the extensionpack for 4.18 was installed, vbox will detect it and ask whether it should get updatet.
Good idea to say "yes". ;)

jacmoe

  • Guest
Kernel 3.7.1 couldn't build module for virtualbox
« Reply #4 on: 2012/12/18, 10:30:41 »
It works - although I had to purge the vboxadditions iso too:

apt-get purge virtualbox-guest-additions-iso

Offline spacepenguin

  • User
  • Posts: 862
    • spacepenguin.de
Kernel 3.7.1 couldn't build module for virtualbox
« Reply #5 on: 2013/01/04, 00:58:46 »
Does it work with dkms?
Susan | Hardware: SysProfile
Music-Profile: http://www.last.fm/de/user/spacepengu

Offline ayla

  • User
  • Posts: 1.744
Kernel 3.7.1 couldn't build module for virtualbox
« Reply #6 on: 2013/01/04, 07:19:07 »
hmm, I guess so:

Quote
ls -l /var/lib/dkms/vboxhost/4.2.4/3.7-1.towo-siduction-amd64/x86_64/module/
insgesamt 2008
-rw-r--r-- 1 root root 1973560 Dez 18 09:03 vboxdrv.ko
-rw-r--r-- 1 root root   12296 Dez 18 09:03 vboxnetadp.ko
-rw-r--r-- 1 root root   30464 Dez 18 09:03 vboxnetflt.ko
-rw-r--r-- 1 root root   30640 Dez 18 09:03 vboxpci.ko

Offline oduffo

  • User
  • Posts: 198
Kernel 3.7.1 couldn't build module for virtualbox
« Reply #7 on: 2013/01/05, 16:26:51 »
Hi,
similar problem here.

Vbox 4.2.4 was working fine with kernel 3.6-6 and dkms installed.

Did a d-u this morning pulling in kernel 3.7-1. Virtualbox complained about missing kernel modules.
Code: [Select]
/etc/init.d/vboxdrv setup didn't help.

I purged virtualbox and installed newest version 4.2.6. Same result
Code: [Select]
~$ virtualbox
WARNING: The vboxdrv kernel module is not loaded. Either there is no module
         available for the current kernel (3.7-1.towo-siduction-amd64) or it failed to
         load. Please recompile the kernel module and install it by
           sudo /etc/init.d/vboxdrv setup
         You will not be able to start VMs until this problem is fixed.

Any help would be appreciated.

Gruß
oduffo

Offline oduffo

  • User
  • Posts: 198
Kernel 3.7.1 couldn't build module for virtualbox
« Reply #8 on: 2013/01/05, 16:55:33 »
Problem solved due to some hints in the vbox-forums.

I reinstalled the linux-kernel-headers and did a reboot.
The latter I should have done in the first place.

Gruß
oduffo (who is happy again)

mylo

  • Guest
Kernel 3.7.1 couldn't build module for virtualbox
« Reply #9 on: 2013/01/20, 14:38:03 »
What is the most secure strategy to solve the prob?

Code: [Select]
DKMS make.log for virtualbox-4.1.18 for kernel 3.7-3.towo-siduction-amd64 (x86_64)
So 20. Jan 13:51:59 CET 2013
make: Entering directory `/usr/src/linux-headers-3.7-3.towo-siduction-amd64'
  LD      /var/lib/dkms/virtualbox/4.1.18/build/built-in.o
  LD      /var/lib/dkms/virtualbox/4.1.18/build/vboxdrv/built-in.o
  CC [M]  /var/lib/dkms/virtualbox/4.1.18/build/vboxdrv/linux/SUPDrv-linux.o
  CC [M]  /var/lib/dkms/virtualbox/4.1.18/build/vboxdrv/SUPDrv.o
  CC [M]  /var/lib/dkms/virtualbox/4.1.18/build/vboxdrv/SUPDrvSem.o
  CC [M]  /var/lib/dkms/virtualbox/4.1.18/build/vboxdrv/r0drv/alloc-r0drv.o
  CC [M]  /var/lib/dkms/virtualbox/4.1.18/build/vboxdrv/r0drv/initterm-r0drv.o
  CC [M]  /var/lib/dkms/virtualbox/4.1.18/build/vboxdrv/r0drv/memobj-r0drv.o
  CC [M]  /var/lib/dkms/virtualbox/4.1.18/build/vboxdrv/r0drv/mpnotification-r0drv.o
  CC [M]  /var/lib/dkms/virtualbox/4.1.18/build/vboxdrv/r0drv/powernotification-r0drv.o
  CC [M]  /var/lib/dkms/virtualbox/4.1.18/build/vboxdrv/r0drv/linux/assert-r0drv-linux.o
  CC [M]  /var/lib/dkms/virtualbox/4.1.18/build/vboxdrv/r0drv/linux/alloc-r0drv-linux.o
  CC [M]  /var/lib/dkms/virtualbox/4.1.18/build/vboxdrv/r0drv/linux/initterm-r0drv-linux.o
  CC [M]  /var/lib/dkms/virtualbox/4.1.18/build/vboxdrv/r0drv/linux/memobj-r0drv-linux.o
/var/lib/dkms/virtualbox/4.1.18/build/vboxdrv/r0drv/linux/memobj-r0drv-linux.c: In function ‘rtR0MemObjNativeMapUser’:
/var/lib/dkms/virtualbox/4.1.18/build/vboxdrv/r0drv/linux/memobj-r0drv-linux.c:1451:38: error: ‘VM_RESERVED’ undeclared (first use in this function)
/var/lib/dkms/virtualbox/4.1.18/build/vboxdrv/r0drv/linux/memobj-r0drv-linux.c:1451:38: note: each undeclared identifier is reported only once for each function it appears in
make[2]: *** [/var/lib/dkms/virtualbox/4.1.18/build/vboxdrv/r0drv/linux/memobj-r0drv-linux.o] Fehler 1
make[1]: *** [/var/lib/dkms/virtualbox/4.1.18/build/vboxdrv] Fehler 2
make: *** [_module_/var/lib/dkms/virtualbox/4.1.18/build] Fehler 2
make: Leaving directory `/usr/src/linux-headers-3.7-3.towo-siduction-amd64'


Do I just apt-get purge linux-kernel-headers and install them again?

Offline oduffo

  • User
  • Posts: 198
Kernel 3.7.1 couldn't build module for virtualbox
« Reply #10 on: 2013/01/21, 13:26:46 »
@mylo,

first of all I would install latest version of virtualbox 4.2.6 from Oracle.

Gruß
oduffo

Offline sunrat

  • User
  • Posts: 406
Kernel 3.7.1 couldn't build module for virtualbox
« Reply #11 on: 2013/01/21, 14:49:59 »
I installed VBox 4.2.6 for kernel 3.7-1 but don't recall if it built module with dkms. Dist-upgrade today brought in kernel 3.7-3 but module did not build with dkms. It built OK manually.
 Should it build with dkms?
Headers are installed, virtualbox-dkms package is not available for VBox 4.2.6. I am in vboxusers group.

Code: [Select]
apt-cache policy virtualbox-dkms
virtualbox-dkms:
  Installed: (none)
  Candidate: 4.1.18-dfsg-2
  Version table:
     4.1.18-dfsg-2 0
        500 http://http.debian.net/debian/ unstable/main amd64 Packages

Offline ayla

  • User
  • Posts: 1.744
Kernel 3.7.1 couldn't build module for virtualbox
« Reply #12 on: 2013/01/21, 15:01:25 »
Quote
Should it build with dkms?


It had build here (twice now, for 3.7-2 and 3.7-3).

Just
Code: [Select]
apt-get install dkms


virtualbox-dkms is not needed for the Oracle module.

Greets
ayla

Offline sunrat

  • User
  • Posts: 406
Kernel 3.7.1 couldn't build module for virtualbox
« Reply #13 on: 2013/01/21, 15:08:44 »
Code: [Select]
apt-cache policy dkms
dkms:
  Installed: 2.2.0.3-1.2


Installed already. Oh well, only a small problem as it built manually.

Offline orinoco

  • User
  • Posts: 233
  • Bullshit artist
Kernel 3.7.1 couldn't build module for virtualbox
« Reply #14 on: 2013/01/25, 13:43:02 »
Why aren't the matching headerfiles automatically installed if d-u brings a new kernal? Without this all dkms tasks are failling (virtualbox-oracle, fglrx, etc.) as long I install the propper header-files by hand. My fault?