[Solved 5.2.6] VBox on Fedora 27

Discussions related to using VirtualBox on Linux hosts.
Lizzie
Posts: 50
Joined: 24. Oct 2015, 20:50

[Solved 5.2.6] VBox on Fedora 27

Post by Lizzie »

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.
So I then ran the following:

Code: Select all

[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].
socratis
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: VBox on Fedora 27

Post by socratis »

Disable secure boot.
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.
Lizzie
Posts: 50
Joined: 24. Oct 2015, 20:50

Re: VBox on Fedora 27

Post by Lizzie »

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.

Lizzie
socratis
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: VBox on Fedora 27

Post by socratis »

Lizzie wrote:Secure boot is turned off.
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.
Lizzie
Posts: 50
Joined: 24. Oct 2015, 20:50

Re: VBox on Fedora 27

Post by Lizzie »

The only thing I know to set is the KERN_DIR. I do not know what KERN_VER is set to or how/what it should be set to.

For KERN_DIR it is set to /usr/src/kernels/4.13.16-300.fc27.x86_64

Lizzie
socratis
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: VBox on Fedora 27

Post by socratis »

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.
Perryg
Site Moderator
Posts: 34369
Joined: 6. Sep 2008, 22:55
Primary OS: Linux other
VBox Version: OSE self-compiled
Guest OSses: *NIX

Re: VBox on Fedora 27

Post by Perryg »

Are the matching headers for the running kernel installed?
Lizzie
Posts: 50
Joined: 24. Oct 2015, 20:50

Re: VBox on Fedora 27

Post by Lizzie »

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
socratis
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: VBox on Fedora 27

Post by socratis »

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.
Lizzie
Posts: 50
Joined: 24. Oct 2015, 20:50

Re: VBox on Fedora 27

Post by Lizzie »

Checked and double checked. It is turned off.
socratis
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: VBox on Fedora 27

Post by socratis »

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.
Lizzie
Posts: 50
Joined: 24. Oct 2015, 20:50

Re: VBox on Fedora 27 (Resolved)

Post by Lizzie »

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.

Thanks to everyone who attempted to assist.

Lizzie
thommym
Posts: 9
Joined: 8. Aug 2010, 12:45
Primary OS: OpenSolaris 11
VBox Version: OSE other
Guest OSses: Many

Re: VBox on Fedora 27

Post by thommym »

I experience the same problem after upgrading from fc26 to fc27 today. Then I did a rebbot again and then an upgrade and everything is fine.
$ sudo dnf upgrade --refresh
[sudo] password for xxxxxxxxxxxxxxxx: 
Fedora 27 - x86_64 - VirtualBox                                                                                                                     583 kB/s |  25 kB     00:00    
Last metadata expiration check: 0:00:00 ago on Tue 19 Dec 2017 04:55:43 PM CET.
Dependencies resolved.

 Problem: package mariadb-connector-c-3.0.2-15.fc27.x86_64 requires mariadb-libs, but none of the providers can be installed
  - installed package mysql-community-libs-compat-5.7.20-1.fc26.x86_64 obsoletes mariadb-libs provided by mariadb-libs-3:10.2.9-3.fc27.i686
  - installed package mysql-community-libs-compat-5.7.20-1.fc26.x86_64 obsoletes mariadb-libs provided by mariadb-libs-3:10.2.9-3.fc27.x86_64
  - cannot install the best update candidate for package mariadb-connector-c-3.0.2-4.fc27.x86_64
  - problem with installed package mysql-community-libs-compat-5.7.20-1.fc26.x86_64
====================================================================================================================================================================================
 Package                                        Arch                              Version                                               Repository                             Size
====================================================================================================================================================================================
Upgrading:
 VirtualBox-5.2                                 x86_64                            5.2.4_119785_fedora26-1                               virtualbox                             69 M
Skipping packages with broken dependencies:
 mariadb-connector-c                            x86_64                            3.0.2-15.fc27                                         updates                               9.8 k

Transaction Summary
====================================================================================================================================================================================
Upgrade  1 Package
Skip     1 Package

Total download size: 69 M
Is this ok [y/N]: y
Downloading Packages:
VirtualBox-5.2-5.2.4_119785_fedora26-1.x86_64.rpm                                                                                                    13 MB/s |  69 MB     00:05    
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Total                                                                                                                                                13 MB/s |  69 MB     00:05     
Running transaction check
Transaction check succeeded.
Running transaction test
Transaction test succeeded.
Running transaction
  Preparing        :                                                                                                                                                            1/1 
  Running scriptlet: VirtualBox-5.2-5.2.4_119785_fedora26-1.x86_64                                                                                                              1/2 
  Upgrading        : VirtualBox-5.2-5.2.4_119785_fedora26-1.x86_64                                                                                                              1/2 
  Running scriptlet: VirtualBox-5.2-5.2.4_119785_fedora26-1.x86_64                                                                                                              1/2 

Creating group 'vboxusers'. VM users must be member of that group!

  Running scriptlet: VirtualBox-5.2-5.2.2_119230_fedora26-1.x86_64                      2/2 
  Cleanup          : VirtualBox-5.2-5.2.2_119230_fedora26-1.x86_64                      2/2 
  Running scriptlet: VirtualBox-5.2-5.2.2_119230_fedora26-1.x86_64                      2/2 
  Running scriptlet: VirtualBox-5.2-5.2.2_119230_fedora26-1.x86_64                      2/2 
  Verifying        : VirtualBox-5.2-5.2.4_119785_fedora26-1.x86_64                      1/2 
  Verifying        : VirtualBox-5.2-5.2.2_119230_fedora26-1.x86_64                      2/2 

Upgraded:
  VirtualBox-5.2.x86_64 5.2.4_119785_fedora26-1                                            

Complete!
Last edited by socratis on 20. Dec 2017, 09:56, edited 1 time in total.
Reason: Enclosed the information in [pre] tag for better readability
piters
Posts: 5
Joined: 8. Jan 2018, 11:25

Re: VBox on Fedora 27

Post by piters »

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.

I did

Code: Select all

dnf install elfutils-libelf-devel.x86_64
and then

Code: Select all

/sbin/vboxconfig
and it worked...
Lizzie
Posts: 50
Joined: 24. Oct 2015, 20:50

Re: VBox on Fedora 27

Post by Lizzie »

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

Code: Select all

 /usr/lib/virtualbox/vboxdrv.sh setup
vboxdrv.sh: Stopping VirtualBox services.
vboxdrv.sh: failed: Cannot unload module vboxnetflt.
from the log

Code: Select all

# 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
Post Reply