[SOLVED] Virtualbox-kernel compile error.

business_kid · 03-09-2015, 07:27 AM

Every new kernel I have to recompile the virtualbox kernel. I did what I thought was the safe thing with the same source as before
make clean
make
make DESTDIR=/blah install
Here's the meltdown:

Code:

*** Building 'vboxnetadp' module ***
make[1]: Entering directory `/usr/src/virtualbox-kernel-4.3.10/vboxnetadp'
make KBUILD_VERBOSE= SUBDIRS=/usr/src/virtualbox-kernel-4.3.10/vboxnetadp SRCROOT=/usr/src/virtualbox-kernel-4.3.10/vboxnetadp CONFIG_MODULE_SIG= -C /lib/modules/3.19.0-rc6/build modules
make[2]: Entering directory `/usr/src/linux-stable'
  CC [M]  /usr/src/virtualbox-kernel-4.3.10/vboxnetadp/linux/VBoxNetAdp-linux.o
/usr/src/virtualbox-kernel-4.3.10/vboxnetadp/linux/VBoxNetAdp-linux.c: In function 'vboxNetAdpOsCreate':
[B]/usr/src/virtualbox-kernel-4.3.10/vboxnetadp/linux/VBoxNetAdp-linux.c:186:48: error: macro "alloc_netdev" requires 4 arguments, but only 3 given[/B]
                            vboxNetAdpNetDevInit);
                                                ^
/usr/src/virtualbox-kernel-4.3.10/vboxnetadp/linux/VBoxNetAdp-linux.c:184:15: error: 'alloc_netdev' undeclared (first use in this function)
     pNetDev = alloc_netdev(sizeof(VBOXNETADPPRIV),
               ^
/usr/src/virtualbox-kernel-4.3.10/vboxnetadp/linux/VBoxNetAdp-linux.c:184:15: note: each undeclared identifier is reported only once for each function it appears in
/usr/src/virtualbox-kernel-4.3.10/vboxnetadp/linux/VBoxNetAdp-linux.c: At top level:
/usr/src/virtualbox-kernel-4.3.10/vboxnetadp/linux/VBoxNetAdp-linux.c:159:13: warning: 'vboxNetAdpNetDevInit' defined but not used [-Wunused-function]
 static void vboxNetAdpNetDevInit(struct net_device *pNetDev)
             ^
make[3]: *** [/usr/src/virtualbox-kernel-4.3.10/vboxnetadp/linux/VBoxNetAdp-linux.o] Error 1
make[2]: *** [_module_/usr/src/virtualbox-kernel-4.3.10/vboxnetadp] Error 2
make[2]: Leaving directory `/usr/src/linux-stable'
make[1]: *** [vboxnetadp] Error 2
make[1]: Leaving directory `/usr/src/virtualbox-kernel-4.3.10/vboxnetadp'
cp: cannot stat 'vboxnetadp/vboxnetadp.ko': No such file or directory

*** Building 'vboxpci' module ***
make[1]: Entering directory `/usr/src/virtualbox-kernel-4.3.10/vboxpci'
make KBUILD_VERBOSE= SUBDIRS=/usr/src/virtualbox-kernel-4.3.10/vboxpci SRCROOT=/usr/src/virtualbox-kernel-4.3.10/vboxpci CONFIG_MODULE_SIG= -C /lib/modules/3.19.0-rc6/build modules
make[2]: Entering directory `/usr/src/linux-stable'
  Building modules, stage 2.
  MODPOST 1 modules
make[2]: Leaving directory `/usr/src/linux-stable'
make[1]: Leaving directory `/usr/src/virtualbox-kernel-4.3.10/vboxpci'

Is it the fact that I'm using a linux-stable as the kernel source?

Ztcoracat · 03-16-2015, 11:37 PM

Not sure if it's because your using a linux-stable as the kernel src or not-
Maybe because of changes made in the kernel?

This is the stuff that is maddening:-
This one has me baffeled.

I looked up this to find the thread below.

Code:

make[1]: Leaving directory `/usr/src/virtualbox-kernel-4.3.10/vboxnetadp'
cannot stat 'vboxnetadp/vboxnetadp.ko': No such file or directory

Maybe upgrade VBox it helped others in this thread.
https://forums.gentoo.org/viewtopic-...4-start-0.html

http://pietrushnic.github.io/blog/20...0-rcx-headers/

HTH business_kid gave it my best:-

Cheers

business_kid · 03-18-2015, 04:14 AM

My source is there still, and I ran 'make' in your honour.

There has to be a higher error; I get that too - it didn't make the module. It's just doing a cd to top source and checking it actually made the module, and flagging that it didn't. That's verbose, convoluted and weird, but maybe necessary.

Ztcoracat · 03-18-2015, 07:53 PM

Maybe read through the build log and see where it starts to go south.

Try updating your VBox to the latest and downgrade your kernel. (just an idea)

I'm pondering on the output of this thread to see if anything comes to mind.
http://www.gossamer-threads.com/list...oo/user/295862

-:-If there is a higher error I'm not sure where it would be aside form the build log.-:-

Not sure if debugging the kernel is the answer but it did come to mind.

Are you able to boot the guest?
Do you have the suspicion that this could this be a bug?

business_kid · 03-19-2015, 05:10 AM

Well, in my case, I may have spotted it.

To get around linux-stable, I created a symlink in /usr/src 3.19.0-rc6 --> linux-stable, and altered the build and source symlinks in /lib/modules. Then I made clean, and went from there. And it built successfully, but still managed to pick up linux-stable from somewhere.

There's also an undeclared function (first use of . . . .) which incdicates an earlier error, but I'll have to need this thing real bad before I dig through that!

Thinks: next try, I'll have to go back to the configure, mv linux-stable --> linux-3.19.0-rc6, and have linux-stable as the symlink.

Ztcoracat · 03-19-2015, 09:57 PM

Well I hope your able to fix it.

This seems to be more than what I understand.

business_kid · 05-04-2015, 12:14 PM

Well, sorted it by installing virtualbox-kernel-4.3.24.

I'm guessing the git kernel was not compatible in some way with 4.3.10, and that a later version sorted it.

Ztcoracat · 05-04-2015, 07:59 PM

Quote:

Originally Posted by business_kid

Well, sorted it by installing virtualbox-kernel-4.3.24.

I'm guessing the git kernel was not compatible in some way with 4.3.10, and that a later version sorted it.

Glad to hear the good news.

Could of been a compatibility issue; very possible.

Ztcoracat · 05-04-2015, 08:00 PM

Was it difficult installing VBox on Slack?

business_kid · 05-05-2015, 03:42 AM

No difficulty with virtualbox itself. VirtualBox requires acpica, the jdk package from /extra.

My difficulties have been with stupid things. I have a versioning issue (new thread) because the modules didn't pick up the '-rc6' on my kernel (3.19.0-rc6) so they throw a versioning error "Exec format error."

The thing insists on putting the machines in Virtualbox\ VMs, but try as you might, you won't mount a partition on a directory with a space in it. Every time you change kernel version, you need a new set of virtialbox-kernel modules. Hence the pain.

Ztcoracat · 05-05-2015, 05:54 PM

Quote:

Originally Posted by business_kid

No difficulty with virtualbox itself. VirtualBox requires acpica, the jdk package from /extra.

My difficulties have been with stupid things. I have a versioning issue (new thread) because the modules didn't pick up the '-rc6' on my kernel (3.19.0-rc6) so they throw a versioning error "Exec format error."

The thing insists on putting the machines in Virtualbox\ VMs, but try as you might, you won't mount a partition on a directory with a space in it. Every time you change kernel version, you need a new set of virtialbox-kernel modules. Hence the pain.

Yeah, I see where that could be redundant and painful:-

I'll try installing VBox on my Slackware box and see how it goes.

Thanks:-