LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (https://www.linuxquestions.org/questions/slackware-14/)
-   -   Virtualbox - Guest additions not building with kernel 4.4.172 (https://www.linuxquestions.org/questions/slackware-14/virtualbox-guest-additions-not-building-with-kernel-4-4-172-a-4175647641/)

seb_62 02-05-2019 03:17 AM

Virtualbox - Guest additions not building with kernel 4.4.172
 
Hi,

All is in the title.
Came back to 4.4.157, work fine.

Have a nice day.

camorri 02-05-2019 08:31 AM

fwiw, virtualbox-kernel-addons won't build on 4.4.172 either. There is a patch to build virtualbox-kernel. On two systems I rebuilt only the kernel with 4.4.172 and all was well.

On the first system I was upgrading, I blew away virtual box, and tried to rebuilt. Nope.

I went to VirtualBox 6.0.4 from Oracle. Willy has posted a fix to get it installed on 4.4.172. It worked fine on that system.

bormant 02-05-2019 09:46 AM

Since 4.4.168+ kernel changed API my personal choice is to jump to 4.19.x kernel from current ;-)
My hardware has drivers compatible with 4.19 so I can do it on my own.

lambo69 02-06-2019 10:58 PM

I ran into the same problem after upgrading to 4.4.172 on Slackware yesterday. On a first view, it doesn't seem to be just guest additions, VirtualBox refuses to build kernel modules, no matter if i take VB 5.5.22, which was the running version, or if I take 6.0.4. Returning to an older kernel (which one ships with Slackware14.2 originally, 4.4.14 iirc?) raises the same error, so VB is completely unusable on that system.

@camorri
Where can i get the patch from? Is it a patch for VirtualBox or for the Kernel?

camorri 02-07-2019 03:11 AM

Here is the link to Willy's SlackBlog. If you want to go to version 6.0.4 from Oracle.

-->https://slackblogs.blogspot.com/

It worked for me, and I have seen posts from others it worked for.

Post #5 in this thread has the patch.

-->https://www.linuxquestions.org/quest...-a-4175647407/

You create the two .diff files that are posted, name them the same as the post, and then run the patch command as listed. This was for version 5.0.40 that is still on SBo. I have no idea if this would work on 5.5.22.

My suggestion would be remove 5.2.22 and go to 6.0.4 from Oracle, and follow Willys post to get it working. You will have to import your .vdi files onto 6.0.4. The documentation tells you hoe to do that.

Best of luck.

lambo69 02-11-2019 10:21 PM

Thank you!
I switched to Kernel 4.20.7, which works for me.


All times are GMT -5. The time now is 04:50 AM.