Support and News Forum

Hello eveng team,
do you know if someone can fix this long standing typo issue with kernel-headers package of eve-ng :


root@lab:/usr/src/virtualbox-5.0.40/vboxdrv# apt list --installed | grep -i eve-ng

WARNING: apt does not have a stable CLI interface. Use with caution in scripts.

eve-ng/unknown,now 2.0.3-86 amd64 [installed]
eve-ng-dynamips/unknown,now 2.0.2-2 amd64 [installed,automatic]
eve-ng-guacamole/unknown,now 2.0.3-69 amd64 [installed,automatic]
eve-ng-qemu/unknown,now 2.0.3-72 amd64 [installed,automatic]
eve-ng-schema/unknown,now 2.0.3-69 amd64 [installed,automatic]
eve-ng-vpcs/unknown,now 1.0-eve-ng amd64 [installed,automatic]
linux-headers-4.9.40-eve-ng-ukms+/unknown,now 4.9.40-eve-ng-ukms-brctl amd64 [installed]
linux-image-4.9.40-eve-ng-ukms-2+/unknown,now 4.9.40-eve-ng-ukms-2-brctl amd64 [installed,automatic]



root@lab:/lib/modules/4.9.40-eve-ng-ukms-2+# modprobe vboxdrv
modprobe: ERROR: could not insert 'vboxdrv': Exec format error
root@lab:/lib/modules/4.9.40-eve-ng-ukms-2+# dmesg | grep vboxdrv
[328634.381407] vboxdrv: version magic '4.9.40-eve-ng-ukms+ SMP mod_unload ' should be '4.9.40-eve-ng-ukms-2+ SMP mod_unload '
root@lab:/lib/modules/4.9.40-eve-ng-ukms-2+#


Note: all baremetal installations are not able to use any other software requires fresh module build (i.e. vmware player /virtualbox) ,
making eve-ng on baremetal environments very limited only for eve-ng and IMO useless.

Please advise.

I see you trying get up eve on vbox..
my advice dont even touch it for eve.

http://www.eve-ng.net/index.php/documen ... equirement

but bare hw installs of eve has no issues at all.
true, dedicated box for eve.

UD

As I said, the installation is bare-metal on ubuntu 16.04 LTS where eve-ng installed using package method (apt-get) as per guide.

But, linux-header package for the (eve-ng) customized kernel seems to has wrong name build , making system unusable for anyone to compile modules.

As example , I tried to install virtualbox (module) , and as you see on the logs above the compile succeeds but the vermagic is wrong , so is not loaded.

The same happens for any other kernel module (i.e. a NIC driver, sound module etc) builded on host.

Here is another example from someone trying to make his host NIC to work :

https://ubuntuforums.org/showthread.php?t=2372856

as in my case the vermagic is wrong due to wrong linux-headers (typo?) .
You can try it to any bare-metal or VM deployment.

Any help to fix the issue appreciated.

Hey, guys!
I'm experiencing the same problem (Linux-headers). Does anyone have a direction to resolve this limitation?
In advance grateful!

Linux eve-ng 4.9.40-eve-ng-ukms-2+

Same problem trying to install Veeam to backup our physical lab server (bare metals install)