2

I previously was using VirtualBox on Fedora 30, but recently moved to using Boxes (review) and am quite happy with the switch. I've removed VirtualBox, but upon booting up my system, I still get a tainted kernel message:

vboxdrv: module verification failed: signature and/or required key missing - tainting kernel

I've tried:

sudo rmmod vboxpci vboxnetadp vboxnetflt vboxdrv

(the other modules were being used by vboxdrv)

This appeared to remove the module, but after a reboot, the modules were back.

Since I am no longer using VirtualBox, how can I remove this vboxdrv kernel module?

Thank you for any help!

  • 1
    Do you have any files in /etc/modules-load.d/, such as virtualbox.conf? – Jeff Schaller Jun 14 at 16:21
  • 1
    Did you remove the VirtualBox package? – 9000 Jun 14 at 16:25
  • @vim_usr How did you remove VirtualBox? – Yurij Goncharuk Jun 14 at 16:30
  • @YurijGoncharuk I removed the Virtual Box package using: dnf remove VirtualBox – vim_usr Jun 14 at 17:54
  • @JeffSchaller No files in that dir – vim_usr Jun 14 at 17:56
2

Caveat: I don't have a Fedora system at-hand, so this is untested!

I would suggest removing the file /etc/modules-load.d/virtualbox.conf; it may be owned by a package, so check: dnf provides /etc/modules-load.d/virtualbox.conf and if needed, remove that package with: dnf remove (that package name).

As per this Fedora Forum post, you may need to rebuild your initramfs so that it's built without the vbox driver(s). Use: dracut -f /boot/initramfs-"$(uname -r)".img "$(uname -r)"


Specific solution from the OP:

I found virtualbox.conf located in /lib/modules-load.d/ and provided by VirtualBox-server. After removing VirtualBox-server, then removing vboxpci, vboxnetadp, vboxnetflt, and vboxdrv via rmmod, and finally rebuilding initramfs as written above, the problem is solved.

  • 1
    I found virtualbox.conf located in /lib/modules-load.d/ and provided by VirtualBox-server. After removing VirtualBox-server, then removing vboxpci, vboxnetadp, vboxnetflt, and vboxdrv via rmmod, and finally rebuilding initramfs as written above, the problem is solved. Thank you. – vim_usr Jun 14 at 18:28

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.