Attempting to get VirtualBox 5.2.2 r119230 from the website running on Fedora 27. I get the following error message when I attempt to start the program:
Kernel driver not installed (rc=-1908)
The VirtualBox Linux kernel driver (vboxdrv) is either not loaded or there is a permission problem with /dev/vboxdrv. Please reinstall the kernel module by executing
'/sbin/vboxconfig'
as root.
where: suplibOsInit what: 3 VERR_VM_DRIVER_NOT_INSTALLED (-1908) - The support driver is not installed. On linux, open returned ENOENT.
[root@lizzie Lizzie]# cd /usr/src/kernels
[root@lizzie kernels]# ls
4.13.13-300.fc27.x86_64 4.13.15-300.fc27.x86_64 4.13.16-300.fc27.x86_64
[root@lizzie kernels]# export KERN_DIR=/usr/src/kernels/4.13.16-300.fc27.x86_64
[root@lizzie kernels]# /usr/lib/virtualbox/vboxdrv.sh setup
With the following error message:
vboxdrv.sh: Stopping VirtualBox services.
vboxdrv.sh: Building VirtualBox kernel modules.
vboxdrv.sh: failed: Look at /var/log/vbox-install.log to find out what went wrong.
With the following message in the log file:
tail /var/log/vbox-install.log
/bin/false)
mkdir -p /lib/modules/4.13.16-300.fc27.x86_64/misc
make -f ./scripts/Makefile.modinst
mkdir -p /lib/modules/4.13.16-300.fc27.x86_64/misc ;
cp /tmp/vbox.0/vboxpci.ko /lib/modules/4.13.16-300.fc27.x86_64/misc ;
true /lib/modules/4.13.16-300.fc27.x86_64/misc/vboxpci.ko ;
scripts/sign-file "sha256" "certs/signing_key.pem" certs/signing_key.x509 /lib/modules/4.13.16-300.fc27.x86_64/misc/vboxpci.ko || true && true /lib/modules/4.13.16-300.fc27.x86_64/misc/vboxpci.ko
At main.c:160:
- SSL error:02001002:system library:fopen:No such file or directory: crypto/bio/bss_file.c:74
- SSL error:2006D080:BIO routines:BIO_new_file:no such file: crypto/bio/bss_file.c:81
sign-file: certs/signing_key.pem: No such file or directory
/bin/sh ./scripts/depmod.sh /sbin/depmod 4.13.16-300.fc27.x86_64 ""
/tmp/vbox.0/Makefile.include.header:99: *** The variable KERN_DIR must be a kernel build folder and end with /build without a trailing slash, or KERN_VER must be set. Stop.
Any suggestions as to what I need to do to resolve this problem?
Lizzie
Last edited by socratis on 17. Jan 2018, 13:21, edited 1 time in total.
Reason:Marked as [Solved].
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.
Secure boot is turned off. I have been running virtualbox successfully since Fedora 24. I can not seem to get it running with the latest update to Fedora 27.
Hmm... That's funny, because all the errors point to "crypto" and "signing" and "x509". What about the message about the KERN_DIR variable? Is that set? If yes, what is it?
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.
I'm afraid that this is where my "in depth" Linux knowledge ends (it didn't even start to begin with).
I think I'm going to let a more knowledgeable Linux person help you out with this if they can...
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.
Yes. kernel-core, kernel-devel, kernel-headers, kernel modules, kernel-modules-extra, kernel-tools, kernel-tools-libs, kernel-tools-libs-devel for version 4.13.16 are all installed
Sorry if I repeat myself, but did you make absolutely sure that secure boot is disabled in Fedora 27? It may have worked in Fedora 24, but the defaults might have changed. Please check one more time, just as a favor...
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.
OK, thanks for verifying that. I see that you posted the same question in the Fedora forums. Smart move
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.
For whatever reason, VBox started working this morning. On a whim, I decided to try and start it and it started right up. No idea what was wrong or what was done to fix it. My assumption is that it was not anything going on on my system but who knows.
Not sure if this helps, but on my machine (after today's upgrade) I got a similar error, and this one was not actually a problem - the problem was pointed by a few lines below and complained about missing lbelf-devel.
The desktop computer that I first wrote about is still up and running vbox as it should.
I am now attempting to get it running on my laptop. Same version of vbox on the same OS. Kernel has been updated to 4.14.13-300.fc27.x86_64. I am receiving the following error
# tail /var/log/vbox-install.log
/bin/false)
mkdir -p /lib/modules/4.14.13-300.fc27.x86_64/misc
make -f ./scripts/Makefile.modinst
mkdir -p /lib/modules/4.14.13-300.fc27.x86_64/misc ; cp /tmp/vbox.0/vboxnetflt.ko /lib/modules/4.14.13-300.fc27.x86_64/misc ; true /lib/modules/4.14.13-300.fc27.x86_64/misc/vboxnetflt.ko ; scripts/sign-file "sha256" "certs/signing_key.pem" certs/signing_key.x509 /lib/modules/4.14.13-300.fc27.x86_64/misc/vboxnetflt.ko || true && true /lib/modules/4.14.13-300.fc27.x86_64/misc/vboxnetflt.ko
At main.c:160:
- SSL error:02001002:system library:fopen:No such file or directory: crypto/bio/bss_file.c:74
- SSL error:2006D080:BIO routines:BIO_new_file:no such file: crypto/bio/bss_file.c:81
sign-file: certs/signing_key.pem: No such file or directory
/bin/sh ./scripts/depmod.sh /sbin/depmod 4.14.13-300.fc27.x86_64 ""
/tmp/vbox.0/Makefile.include.header:99: *** The variable KERN_DIR must be a kernel build folder and end with /build without a trailing slash, or KERN_VER must be set. Stop.
I tried the things listed above that worked for others with no improvement, Any suggestions would be appreciated.
Lizzie
Last edited by socratis on 13. Jan 2018, 09:21, edited 1 time in total.
Reason:Enclosed the information in [code] tag for better readability