Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

Virtual Box on Fedora 19

I installed Virtual Box 4.2 from rpmfusion/free using this command:

yum repository-packages rpmfusion-free install VirtualBox

It installed the dependency kmod-VirtualBox correctly.

# yum list installed | grep VirtualBox
VirtualBox.x86_64              4.2.18-2.fc19        @rpmfusion-free-updates     
kmod-VirtualBox-3.11.4-201.fc19.x86_64.x86_64

However, Virtual Box fails to start a VM:

$ virtualbox
WARNING: The vboxdrv kernel module is not loaded. Either there is no module
         available for the current kernel (3.11.4-201.fc19.x86_64) or it failed to
         load. Please make sure that you have kmod-VirtualBox for current kernel and load the kernel module by executing

           'systemctl restart systemd-modules-load.service' (as root)

         You will not be able to start VMs until this problem is fixed.

When I try to manually load the kernel modules, an error occurs as well:

# systemctl restart systemd-modules-load.service
Job for systemd-modules-load.service failed. See 'systemctl status systemd-modules-load.service' and 'journalctl -xn' for details.

The error is due to a module not being loaded.

# systemctl status systemd-modules-load.service
systemd-modules-load.service - Load Kernel Modules
   Loaded: loaded (/usr/lib/systemd/system/systemd-modules-load.service; static)
   Active: failed (Result: exit-code) since Tue 2013-10-22 02:46:44 CEST; 3min 49s ago
     Docs: man:systemd-modules-load.service(8)
           man:modules-load.d(5)
  Process: 1949 ExecStart=/usr/lib/systemd/systemd-modules-load (code=exited, status=1/FAILURE)

Oct 22 02:46:44 maarten-acer2 systemd-modules-load[1949]: Failed to insert 'vboxdrv': Required key not available
Oct 22 02:46:44 maarten-acer2 systemd[1]: systemd-modules-load.service: main process exited, code=exited, status=1/FAILURE
Oct 22 02:46:44 maarten-acer2 systemd[1]: Failed to start Load Kernel Modules.
Oct 22 02:46:44 maarten-acer2 systemd[1]: Unit systemd-modules-load.service entered failed state.

Finally, it comes down to vboxdrv not being signed by Fedora's key!

# modprobe vboxdrv
modprobe: ERROR: could not insert 'vboxdrv': Required key not available

I think Virtual Box is packaged incorrectly. The kernel modules should have been signed by Fedora's keys.

This problem is closely related to my previous question.

Virtual Box on Fedora 1919 fails to start a VM

I installed Virtual Box 4.2 from rpmfusion/free using this command:

yum repository-packages rpmfusion-free install VirtualBox

It installed the dependency kmod-VirtualBox correctly.

# yum list installed | grep VirtualBox
VirtualBox.x86_64              4.2.18-2.fc19        @rpmfusion-free-updates     
kmod-VirtualBox-3.11.4-201.fc19.x86_64.x86_64

However, Virtual Box fails to start a VM:

$ virtualbox
WARNING: The vboxdrv kernel module is not loaded. Either there is no module
         available for the current kernel (3.11.4-201.fc19.x86_64) or it failed to
         load. Please make sure that you have kmod-VirtualBox for current kernel and load the kernel module by executing

           'systemctl restart systemd-modules-load.service' (as root)

         You will not be able to start VMs until this problem is fixed.

When I try to manually load the kernel modules, an error occurs as well:

# systemctl restart systemd-modules-load.service
Job for systemd-modules-load.service failed. See 'systemctl status systemd-modules-load.service' and 'journalctl -xn' for details.

The error is due to a module not being loaded.

# systemctl status systemd-modules-load.service
systemd-modules-load.service - Load Kernel Modules
   Loaded: loaded (/usr/lib/systemd/system/systemd-modules-load.service; static)
   Active: failed (Result: exit-code) since Tue 2013-10-22 02:46:44 CEST; 3min 49s ago
     Docs: man:systemd-modules-load.service(8)
           man:modules-load.d(5)
  Process: 1949 ExecStart=/usr/lib/systemd/systemd-modules-load (code=exited, status=1/FAILURE)

Oct 22 02:46:44 maarten-acer2 systemd-modules-load[1949]: Failed to insert 'vboxdrv': Required key not available
Oct 22 02:46:44 maarten-acer2 systemd[1]: systemd-modules-load.service: main process exited, code=exited, status=1/FAILURE
Oct 22 02:46:44 maarten-acer2 systemd[1]: Failed to start Load Kernel Modules.
Oct 22 02:46:44 maarten-acer2 systemd[1]: Unit systemd-modules-load.service entered failed state.

Finally, it comes down to vboxdrv not being signed by Fedora's key!

# modprobe vboxdrv
modprobe: ERROR: could not insert 'vboxdrv': Required key not available

I think Virtual Box is packaged incorrectly. The kernel modules should have been signed by Fedora's keys.

This problem is closely related to my previous question.

Virtual Box on Fedora 19 fails to start a VM

I installed Virtual Box 4.2 from rpmfusion/free using this command:

yum repository-packages rpmfusion-free install VirtualBox

It installed the dependency kmod-VirtualBox correctly.

# yum list installed | grep VirtualBox
VirtualBox.x86_64              4.2.18-2.fc19        @rpmfusion-free-updates     
kmod-VirtualBox-3.11.4-201.fc19.x86_64.x86_64

However, Virtual Box fails to start a VM:

$ virtualbox
WARNING: The vboxdrv kernel module is not loaded. Either there is no module
         available for the current kernel (3.11.4-201.fc19.x86_64) or it failed to
         load. Please make sure that you have kmod-VirtualBox for current kernel and load the kernel module by executing

           'systemctl restart systemd-modules-load.service' (as root)

         You will not be able to start VMs until this problem is fixed.

When I try to manually load the kernel modules, an error occurs as well:

# systemctl restart systemd-modules-load.service
Job for systemd-modules-load.service failed. See 'systemctl status systemd-modules-load.service' and 'journalctl -xn' for details.

The error is due to a module not being loaded.

# systemctl status systemd-modules-load.service
systemd-modules-load.service - Load Kernel Modules
   Loaded: loaded (/usr/lib/systemd/system/systemd-modules-load.service; static)
   Active: failed (Result: exit-code) since Tue 2013-10-22 02:46:44 CEST; 3min 49s ago
     Docs: man:systemd-modules-load.service(8)
           man:modules-load.d(5)
  Process: 1949 ExecStart=/usr/lib/systemd/systemd-modules-load (code=exited, status=1/FAILURE)

Oct 22 02:46:44 maarten-acer2 systemd-modules-load[1949]: Failed to insert 'vboxdrv': Required key not available
Oct 22 02:46:44 maarten-acer2 systemd[1]: systemd-modules-load.service: main process exited, code=exited, status=1/FAILURE
Oct 22 02:46:44 maarten-acer2 systemd[1]: Failed to start Load Kernel Modules.
Oct 22 02:46:44 maarten-acer2 systemd[1]: Unit systemd-modules-load.service entered failed state.

Finally, it comes down to vboxdrv not being signed by Fedora's key!

# modprobe vboxdrv
modprobe: ERROR: could not insert 'vboxdrv': Required key not available

I think Virtual Box is packaged incorrectly. The kernel modules should have been signed by Fedora's keys.

This problem is closely related to my previous question.