VirtualBox 6.1.28 / 6.1.29 on Fedora 35/34/33, CentOS/RHEL 8/7 - Comment Page: 17
Oracle VirtualBox is a powerful x86 and AMD64/Intel64 virtualization product for enterprise as well as home use. VirtualBox is a general-purpose full virtualizer for x86 hardware. Targeted at server, desktop and embedded use, it is now the only professional-quality virtualization solution that is also Open Source Software.
Check video guide howto install VirtualBox 6.1.28/6.1.29 on Fedora 35/34/33 using .run installer:
Check video guide howto install VirtualBox 6.1.28 on Fedora 34/33 using Oracle's own dnf repo:
Watch More Videos and Subscribe to if-not-true-then-false.com Youtube Channel
VirtualBox supports a large number of guest operating...
tq!! for your help!!
For rebuilding the kernel on Centos7 I had to run:
/usr/lib/virtualbox/vboxdrv.sh setup
3.10.0-229.14.1.el7.x86_64 #1 SMP Tue Sep 15 15:05:51 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
For some reason the service didn’t accept the “setup” parameter.
Cheers.
HI Ariel,
If you are using dkms, you shouldn’t need to rebuild it manually.
I just tested rebuild it on CentOS 7 using /usr/lib/virtualbox/vboxdrv.sh setup and it’s working normally.
Setup parameter should be fine. Do you get some error when you try to run /usr/lib/virtualbox/vboxdrv.sh setup?
Hi JR,
Not really a problem, it’s just that the location has change for Centos7 and Fedora (I think since F20)… When you try to run:
/etc/init.d/vboxdrv setup
## OR ##
service vboxdrv setup
[[email protected] Downloads]# service vboxdrv setup
The service command supports only basic LSB actions (start, stop, restart, try-restart, reload, force-reload, status). For other actions, please try to use systemctl.
[[email protected] Downloads]# /etc/init.d/vboxdrv setup
bash: /etc/init.d/vboxdrv: No such file or directory
– then you have to go to:
[[email protected] Downloads]# /usr/lib/virtualbox/vboxdrv.sh setup
Stopping VirtualBox kernel modules [ OK ]
Uninstalling old VirtualBox DKMS kernel modules [ OK ]
Trying to register the VirtualBox kernel modules using DKMS[ OK ]
Starting VirtualBox kernel modules [ OK ]
and everything looks just fine.
Cheers!
Excellent! I just added this to step 5.
hi i get an error when executing the setup script:
[code]
[[email protected] ~]# /usr/lib/virtualbox/vboxdrv.sh setup
Stopping VirtualBox kernel modules [ OK ]
Uninstalling old VirtualBox DKMS kernel modules [ OK ]
Trying to register the VirtualBox kernel modules using DKMSError! echo
Your kernel headers for kernel 4.2.0-0.rc5.git0.2.fc23.x86_64 cannot be found at
/lib/modules/4.2.0-0.rc5.git0.2.fc23.x86_64/build or /lib/modules/4.2.0-0.rc5.git0.2.fc23.x86_64/source.
[FEHLGESCHLAGEN]
(Failed, trying without DKMS)
Recompiling VirtualBox kernel modules [FEHLGESCHLAGEN]
(Look at /var/log/vbox-install.log to find out what went wrong)
[/code]
when looking up kernel version with ‘uname -r’ i get this response:
[code]
4.2.0-0.rc5.git0.2.fc23.x86_64
[/code]
how to post source here?
when executing rpm -qa kernel |sort -V |tail -n 1 i get ‘kernel-4.2.3-300.fc23.x86_64’
so this might be the problem, but how to solve ist?
Hi major_tom,
Just reboot and select kernel-4.2.3-300.fc23.x86_64.
i unfortunatly have no kernel options in grub (dualboot with ubuntu) – so i will first need to find out how to set up grub for that…
After switching the boot drive at the bios i was able to enter the fedora grub menu and boot the newer kernel.
then
# /usr/lib/virtualbox/vboxdrv.sh setup Stopping VirtualBox kernel modules [ OK ] Uninstalling old VirtualBox DKMS kernel modules [ OK ] Trying to register the VirtualBox kernel modules using DKMSError! echo Your kernel headers for kernel 4.2.3-300.fc23.x86_64 cannot be found at /lib/modules/4.2.3-300.fc23.x86_64/build or /lib/modules/4.2.3-300.fc23.x86_64/source. [FEHLGESCHLAGEN] (Failed, trying without DKMS) Recompiling VirtualBox kernel modules [FEHLGESCHLAGEN] (Look at /var/log/vbox-install.log to find out what went wrong)the file ‘/lib/modules/4.2.3-300.fc23.x86_64/build’ was missing so i had to install ‘kernel-devel-4.2.3-300.fc23.x86_64’,
the ‘kernel-devel’ package i installed before was for the old kernel?
after that ‘/usr/lib/virtualbox/vboxdrv.sh setup’ worked.
thanks for your help!
Worked perfectly on Fedora 23, thanks!
Unfortunately, the Oracle repo for 6.7 appears to
be missing; this all worked up until I updated from
SL 6.6 to SL 6.7.
Hi bit twiddler,
Could you post output of following command:
Most certainly!
As root, with virtualbox repo enabled:
Loaded plugins: fastestmirror, presto, priorities, refresh-packagekit
{‘arch’: ‘ia32e’,
‘basearch’: ‘x86_64’,
‘releasever’: ‘6.7’,
‘uuid’: ‘500c414d-d981-436e-ad17-5e518d040499’}
and the repo itself is:
[virtualbox]
name=Oracle Linux / RHEL / CentOS-$releasever / $basearch – VirtualBox
baseurl=http://download.virtualbox.org/virtualbox/rpm/el/$releasever/$basearch
enabled=1
priority=15
gpgcheck=1
gpgkey=https://www.virtualbox.org/download/oracle_vbox.asc
and, the end result:
[[email protected] yum.repos.d]$ yum repolist
Loaded plugins: fastestmirror, presto, priorities, refresh-packagekit, security
Loading mirror speeds from cached hostfile
epel/metalink | 12 kB 00:00
* epel: mirror.sfo12.us.leaseweb.net
* sl: ftp2.scientificlinux.org
* sl-security: ftp2.scientificlinux.org
* sl6x: ftp2.scientificlinux.org
* sl6x-security: ftp2.scientificlinux.org
adobe-linux-i386 | 951 B 00:00
adobe-linux-x86_64 | 951 B 00:00
epel | 4.3 kB 00:00
epel/primary_db | 5.7 MB 00:52
google-chrome | 951 B 00:00
linuxtech | 2.6 kB 00:00
pgdg94 | 3.7 kB 00:00
sl | 3.7 kB 00:00
sl-security | 2.9 kB 00:00
sl6x | 3.7 kB 00:00
sl6x-security | 2.9 kB 00:00
http://download.virtualbox.org/virtualbox/rpm/el/6.7/x86_64/repodata/repomd.xml: [Errno 14] PYCURL ERROR 22 – “The requested URL returned error: 404 Not Found”
Trying other mirror.
http://download.virtualbox.org/virtualbox/rpm/el/6.7/x86_64/repodata/repomd.xml: [Errno 14] PYCURL ERROR 22 – “The requested URL returned error: 404 Not Found”
Trying other mirror.
repo id repo name status
adobe-linux-i386 Adobe Systems Incorporated 2
adobe-linux-x86_64 Adobe Systems Incorporated 2
*epel Extra Packages for Enterprise Linux 6 – x86_64 11,866
google-chrome google-chrome 3
linuxtech LinuxTECH 1,167
pgdg94 PostgreSQL 9.4 6.7 – x86_64 306
sl Scientific Linux 6.7 – x86_64 6,714
sl-security Scientific Linux 6.7 – x86_64 – security updates 251
sl6x Scientific Linux 6x – x86_64 6,714
sl6x-security Scientific Linux 6x – x86_64 – security updates 251
virtualbox Oracle Linux / RHEL / CentOS-6.7 / x86_64 – VirtualBox 0
repolist: 27,276
Hi bit twiddler,
Thanks, you can change virtualbox.repo file $releasever variable to 6, like:
Then it should work normally, and should work also with SL 6.8, 6.9, etc.
Example, CentOS 6.7 output is:
Thanks, that worked perfectly!
Excellent! You are welcome!
I actually meant that this should work also with Scientific Linux 6.8, 6.9, etc (not CentOS). Updated my comment too.
HI!
hello I’m using fedora 23. By the time I try to run the following command: /usr/lib/virtualbox/vboxdrv.sh setup . I have the following error:
Starting VirtualBox kernel modules [FALHOU]
Can anyone help me?
Hi Aristóteles,
Could you post output of following commands:
I have the same problem on fedora 23.
[[email protected] yum.repos.d]# uname -r
4.2.6-300.fc23.x86_64
[[email protected] yum.repos.d]# rpm -qa kernel |sort -V |tail -n 1
kernel-4.2.6-300.fc23.x86_64
Hi Daniel,
Could you also post output of following command:
Hi JR, output:
kernel-4.2.3-300.fc23.x86_64
kernel-4.2.6-300.fc23.x86_64
kernel-core-4.2.3-300.fc23.x86_64
kernel-core-4.2.6-300.fc23.x86_64
kernel-devel-4.2.6-300.fc23.x86_64
kernel-headers-4.2.6-300.fc23.x86_64
kernel-modules-4.2.3-300.fc23.x86_64
kernel-modules-4.2.6-300.fc23.x86_64
Thanks, looks good.
Could you post your /var/log/vbox-install.log example to http://pastebin.com ?
Uninstalling modules from DKMS
removing old DKMS module vboxhost version 5.0.10
——– Uninstall Beginning ——–
Module: vboxhost
Version: 5.0.10
Kernel: 4.2.6-300.fc23.x86_64 (x86_64)
————————————-
Status: Before uninstall, this module version was ACTIVE on this kernel.
Removing any linked weak-modules
weak-modules: this tool requires a dracut-enabled kernel
vboxdrv.ko:
– Uninstallation
– Deleting from: /lib/modules/4.2.6-300.fc23.x86_64/extra/
– Original module
– No original module was found for this module on this kernel.
– Use the dkms install command to reinstall any previous module version.
vboxnetflt.ko:
– Uninstallation
– Deleting from: /lib/modules/4.2.6-300.fc23.x86_64/extra/
– Original module
– No original module was found for this module on this kernel.
– Use the dkms install command to reinstall any previous module version.
vboxnetadp.ko:
– Uninstallation
– Deleting from: /lib/modules/4.2.6-300.fc23.x86_64/extra/
– Original module
– No original module was found for this module on this kernel.
– Use the dkms install command to reinstall any previous module version.
vboxpci.ko:
– Uninstallation
– Deleting from: /lib/modules/4.2.6-300.fc23.x86_64/extra/
– Original module
– No original module was found for this module on this kernel.
– Use the dkms install command to reinstall any previous module version.
depmod….
DKMS: uninstall completed.
——————————
Deleting module version: 5.0.10
completely from the DKMS tree.
——————————
Done.
Attempting to install using DKMS
Creating symlink /var/lib/dkms/vboxhost/5.0.10/source ->
/usr/src/vboxhost-5.0.10
DKMS: add completed.
Kernel preparation unnecessary for this kernel. Skipping…
Building module:
cleaning build area…
make KERNELRELEASE=4.2.6-300.fc23.x86_64 -C /lib/modules/4.2.6-300.fc23.x86_64/build M=/var/lib/dkms/vboxhost/5.0.10/build……….
cleaning build area…
DKMS: build completed.
vboxdrv:
Running module version sanity check.
– Original module
– No original module exists within this kernel
– Installation
– Installing to /lib/modules/4.2.6-300.fc23.x86_64/extra/
vboxnetflt.ko:
Running module version sanity check.
– Original module
– No original module exists within this kernel
– Installation
– Installing to /lib/modules/4.2.6-300.fc23.x86_64/extra/
vboxnetadp.ko:
Running module version sanity check.
– Original module
– No original module exists within this kernel
– Installation
– Installing to /lib/modules/4.2.6-300.fc23.x86_64/extra/
vboxpci.ko:
Running module version sanity check.
– Original module
– No original module exists within this kernel
– Installation
– Installing to /lib/modules/4.2.6-300.fc23.x86_64/extra/
Adding any weak-modules
weak-modules: this tool requires a dracut-enabled kernel
depmod….
DKMS: install completed.
Thanks, looks good too.
Could you post output of following commands:
JR,
Don’t work… :(
Starting VirtualBox kernel modules [FAILED]
(modprobe vboxdrv failed. Please use ‘dmesg’ to find out why)
Okay.
Could you check your:
output and post virtualbox/vbox related lines here?
And also post output of following commands:
Hi JR,
In the dmesg I have this output: capability: warning: `VirtualBox’ uses 32-bit capabilities (legacy support in use)
On the modinfo vboxdrv:
[ilename: /lib/modules/4.2.6-300.fc23.x86_64/extra/vboxdrv.ko
version: 5.0.10 (0x00240000)
license: GPL
description: Oracle VM VirtualBox Support Driver
author: Oracle Corporation
srcversion: 342F9F95905EFBCEFD26E63
depends:
vermagic: 4.2.6-300.fc23.x86_64 SMP mod_unload
parm: force_async_tsc:force the asynchronous TSC mode (int)
Thanks, could you first post output of following commands:
Hi my friend. The outputs:
Linux mypc 4.2.6-300.fc23.x86_64 #1 SMP Tue Nov 10 19:32:21 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
VirtualBox-5.0-5.0.10_104061_fedora22-1.x86_64
model name : Intel(R) Core(TM) i5-4200U CPU @ 1.60GHz
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 fma cx16 xtpr pdcm pcid sse4_1 sse4_2 movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm ida arat epb pln pts dtherm tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid xsaveopt
5
Thank you very much for helping!
Everything looks good.
Could you post output of following command:
Then could you run following commands again and post output:
Hi JR,
My system is corrupted once this weekend, I had to reinstall everything again.
Well … at least the error went away together.
Thank you for dedication and effort to help me.
A big hug.
You are very welcome! Excellent to hear that you got it working!
sorry for the delay
####
Comment uname -a
Linux localhost.localdomain 4.3.3-303.fc23.x86_64 #1 SMP Tue Jan 19 18:31:55 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
#####
rpm -qa kernel\* |sort -V
kernel-4.3.3-300.fc23.x86_64
kernel-4.3.3-301.fc23.x86_64
kernel-4.3.3-303.fc23.x86_64
kernel-core-4.3.3-300.fc23.x86_64
kernel-core-4.3.3-301.fc23.x86_64
kernel-core-4.3.3-303.fc23.x86_64
kernel-devel-4.3.3-303.fc23.x86_64
kernel-headers-4.3.3-303.fc23.x86_64
kernel-modules-4.3.3-300.fc23.x86_64
kernel-modules-4.3.3-301.fc23.x86_64
kernel-modules-4.3.3-303.fc23.x86_64
➜ ~ uname -a
Linux localhost.localdomain 4.3.3-303.fc23.x86_64 #1 SMP Tue Jan 19 18:31:55 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
➜ ~ rpm -qa kernel\* |sort -V
kernel-4.3.3-300.fc23.x86_64
kernel-4.3.3-301.fc23.x86_64
kernel-4.3.3-303.fc23.x86_64
kernel-core-4.3.3-300.fc23.x86_64
kernel-core-4.3.3-301.fc23.x86_64
kernel-core-4.3.3-303.fc23.x86_64
kernel-devel-4.3.3-303.fc23.x86_64
kernel-headers-4.3.3-303.fc23.x86_64
kernel-modules-4.3.3-300.fc23.x86_64
kernel-modules-4.3.3-301.fc23.x86_64
kernel-modules-4.3.3-303.fc23.x86_64
Dude, I don’t know who you are, but you fucking rule! These instructions worked like a charm!
When i get to step 4 i get the error ” Failed to open: /var/cache/dnf/epel-2b6dfc5904c26562/repodata/b1f1960d7c193c704fb268500c547db3d4985ee562079a5c86c17737ca6d07ab-updateinfo.xml.bz2.
“
Hi Leon,
Could you post output of following command:
Linux localhost.localdomain 4.2.6-301.fc23.x86_64 #1 SMP Fri Nov 20 22:22:41 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
You have Fedora 23, so EPEL repo isn’t needed. It’s only needed on CentOS/RHEL 7/6/5.
Could you post output of following command:
Nothing comes out when i enter “rpm -qa epel\*”
Could you then post output of:
[[email protected] Terminator]# dnf repolist
Last metadata expiration check performed 2:02:54 ago on Sun Dec 6 20:43:55 2015.
repo id repo name status
*fedora Fedora 23 – x86_64 46.074
google-chrome google-chrome 3
rpmfusion-free RPM Fusion for Fedora 23 – Free 692
rpmfusion-free-updates-testing RPM Fusion for Fedora 23 – Free – Test Updates 231
rpmfusion-nonfree RPM Fusion for Fedora 23 – Nonfree 206
rpmfusion-nonfree-updates-testing RPM Fusion for Fedora 23 – Nonfree – Test Updates 66
*updates Fedora 23 – x86_64 – Updates 6.637
virtualbox Fedora 23 – x86_64 – VirtualBox 10
[[email protected] Terminator]# ^C
I know that I got virtual box installed but its not working properly so im trying to uninstall it
Try again step 4. and run following command:
Is it working normally or do you still get same error?
At step five i get
[[email protected] yum.repos.d]# /usr/lib/virtualbox/vboxdrv.sh setup
Stopping VirtualBox kernel modules [ OK ]
Uninstalling old VirtualBox DKMS kernel modules [ OK ]
Trying to register the VirtualBox kernel modules using DKMS[ OK ]
Starting VirtualBox kernel modules [FAILED]
(modprobe vboxdrv failed. Please use ‘dmesg’ to find out why)
Okay, could you then post output of following commands:
The command dmesg |grep -i vbox give this output ” *NOTHING* ”
The command rpm -qa kernel\* |sort -V gives this output ”
kernel-4.2.3-300.fc23.x86_64
kernel-4.2.6-301.fc23.x86_64
kernel-core-4.2.3-300.fc23.x86_64
kernel-core-4.2.6-301.fc23.x86_64
kernel-devel-4.2.6-301.fc23.x86_64
kernel-headers-4.2.6-301.fc23.x86_64
kernel-modules-4.2.3-300.fc23.x86_64
kernel-modules-4.2.6-301.fc23.x86_64
”
The command rpm -qa VirtualBox\* gives out this output ”
VirtualBox-5.0-5.0.10_104061_fedora22-1.x86_64
VirtualBox-kmodsrc-5.0.10-1.fc23.x86_64
”
The command cat /proc/cpuinfo |grep -E “model name|flags” |tail -n 2 gives out this output ”
model name : Intel(R) Core(TM) i7-4790 CPU @ 3.60GHz
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm ida arat epb pln pts dtherm tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid xsaveopt
”
The command modinfo vboxdrv gives this ”
filename: /lib/modules/4.2.6-301.fc23.x86_64/extra/vboxdrv.ko
version: 5.0.10 (0x00240000)
license: GPL
description: Oracle VM VirtualBox Support Driver
author: Oracle Corporation
srcversion: 342F9F95905EFBCEFD26E63
depends:
vermagic: 4.2.6-301.fc23.x86_64 SMP mod_unload
parm: force_async_tsc:force the asynchronous TSC mode (int)
”
The command gives this ”
insmod /lib/modules/4.2.6-301.fc23.x86_64/extra/vboxdrv.ko
modprobe: ERROR: could not insert ‘vboxdrv’: Required key not available
”
the command /usr/lib/virtualbox/vboxdrv.sh status ”
VirtualBox kernel module is not loaded.
“
Looks like you have Secure Boot enabled and you have to go to BIOS/UEFI and disable Secure Boot, then it should work normally.
Thanks alot mate!
You are welcome!
I am running F23 LXDE, kernel 4.2.6-301.fc23.x86_64.
Funnily when installing VirtualBox 5.0.10 it pulled
the VirtualBox kernel modules built for the Linux
kernel 4.2.3-300.fc23.x86_64
I can’t start any VMs.
How do I fetch and install the right kmod for my kernel?
Hi THN,
Could you post output of following commands:
Hi JR
I uninstalled everything around VB, installed all the compiler stuff in your step 4 and reinstalled VB from yumex. All looks good now. Thanks for your help !!! My best, THN
Hi, I did an upgrade last night from F21 to 22 to 23. I removed all traces of VB due to an error, so I thought and for some reason systemd is trying to load kernel-modules and getting errors.
vboxdrv
vboxnetflt
vboxnetadp
systemctl status systemd-modules-load.service
● systemd-modules-load.service – Load Kernel Modules
Loaded: loaded (/usr/lib/systemd/system/systemd-modules-load.service; static; vendor preset: disabled)
Active: failed (Result: exit-code) since Sat 2015-12-12 23:28:16 EST; 9min ago
Docs: man:systemd-modules-load.service(8)
man:modules-load.d(5)
Process: 24816 ExecStart=/usr/lib/systemd/systemd-modules-load (code=exited, status=1/FAILURE)
Main PID: 24816 (code=exited, status=1/FAILURE)
Dec 12 23:28:15 nano systemd[1]: Starting Load Kernel Modules…
Dec 12 23:28:16 nano systemd[1]: systemd-modules-load.service: Main process exited, code=exited, status=1/FAILURE
Dec 12 23:28:16 nano systemd[1]: Failed to start Load Kernel Modules.
Dec 12 23:28:16 nano systemd[1]: systemd-modules-load.service: Unit entered failed state.
Dec 12 23:28:16 nano systemd[1]: systemd-modules-load.service: Failed with result ‘exit-code’.
[[email protected] Downloads]# systemctl start systemd-modules-load.service
Job for systemd-modules-load.service failed because the control process exited with error code. See “systemctl status systemd-modules-load.service” and “journalctl -xe” for details.
[[email protected] Downloads]# systemctl status systemd-modules-load.service
● systemd-modules-load.service – Load Kernel Modules
Loaded: loaded (/usr/lib/systemd/system/systemd-modules-load.service; static; vendor preset: disabled)
Active: failed (Result: exit-code) since Sat 2015-12-12 23:37:24 EST; 3s ago
Docs: man:systemd-modules-load.service(8)
man:modules-load.d(5)
Process: 26686 ExecStart=/usr/lib/systemd/systemd-modules-load (code=exited, status=1/FAILURE)
Main PID: 26686 (code=exited, status=1/FAILURE)
Dec 12 23:37:24 nano systemd[1]: Starting Load Kernel Modules…
Dec 12 23:37:24 nano systemd[1]: systemd-modules-load.service: Main process exited, code=exited, status=1/FAILURE
Dec 12 23:37:24 nano systemd[1]: Failed to start Load Kernel Modules.
Dec 12 23:37:24 nano systemd[1]: systemd-modules-load.service: Unit entered failed state.
Dec 12 23:37:24 nano systemd[1]: systemd-modules-load.service: Failed with result ‘exit-code’.
[[email protected] Downloads]# journalctl -b _PID=26686
— Logs begin at Wed 2015-12-09 18:24:02 EST, end at Sat 2015-12-12 23:37:24 EST. —
Dec 12 23:37:24 nano systemd-modules-load[26686]: Failed to find module ‘vboxdrv’
Dec 12 23:37:24 nano systemd-modules-load[26686]: Failed to find module ‘vboxnetflt’
Dec 12 23:37:24 nano systemd-modules-load[26686]: Failed to find module ‘vboxnetadp’
I have searched and searched and cannot find anything as to why the modules are attempting to be loaded when I cannot find any files left on the system for Virtual Box.
[[email protected] lib]# dmesg |grep -i vbox
[[email protected] lib]#
[[email protected] lib]# rpm -qa kernel\* |sort -V
kernel-4.2.6-301.fc23.x86_64
kernel-core-4.2.3-300.fc23.x86_64
kernel-core-4.2.6-301.fc23.x86_64
kernel-debug-devel-4.2.6-301.fc23.x86_64
kernel-headers-4.2.6-301.fc23.x86_64
kernel-modules-4.2.6-301.fc23.x86_64
kernel-modules-extra-4.2.6-301.fc23.x86_64
kernel-tools-libs-4.2.6-301.fc23.x86_64
[[email protected] lib]#
[[email protected] lib]# rpm -qa VirtualBox\*
[[email protected] lib]#
[[email protected] lib]# cat /proc/cpuinfo |grep -E “model name|flags” |tail -n 2
model name : Intel(R) Core(TM)2 Duo CPU P8400 @ 2.26GHz
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts rep_good nopl aperfmperf pni dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm sse4_1 xsave lahf_lm ida dtherm tpr_shadow vnmi flexpriority
[ro[email protected] lib]#
[[email protected] lib]# modinfo vboxdrv
modinfo: ERROR: Module vboxdrv not found.
[[email protected] lib]#
[[email protected] lib]# modprobe -v vboxdrv
modprobe: FATAL: Module vboxdrv not found in directory /lib/modules/4.2.3-300.fc23.x86_64
[[email protected] lib]#
[[email protected] lib]# /usr/lib/virtualbox/vboxdrv.sh status
-bash: /usr/lib/virtualbox/vboxdrv.sh: No such file or directory
[[email protected] lib]#
[[email protected] lib]#
[[email protected] lib]# uname -a
Linux nano 4.2.3-300.fc23.x86_64 #1 SMP Mon Oct 5 15:42:54 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
[[email protected] lib]#
Any ideas?
Hi Eric,
Looks like you are running 4.2.3 kernel and you have 4.2.6 kernel (also headers and devel) installed. Try to boot using 4.26 kernel.
I didn’t notice that. However I happen to do a dnf update and a new kernel was avail. I did the update, rebooted, and now the kernel that is installed is being ran on 4.2.7. Checked the status of the modules and this is the output.
systemctl status systemd-modules-load.service
● systemd-modules-load.service – Load Kernel Modules
Loaded: loaded (/usr/lib/systemd/system/systemd-modules-load.service; static; vendor preset: disabled)
Active: inactive (dead)
Condition: start condition failed at Wed 2015-12-16 22:15:19 EST; 3s ago
none of the trigger conditions were met
Docs: man:systemd-modules-load.service(8)
man:modules-load.d(5)
I cannot find where but it seems there is a pointer somewhere referencing the missing vbox modules.
Any recommendation?
I am not an expert so I apologize, looks like all traces were removed. There just isn’t any modules in there for it to start. I thought this was just another error message due to the original issue.
Thanks! It was because I was not on the right Kernel.
Hi Eric,
If you didn’t got it working yet, then try to run:
I just wanted it fully removed. Upon updating kernel and booting to that version, it no longer looks for it. Thanks for your help.
Okay, excellent! You are welcome!