Ask Your Question
0

I can't run VirtualBox at all.

asked 2017-05-06 12:01:16 -0500

ronok gravatar image

dnf install akmod-VirtualBox kernel-devel-4.8.6-300.fc25.x8664 akmods --kernels 4.8.6-300.fc25.x8664 && systemctl restart systemd-modules-load.service

You will not be able to start VMs until this problem is fixed. Qt WARNING: libpng warning: iCCP: known incorrect sRGB profile

[root@Raiju Raiju]# virtualbox WARNING: The vboxdrv kernel module is not loaded. Either there is no module available for the current kernel (4.8.6-300.fc25.x86_64) or it failed to load. Please try load the kernel module by executing as root

       dnf install akmod-VirtualBox kernel-devel-4.8.6-300.fc25.x86_64
       akmods --kernels 4.8.6-300.fc25.x86_64 && systemctl restart systemd-modules-load.service

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

No protocol specified Qt FATAL: QXcbConnection: Could not connect to display :0 Aborted (core dumped) [root@Raiju Raiju]# dnf install akmod-VirtualBox kernel-devel-4.8.6-300.fc25.x8664 Warning: failed loading '/etc/yum.repos.d/fedora-spotify.repo', skipping. Last metadata expiration check: 0:31:03 ago on Sat May 6 09:10:37 2017. Package akmod-VirtualBox-5.1.20-1.fc25.x8664 is already installed, skipping. Package kernel-devel-4.8.6-300.fc25.x8664 is already installed, skipping. Dependencies resolved. Nothing to do. Complete! [root@Raiju Raiju]# akmods --kernels 4.8.6-300.fc25.x8664 && systemctl restart systemd-modules-load.service Checking kmods exist for 4.8.6-300.fc25.x8664 [ OK ] Job for systemd-modules-load.service failed because the control process exited with error code. See "systemctl status systemd-modules-load.service" and "journalctl -xe" for details. [root@Raiju Raiju]# akmods --kernels 4.8.6-300.fc25.x8664 && systemctl restart systemd-modules-load.service Checking kmods exist for 4.8.6-300.fc25.x86_64 [ OK ] Job for systemd-modules-load.service failed because the control process exited with error code. See "systemctl status systemd-modules-load.service" and "journalctl -xe" for details. [root@Raiju Raiju]# 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 Sat 2017-05-06 09:41:58 PDT; 12s ago Docs: man:systemd-modules-load.service(8) man:modules-load.d(5) Process: 14941 ExecStart=/usr/lib/systemd/systemd-modules-load (code=exited, s Main PID: 14941 (code=exited, status=1/FAILURE)

May 06 09:41:58 Raiju systemd[1]: Starting Load Kernel Modules... May 06 09:41:58 Raiju systemd-modules-load[14941]: Failed to insert 'vboxdrv': R May 06 09:41:58 Raiju systemd-modules-load[14941]: Failed to insert 'vboxnetflt' May 06 09:41:58 Raiju systemd[1]: systemd-modules-load.service: Main process exi May 06 09:41:58 Raiju systemd[1]: Failed to start Load Kernel Modules. May 06 09:41:58 Raiju systemd[1]: systemd-modules-load.service: Unit entered fai May 06 09:41:58 Raiju systemd[1]: systemd-modules-load.service: Failed with resu [root@Raiju Raiju]# journalctl -xe May 06 09:41:58 Raiju systemd[1]: Starting Load Kernel Modules... -- Subject: Unit systemd-modules-load.service has begun start-up -- Defined-By: systemd

-- Support: http://lists.freedesktop.org/mailman/...

-- Unit systemd-modules-load.service has begun starting up. May 06 09:41:58 Raiju systemd-modules-load[14941]: Failed to insert 'vboxdrv': R May 06 ... (more)

edit retag flag offensive close merge delete

Comments

1

Do you have "Secure Boot" enabled in BIOS? If yes, this prevents the VirtualBox kernel module from being loaded, so disabling "Secure Boot" should help.

Axel Sommerfeldt gravatar imageAxel Sommerfeldt ( 2017-05-07 05:12:02 -0500 )edit

Use KVM and virt manager instead of VirtualBox it will save you all this issues and accomplish the same thing. Other wise follow @axel-sommerfeldt advise, beware that next kernel update you may need to recompile VirtualBox kernel module

aeperezt gravatar imageaeperezt ( 2017-05-07 12:05:01 -0500 )edit

1 Answer

Sort by » oldest newest most voted
2

answered 2017-05-08 02:45:44 -0500

andybe gravatar image

You need to run the current version VBOX 5.1. KVM & VBOX can not run together because of vmx extension.

edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Question Tools

Stats

Asked: 2017-05-06 12:01:16 -0500

Seen: 703 times

Last updated: May 06 '17