VirtualBox 5.0.24 is not registering module on kernel 4.7-rc6

[turneliusz]

Reporting compatibility problem with newest 4.7-rc6. Latest working version is 4.7-rc4.

[  148.178280] vboxdrv: Unknown symbol mod_timer_pinned (err 0)
[  148.178322] vboxdrv: Unknown symbol __get_vm_area (err 0)
[  148.178343] vboxdrv: Unknown symbol set_pages_nx (err 0)
[  148.178363] vboxdrv: Unknown symbol smp_call_function (err 0)
[  148.178398] vboxdrv: Unknown symbol map_vm_area (err 0)
[  148.178425] vboxdrv: Unknown symbol set_pages_x (err 0)

[turneliusz]

Just for clarification, latest working version I have tried was 4.7-rc3

[Frank Mehnert]

I cannot reproduce your problem. I compiled the vboxdrv modules against Linux 4.7-rc6, loaded it and successfully started a VM. Looks to me like you compiled the VBox modules against kernel headers which do not match your currently running kernel.

[Michael Stucki]

I'm having exactly the same problem. Ubuntu Xenial, Kernel 4.7.0-rc6 from ​http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.7-rc6-yakkety/, VirtualBox 5.0.18-dfsg-2build1 from Ubuntu default repositories. This worked fine with 4.7-rc4.

Note: I had to patch the driver already before to make it build with kernel 4.7. So the patch "vbox-4.7-rc1.patch" from ​https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=825819 needs to be applied and then it works on kernels up to 4.7-rc4. However with 4.7-rc5 and 4.7-rc6 it won't work anymore.

[Frank Mehnert]

Replying to stucki:

I'm having exactly the same problem. Ubuntu Xenial, Kernel 4.7.0-rc6 from ​http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.7-rc6-yakkety/, VirtualBox 5.0.18-dfsg-2build1 from Ubuntu default repositories. This worked fine with 4.7-rc4.

Maybe these packages just have a problem. It wouldn't be the first time if such Ubuntu ppa repos would have a problem. As I said above, no problem using 4.7-rc6 vanilla sources.

Note: I had to patch the driver already before to make it build with kernel 4.7. So the patch "vbox-4.7-rc1.patch" from ​https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=825819 needs to be applied and then it works on kernels up to 4.7-rc4. However with 4.7-rc5 and 4.7-rc6 it won't work anymore.

Completely unrelated. Something you need to tell the distro people. VBox 5.0.18 was released long before Linux 4.7 was in sight. These adaptions were made in VBox 5.0.22 and the official 5.0.24 packages from last week have the fix as well.

[Michael Stucki]

Thanks for the reply, Frank!

Replying to frank:

Replying to stucki:

Note: I had to patch the driver already before to make it build with kernel 4.7. So the patch "vbox-4.7-rc1.patch" from ​https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=825819 needs to be applied and then it works on kernels up to 4.7-rc4. However with 4.7-rc5 and 4.7-rc6 it won't work anymore.

Completely unrelated. Something you need to tell the distro people. VBox 5.0.18 was released long before Linux 4.7 was in sight. These adaptions were made in VBox 5.0.22 and the official 5.0.24 packages from last week have the fix as well.

It's clear to me that this is unrelated. I was just going to document what I've used to reproduce the problem. Without the change, you wouldn't get to the point where the error happens.

[Michael Stucki]

Using 4.7.0-rc7 from ​http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.7-rc7/ the problem is gone.

[Frank Mehnert]

Thanks for letting us know!