virtualbox.org

Hello, I have Fedora 26 KDE spin 64bit fresh install, I ran the following commands:

1 su
2 dnf update and reboot to kernel 4.11.10-300.fc26.x86_64
3 cd /etc/yum.repos.d/
4 install virtualbox.repo
5 dnf update
6 dnf install binutils gcc make patch libgomp glibc-headers glibc-devel kernel-headers kernel-devel dkms
7 dnf install VirtualBox-5.1

and virtualbox failed for /sbin/vboxconfig:

vboxdrv.sh: Stopping VirtualBox services.
vboxdrv.sh: Building VirtualBox kernel modules.
vboxdrv.sh: Starting VirtualBox services.
vboxdrv.sh: Building VirtualBox kernel modules.
vboxdrv.sh: failed: modprobe vboxdrv failed. Please use 'dmesg' to find out why.

Command dmesg does not show anything

Why the vboxdrv.sh does Stopping, Building, Starting and Building again?

You have an idea?
Thank you
Pumart

Sorry, version VBox is 5.1.24 r117012

Have you tried downloading VirtualBox directly from the website, instead of going through all the hoops? https://www.virtualbox.org/wiki/Linux_Downloads

Thank you, I tried it now, but the result is the same

The RPM files in the repository and on the above address are the same (VirtualBox-5.1-5.1.24_117012_fedora25-1.x86_64.rpm)

The RPM files are not only identical, something about them is broken.

When my Fedora box ran F25 and VB 5.1.22, I tried to upgrade VB to 5.1.24. The new VB would not run, complaining about some module version mismatch. After struggling with this for hours with no success, I finally did "dnf downgrade VirtualBox-5.1" and got a working 5.1.22 back.

I have since upgraded the box to F26, adding "--exclude=VirtualBox-5.1" to the system-upgrade dnf command. This got me a working F26 and VB 5.1.22 combination.

stpeters00 wrote:complaining about some module version mismatch

A more detailed error message would definitely help those that could help you...

Yes, and if I'm ever seeking help I'll post as much detail as I can. For now, 5.1.22 works well enough for what little I use VB for. The intent of my post was to add my voice to the chorus of posts saying the fix for 5.1.24 problems is to downgrade.

Maybe someday I will need something beyond 5.1.22 ... but my computing life began in 1964, and after more than half a century the thrill is gone. I no longer climb upgrade mountains just because the mountain is there.

stpeters00 wrote:The intent of my post was to add my voice to the chorus of posts saying the fix for 5.1.24 problems is to downgrade.

I'm sorry, but that's not a solution, by any stretch of the imagination. That's a temporary workaround at best. You're looking at it backwards. I'll add you to the "me too", and the "couldn't care less" columns for now. And BTW "chorus" means definitely more than a handful of people, and at the moment it's not even that.

I found the problem. Command "modprobe vboxdrv" writes "Required key not available"

Solution:

Since kernel version ?? the EFI_SECURE_BOOT_SIG_ENFORCE kernel config has been enabled. That prevents from loading unsigned third party modules if UEFI Secure Boot is enabled.

The easiest way to fix this issue is to disable Secure Boot in UEFI (BIOS) settings. You can find another solutions using Google

Thank you for your cooperation

Pumart

pumart wrote:Thank you for your cooperation

Thank you for the feedback!