You are not logged in.
I compiled a custom kernel, making sure not to touch vbox settings IMO. Yet, virtual box fails with:
The VirtualBox Linux kernel driver (vboxdrv) is either not loaded or there is a permission problem with /dev/vboxdrv.
"https://wiki.archlinux.org/index.php/VirtualBox" has:
When using a custom kernel with CONFIG_MODULE_SIG_FORCE option enabled, you must sign your modules with a key generated during kernel compilation.
Note that /lib/modules/4.8.13-1-broadwell/kernel/misc/vboxdrv.ko doesn't exist. Seems I need to fix a number of things before I can sign the modules "with a key generated during kernel compilation" (per ttps://wiki.archlinux.org/index.php/VirtualBox).
I found this (https://bbs.archlinux.org/viewtopic.php?id=199723) and now I am not sure if I understand the implications of following:
- for linux kernel choose virtualbox-host-modules-arch
- for other kernels choose virtualbox-host-dkms
I had virtualbox-host-modules-arch installed and it works fine with my stock kernel or -CK kernel.
It seems for a custom kernel I need virtualbox-host-dkms. But that means I need to remove virtualbox-host-modules-arch (because: conflict). After removing that packagae, will, when I boot in stock or -CK kernel, vbox still work?
Last edited by Bronze (2017-02-11 03:20:52)
Offline
It should still work as dkms compiles modules for all currently installed kernels.
自分を信じなさい(´・ω・`)
Offline