VirtualBox 6.1.12 r139181 for Linux fails to install on Ubuntu 18.04.4 with mainline kernel 5.7.8-050708-generic

[Daniel Bonner]

Hi, I'm using Ubuntu 18.04.4 and mainline kernel 5.7.8-050708-generic (installed with UKUU)

When installing Virtualbox: sudo ./VirtualBox-6.1.12-139181-Linux_amd64.run

I get the following errors:

At main.c:281:
- SSL error:02001002:system library:fopen:No such file or directory: ../crypto/bio/bss_file.c:72
- SSL error:2006D080:BIO routines:BIO_new_file:no such file: ../crypto/bio/bss_file.c:79
kmodsign: /lib/modules/5.7.8-050708-generic/misc/vboxdrv.ko: No such file or directory
At main.c:281:
- SSL error:02001002:system library:fopen:No such file or directory: ../crypto/bio/bss_file.c:72
- SSL error:2006D080:BIO routines:BIO_new_file:no such file: ../crypto/bio/bss_file.c:79
kmodsign: /lib/modules/5.7.8-050708-generic/misc/vboxnetflt.ko: No such file or directory
At main.c:281:
- SSL error:02001002:system library:fopen:No such file or directory: ../crypto/bio/bss_file.c:72
- SSL error:2006D080:BIO routines:BIO_new_file:no such file: ../crypto/bio/bss_file.c:79
kmodsign: /lib/modules/5.7.8-050708-generic/misc/vboxnetadp.ko: No such file or directory
vboxdrv.sh: failed: modprobe vboxdrv failed.

I can run VirtualBox. However, when I try to run a guest, I receive this message:

Kernel driver not installed (rc=-1908)
The VirtualBox Linux kernel driver is either not loaded or not set up correctly.
where: suplibOsInit what: 3 VERR_VM_DRIVER_NOT_INSTALLED (-1908) - The support driver is not installed. On linux, open returned ENOENT.

sudo /sbin/vboxconfig fails and gives the same output to the terminal as the installer.

There are no errors in /var/log/vbox-install.log and no errors in /var/log/vbox-setup.log.

The kernel modules do not work because they are installed in the wrong directory. The installer puts them in:

/lib/modules/5.7.8/misc     (which is incorrect)
The installer also puts the follow 0 byte files which do not work in /lib/modules/5.7.8-050708-generic/misc/ (which is the correct directory for the modules):
-rw-r--r-- 1 root      0 Jul 15 20:02 vboxdrv.ko.~signed~
-rw-r--r-- 1 root      0 Jul 15 20:02 vboxnetadp.ko.~signed~
-rw-r--r-- 1 root      0 Jul 15 20:02 vboxnetflt.ko.~signed~

I can fix this by issuing these commands:

sudo rm /lib/modules/5.7.8-050708-generic/misc/vboxnetflt.ko.~signed~
sudo rm /lib/modules/5.7.8-050708-generic/misc/vboxnetadp.ko.~signed~
sudo rm /lib/modules/5.7.8-050708-generic/misc/vboxdrv.ko.~signed~ 
sudo mv /lib/modules/5.7.8/misc/* /lib/modules/5.7.8-050708-generic/misc/
sudo rm -rf /lib/modules/5.7.8

Then I reboot.

Then VirtualBox and guests run properly.

[Daniel Bonner]

The line breaks did not come out in the last half of the ticket. Here is a better formatted version:

When installing Virtualbox using:
sudo ./VirtualBox-6.1.12-139181-Linux_amd64.run
I get the following errors:

At main.c:281:
SSL error:02001002:system library:fopen:No such file or directory:
../crypto/bio/bss_file.c:72
SSL error:2006D080:BIO routines:BIO_new_file:no such file:
../crypto/bio/bss_file.c:79
kmodsign: /lib/modules/5.7.8-050708-generic/misc/vboxdrv.ko:
No such file or directory
At main.c:281:
SSL error:02001002:system library:fopen:No such file or directory:
../crypto/bio/bss_file.c:72
SSL error:2006D080:BIO routines:BIO_new_file:no such file:
../crypto/bio/bss_file.c:79
kmodsign: /lib/modules/5.7.8-050708-generic/misc/vboxnetflt.ko:
No such file or directory At main.c:281:
SSL error:02001002:system library:fopen:No such file or directory:
../crypto/bio/bss_file.c:72
SSL error:2006D080:BIO routines:BIO_new_file:no such file:
../crypto/bio/bss_file.c:79
kmodsign: /lib/modules/5.7.8-050708-generic/misc/vboxnetadp.ko:
No such file or directory
vboxdrv.sh: failed: modprobe vboxdrv failed.

I can run VirtualBox. However, when I try to run a guest, I receive this message:

Kernel driver not installed (rc=-1908)
The VirtualBox Linux kernel driver is either not loaded or not set up correctly.
where: suplibOsInit what: 3 VERR_VM_DRIVER_NOT_INSTALLED (-1908) -
The support driver is not installed. On linux, open returned ENOENT.

sudo /sbin/vboxconfig fails and gives the same output to the terminal as the installer.

There are no errors in /var/log/vbox-install.log and no errors in /var/log/vbox-setup.log.

The kernel modules do not work because they are installed in the wrong directory.

The installer puts them in:

/lib/modules/5.7.8/misc     ('5.7.8' is not the correct directory for the modules)

The installer also puts the follow faulty 0 byte files which do not work in:

/lib/modules/5.7.8-050708-generic/misc/   (the correct directory for the modules):
-rw-r--r-- 1 root 0 Jul 15 20:02 vboxdrv.ko.~signed~ [[br]]
-rw-r--r-- 1 root 0 Jul 15 20:02 vboxnetadp.ko.~signed~ [[br]]
-rw-r--r-- 1 root 0 Jul 15 20:02 vboxnetflt.ko.~signed~ [[br]]

I can fix this by issuing these commands:

sudo rm /lib/modules/5.7.8-050708-generic/misc/vboxnetflt.ko.~signed~ [[br]]
sudo rm /lib/modules/5.7.8-050708-generic/misc/vboxnetadp.ko.~signed~ [[br]]
sudo rm /lib/modules/5.7.8-050708-generic/misc/vboxdrv.ko.~signed~ [[br]]
sudo mv /lib/modules/5.7.8/misc/* /lib/modules/5.7.8-050708-generic/misc/ [[br]]
sudo rm -rf /lib/modules/5.7.8 [[br]]
Then I reboot.

After rebooting, VirtualBox and guests run properly.

[Daniel Bonner]

Hi, I had this problem with my laptop.
I was able to install VirtualBox on my desktop (which has the same Ubuntu 18.04.4 and the same mainline kernel) without getting these errors. So this problem does not always happen.
Cheers,
Daniel