Opened 4 years ago
Closed 4 years ago
#19723 closed defect (invalid)
VirtualBox 6.1.12 r139181 for Linux fails to install on Ubuntu 18.04.4 with mainline kernel 5.7.8-050708-generic
| Reported by: | Daniel Bonner | Owned by: | |
|---|---|---|---|
| Component: | installer | Version: | |
| Keywords: | VirtualBox 6.1.12 installer defect Ubuntu 18.04.4 mainline kernel 5.7.8-050708-generic | Cc: | |
| Guest type: | all | Host type: | Linux |
Description (last modified by )
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.
Change History (11)
comment:1 by , 4 years ago
| Status: | new → awaitsfeedback |
|---|
comment:2 by , 4 years ago
| Status: | awaitsfeedback → new |
|---|
comment:3 by , 4 years ago
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
comment:4 by , 4 years ago
| Description: | modified (diff) |
|---|
comment:5 by , 4 years ago
| Status: | new → awaitsfeedback |
|---|
what is the 'uname -r' output of your running kernel at the time you try to install (and compile) !Virtualbox?
Note, in the log file vbox-setup.log it tells you against which kernel version it is going to build:
$ cat /var/log/vbox-setup.log Building the main VirtualBox module. Error building the module: make V=1 CONFIG_MODULE_SIG= CONFIG_MODULE_SIG_ALL= -C /lib/modules/5.4.0-42-generic/build M=/tmp/vbox.0 SRCROOT=/tmp/vbox.0 -j4 modules
which is derived from:
$ uname -r 5.4.0-42-generic
comment:6 by , 4 years ago
Hit the same/very similar error on Mint19.3. The hack below fixed it:
root@fun:~# uname -r 5.4.0-45-generic root@fun:~# mv /lib/modules/5.4.55/misc /lib/modules/5.4.0-45-generic/
FYI:
root@fun:~# cat /var/log/vbox-setup.log Building the main VirtualBox module. Building the net filter module. Building the net adaptor module. root@fun:~#
comment:7 by , 4 years ago
The same story with Linux Mint 20.1 + VB Version 6.1.14r140239. The hack above didn't help. My version:
10:17:10 ✔ laptop:~$ uname -r 5.4.0-47-generic 10:17:15 ✔ laptop:~$ sudo mv /lib/modules/5.4.55/misc/ /lib/modules/5.4.55/misc_ORIG/ 10:17:18 ✔ laptop:~$ sudo ln -s /lib/modules/5.4.0-47-generic/misc/ /lib/modules/5.4.55/misc 10:17:42 ✔ laptop:~$ sudo rm /lib/modules/5.4.55/misc/* 10:17:49 ✔ laptop:~$ sudo /sbin/vboxconfig vboxdrv.sh: Stopping VirtualBox services. vboxdrv.sh: Starting VirtualBox services. vboxdrv.sh: Building VirtualBox kernel modules. 10:18:21 ✔ laptop:~$
comment:8 by , 4 years ago
check what the content of this header file is:
/usr/src/linux-headers-$(uname -r)/include/config/kernel.release
eg, for the above case of uname -r that would be:
# cat /usr/src/linux-headers-5.4.0-47-generic/include/config/kernel.release
it should contain: 5.4.0-47-generic
comment:9 by , 4 years ago
check what the content of this header file is...
The versions do not match (ignore new numbers, the kernel has been upgraded recently):
14:08:32 ✔ laptop:~$ uname -r 5.4.0-48-generic 14:08:34 ✔ laptop:~$ cat /usr/src/linux-headers-$(uname -r)/include/config/kernel.release 5.4.60 14:08:42 ✔ laptop:~$
The Linux headers are from Mint/Ubuntu:
14:11:10 ✔ laptop:~$ apt-cache policy linux-headers-5.4.0-48-generic linux-headers-5.4.0-48
linux-headers-5.4.0-48-generic:
Installed: 5.4.0-48.52
Candidate: 5.4.0-48.52
Version table:
*** 5.4.0-48.52 500
500 http://ubuntu.lagis.at/ubuntu focal-updates/main amd64 Packages
500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages
100 /var/lib/dpkg/status
linux-headers-5.4.0-48:
Installed: 5.4.0-48.52
Candidate: 5.4.0-48.52
Version table:
*** 5.4.0-48.52 500
500 http://ubuntu.lagis.at/ubuntu focal-updates/main amd64 Packages
500 http://ubuntu.lagis.at/ubuntu focal-updates/main i386 Packages
500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages
500 http://security.ubuntu.com/ubuntu focal-security/main i386 Packages
100 /var/lib/dpkg/status
14:11:26 ✔ laptop:~$
14:12:04 ✔ laptop:~$ apt-cache policy linux-image-5.4.0-48-generic
linux-image-5.4.0-48-generic:
Installed: 5.4.0-48.52
Candidate: 5.4.0-48.52
Version table:
*** 5.4.0-48.52 500
500 http://ubuntu.lagis.at/ubuntu focal-updates/main amd64 Packages
500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages
100 /var/lib/dpkg/status
14:12:14 ✔ laptop:~$
My symlinking workaround above has helped. The linux kernel and sorces are default one. Any hints whom to report missmatch in kernel.release?
comment:10 by , 4 years ago
I have run into a similar issue myself in the past on Ubuntu and the solution was to reinstall the kernel header package with apt, in your case linux-headers-5.4.0-48-generic
comment:11 by , 4 years ago
| Resolution: | → invalid |
|---|---|
| Status: | awaitsfeedback → closed |
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:
I can run VirtualBox. However, when I try to run a guest, I receive this message:
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:
I can fix this by issuing these commands:
After rebooting, VirtualBox and guests run properly.