Fedora 26, VBox 5.1.22 r115126 (Qt5.7.1) - vboxdrv.sh: failed
-
- Posts: 5
- Joined: 20. Jul 2017, 14:14
- Primary OS: Fedora other
- VBox Version: OSE Fedora
- Guest OSses: Windows 10
- Location: Czech Republic
Fedora 26, VBox 5.1.22 r115126 (Qt5.7.1) - vboxdrv.sh: failed
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
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
-
- Posts: 5
- Joined: 20. Jul 2017, 14:14
- Primary OS: Fedora other
- VBox Version: OSE Fedora
- Guest OSses: Windows 10
- Location: Czech Republic
Re: Fedora 26, VBox 5.1.22 r115126 (Qt5.7.1) - vboxdrv.sh: failed
Sorry, version VBox is 5.1.24 r117012
-
- Site Moderator
- Posts: 27330
- Joined: 22. Oct 2010, 11:03
- Primary OS: Mac OS X other
- VBox Version: PUEL
- Guest OSses: Win(*>98), Linux*, OSX>10.5
- Location: Greece
Re: Fedora 26, VBox 5.1.22 r115126 (Qt5.7.1) - vboxdrv.sh: failed
Have you tried downloading VirtualBox directly from the website, instead of going through all the hoops? https://www.virtualbox.org/wiki/Linux_Downloads
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
-
- Posts: 5
- Joined: 20. Jul 2017, 14:14
- Primary OS: Fedora other
- VBox Version: OSE Fedora
- Guest OSses: Windows 10
- Location: Czech Republic
Re: Fedora 26, VBox 5.1.22 r115126 (Qt5.7.1) - vboxdrv.sh: failed
Thank you, I tried it now, but the result is the same
-
- Posts: 5
- Joined: 20. Jul 2017, 14:14
- Primary OS: Fedora other
- VBox Version: OSE Fedora
- Guest OSses: Windows 10
- Location: Czech Republic
Re: Fedora 26, VBox 5.1.22 r115126 (Qt5.7.1) - vboxdrv.sh: failed
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)
-
- Posts: 2
- Joined: 21. Jul 2017, 20:02
- Primary OS: Fedora other
- VBox Version: PUEL
- Guest OSses: Windows 10
- Location: Saratoga Springs, NY, USA
Re: Fedora 26, VBox 5.1.22 r115126 (Qt5.7.1) - vboxdrv.sh: failed
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.
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.
-
- Site Moderator
- Posts: 27330
- Joined: 22. Oct 2010, 11:03
- Primary OS: Mac OS X other
- VBox Version: PUEL
- Guest OSses: Win(*>98), Linux*, OSX>10.5
- Location: Greece
Re: Fedora 26, VBox 5.1.22 r115126 (Qt5.7.1) - vboxdrv.sh: failed
A more detailed error message would definitely help those that could help you...stpeters00 wrote:complaining about some module version mismatch
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
-
- Posts: 2
- Joined: 21. Jul 2017, 20:02
- Primary OS: Fedora other
- VBox Version: PUEL
- Guest OSses: Windows 10
- Location: Saratoga Springs, NY, USA
Re: Fedora 26, VBox 5.1.22 r115126 (Qt5.7.1) - vboxdrv.sh: failed
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.
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.
-
- Site Moderator
- Posts: 27330
- Joined: 22. Oct 2010, 11:03
- Primary OS: Mac OS X other
- VBox Version: PUEL
- Guest OSses: Win(*>98), Linux*, OSX>10.5
- Location: Greece
Re: Fedora 26, VBox 5.1.22 r115126 (Qt5.7.1) - vboxdrv.sh: failed
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.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.
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
-
- Posts: 5
- Joined: 20. Jul 2017, 14:14
- Primary OS: Fedora other
- VBox Version: OSE Fedora
- Guest OSses: Windows 10
- Location: Czech Republic
Re: Fedora 26, VBox 5.1.22 r115126 (Qt5.7.1) - vboxdrv.sh: failed
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
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
-
- Site Moderator
- Posts: 27330
- Joined: 22. Oct 2010, 11:03
- Primary OS: Mac OS X other
- VBox Version: PUEL
- Guest OSses: Win(*>98), Linux*, OSX>10.5
- Location: Greece
Re: Fedora 26, VBox 5.1.22 r115126 (Qt5.7.1) - vboxdrv.sh: failed
Thank you for the feedback!pumart wrote:Thank you for your cooperation
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.