On Mon, 9 Aug 2021 08:46:36 -0700 Paolo Galtieri <pgaltieri@xxxxxxxxx> wrote: > Thank you for the hint. The problem is that the vbox modules are > being rebuilt on boot, despite the fact I've already built them. It's > interesting that when I run /sbin/vboxconfig to rebuild the modules > it tells me that the modules may need to be signed. After it builds > the modules it tries to load them and fails due to the modules not > being signed. I don't know why vboxconfig doesn't check to see if > the modules already exist before trying to build them. I don't think this is the fault of VirtualBox. I think it is because of either akmod or the kernel itself. But, you can open a bugzilla against VirtualBox in case it is VirtualBox causing the problem. The packager will probably know whether this is VirtualBox or not, and get it to the right place. _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
