Arch Linux

sgillespie

Member

Registered: 2012-12-28

Posts: 32

Grsecurity and virtualbox [solved]

Hi,

I recently installed virtualbox so I could run an android emulator.  Unfortunately, I can't load vboxdrv after booting with the grsecurity kernel:

Dec 12 18:08:04 XXXXX systemd[1]: systemd-modules-load.service: main process exited, code=exited, status=1/FAILURE
Dec 12 18:08:04 XXXXX systemd[1]: Failed to start Load Kernel Modules.
Dec 12 18:08:04 XXXXX systemd[1]: Unit systemd-modules-load.service entered failed state.
Dec 12 18:08:04 XXXXX systemd[1]: systemd-modules-load.service failed.

After looking around a little more, I found I had some stuff in /etc/modules-load.d/virtualbox.conf

And now I try to load vboxdir

bash$ sudo modprobe vboxdrv
modprobe: FATAL: Module vboxdrv not found.

Pardon my newbiness, but what should I do?

Last edited by sgillespie (2014-12-13 00:48:54)

jasonwryan

Anarchist

From: .nz

Registered: 2009-05-09

Posts: 30,426

Website

Re: Grsecurity and virtualbox [solved]

It looks like the grsecurity kernel doesn't include that module. What does `cat /proc/config.gz | grep vbox` show?

---

Arch + dwm   •   Mercurial repos  •   Surfraw

Registered Linux User #482438

lucke

Member

From: Poland

Registered: 2004-11-30

Posts: 4,019

Re: Grsecurity and virtualbox [solved]

You need to build the module. https://wiki.archlinux.org/index.php/Vi … tom_kernel

sgillespie

Member

Registered: 2012-12-28

Posts: 32

Re: Grsecurity and virtualbox [solved]

So, not sure I did this correctly, but here's what I did

sudo pacman -S virtualbox-host-dkms
sudo pacman -Rsn virtualbox-host-modules
sudo pacman -S linux-grsec-headers
sudo dkms install vboxhost/4.3.20 3.17.6.201412071639-1-grsec/x86_64

And then I got

: I do not know how to handle 3.17.6.201412071639-1-grsec/x86_64.

Kernel preparation unnecessary for this kernel.  Skipping...

Building module:
cleaning build area.....
make KERNELRELEASE=3.17.6.201412071639-1-grsec -C /usr/lib/modules/3.17.6.201412071639-1-grsec/
build M=/var/lib/dkms/vboxhost/4.3.20/build....(bad exit status: 2)
Error! Bad return status for module build on kernel: 3.17.6.201412071639-1-grsec (x86_64)
Consult /var/lib/dkms/vboxhost/4.3.20/build/make.log for more information.

And the mentioned make.log

DKMS make.log for vboxhost-4.3.20 for kernel 3.17.6.201412071639-1-grsec (x86_64)
Fri Dec 12 19:29:59 EST 2014
make: Entering directory '/usr/lib/modules/3.17.6.201412071639-1-grsec/build'
  LD      /var/lib/dkms/vboxhost/4.3.20/build/built-in.o
  LD      /var/lib/dkms/vboxhost/4.3.20/build/vboxdrv/built-in.o
  CC [M]  /var/lib/dkms/vboxhost/4.3.20/build/vboxdrv/linux/SUPDrv-linux.o
cc1: error: incompatible gcc/plugin versions
cc1: error: fail to initialize plugin ./tools/gcc/constify_plugin.so
cc1: error: incompatible gcc/plugin versions
cc1: error: fail to initialize plugin ./tools/gcc/stackleak_plugin.so
cc1: error: incompatible gcc/plugin versions
cc1: error: fail to initialize plugin ./tools/gcc/colorize_plugin.so
cc1: error: incompatible gcc/plugin versions
cc1: error: fail to initialize plugin ./tools/gcc/kernexec_plugin.so
cc1: error: incompatible gcc/plugin versions
cc1: error: fail to initialize plugin ./tools/gcc/size_overflow_plugin/size_overflow_plugin.so
cc1: error: incompatible gcc/plugin versions
cc1: error: fail to initialize plugin ./tools/gcc/structleak_plugin.so
scripts/Makefile.build:257: recipe for target '/var/lib/dkms/vboxhost/4.3.20/build/vboxdrv/linux/SUPDrv-linux.o' failed
make[2]: *** [/var/lib/dkms/vboxhost/4.3.20/build/vboxdrv/linux/SUPDrv-linux.o] Error 1
scripts/Makefile.build:404: recipe for target '/var/lib/dkms/vboxhost/4.3.20/build/vboxdrv' failed
make[1]: *** [/var/lib/dkms/vboxhost/4.3.20/build/vboxdrv] Error 2
Makefile:1450: recipe for target '_module_/var/lib/dkms/vboxhost/4.3.20/build' failed
make: *** [_module_/var/lib/dkms/vboxhost/4.3.20/build] Error 2
make: Leaving directory '/usr/lib/modules/3.17.6.201412071639-1-grsec/build'

sgillespie

Member

Registered: 2012-12-28

Posts: 32

Re: Grsecurity and virtualbox [solved]

Nevermind, I got rid of gcc-multilib and it worked.  Thanks for the help!