Problems with VirtualBox kernel modules
Hello All, After migrating my system (Fedora 20 x86_64) from a spinning disc on an old MB to an SSD on a new UEFI MB, I have problems starting any of my VirtualBox guest systems. The message I get says that either the kernel drivers are not installed or there is a permission problem with /etc/init.d/vboxdrv. I have run /etc/init.d/vboxdrv setup and that reports... Stopping VirtualBox kernel modules [ OK ] Uninstalling old VirtualBox DKMS kernel modules [ OK ] Trying to register the VirtualBox kernel modules using DKMS[ OK ] Starting VirtualBox kernel modules [FAILED] and sudo modprobe vboxdrv reports... modprobe: ERROR: could not insert 'vboxdrv': Required key not available so, does this mean that the problem is to do with a missing EFI boot key? Is there any way to fix this? Cheers, -- Regards, Terry Duell
On 10/06/14 16:33, Terry Duell wrote:
modprobe: ERROR: could not insert 'vboxdrv': Required key not available
<https://fedoraproject.org/wiki/Secureboot> Q: What if I want to build a custom kernel or load 3rd party kernel modules? A: You will need to disable Secure Boot, or setup your own keys and sign everything with them.
Hello Jeremy, On Tue, 10 Jun 2014 21:04:50 +1000, Jeremy Visser <jeremy@visser.name> wrote:
On 10/06/14 16:33, Terry Duell wrote:
modprobe: ERROR: could not insert 'vboxdrv': Required key not available
<https://fedoraproject.org/wiki/Secureboot>
Q: What if I want to build a custom kernel or load 3rd party kernel modules?
A: You will need to disable Secure Boot, or setup your own keys and sign everything with them.
I'll have a look at MB firmware settings. Cheers, -- Regards, Terry Duell
On Wed, 11 Jun 2014 08:52:05 +1000, Terry Duell <tduell@iinet.net.au> wrote:
Hello Jeremy,
On Tue, 10 Jun 2014 21:04:50 +1000, Jeremy Visser <jeremy@visser.name> wrote:
On 10/06/14 16:33, Terry Duell wrote:
modprobe: ERROR: could not insert 'vboxdrv': Required key not available
<https://fedoraproject.org/wiki/Secureboot>
Q: What if I want to build a custom kernel or load 3rd party kernel modules?
A: You will need to disable Secure Boot, or setup your own keys and sign everything with them.
I'll have a look at MB firmware settings.
That was the cause of the problem, thanks for pointing that out. I have disabled secure boot and my VirtualBox guests start and run OK. It has introduced another minor problem that I would rather I didn't have. No matter what boot order I set in the BIOS it now always boots Fedora on my old spinning disc, which I would prefer to keep available until I am sure I have found all the problems with the new SSD installation. To boot the SSD I have to interrupt the boot (F8 to get to boot order) and choose the SSD. Maybe there is some combination of settings that will make the BIOS honour my set boot order, but not stumbled on it yet. The MB documentation is a bit sparse. The MB is an Asus Z97M-plus. Cheers, -- Regards, Terry Duell
On Wed, 11 Jun 2014 15:54:27 +1000, Terry Duell <tduell@iinet.net.au> wrote: [snip]
No matter what boot order I set in the BIOS it now always boots Fedora on my old spinning disc, which I would prefer to keep available until I am sure I have found all the problems with the new SSD installation. [snip] Maybe there is some combination of settings that will make the BIOS honour my set boot order, but not stumbled on it yet. The MB documentation is a bit sparse.
Greatcoats off...problem solved. Cheers, -- Regards, Terry Duell
participants (2)
-
Jeremy Visser -
Terry Duell