Ask Your Question
2

Unable to update VirtualBox modules after last kernel update

asked 2018-09-13 10:26:19 -0600

bob323 gravatar image

updated 2018-09-13 11:27:18 -0600

I haven't needed to spin up a VM in a while, but I tried today and was unable to. I created a systemd service that calls a script on boot to ensure the VirtualBox modules are signed, which ran fine until the last kernel update. I haven't had to look at it until now.

The problem is that the vboxdrv module can't be found. When I execute modprobe vboxdrv, I get this error: modprobe: FATAL: Module vboxdrv not found in directory /lib/modules/4.18.5-200.fc28.x86_64. I checked and there are indeed no modules under /lib/modules/.../extra/VirtualBox. In fact, there's not even a VirtualBox directory within the extra directory.

After more troubleshooting I figured out I was missing the akmod-VirtualBox package. I installed that and ran sudo akmods, but it failed to build the VirtualBox modules. I tried removing that and installing kmod-VirtualBox (I'm a little mixed up on the difference between the akmod and kmod packages), which just installed both the akmod and kmod packages. Tried building again, still no success. I've included the build log at the pastebin link. Any help is appreciated.

https://pastebin.com/pSctvdMM

The only other relevant information I can provide is that the service systemd-modules-load.service fails on boot. Here's the relevant part of the journalctl output when I try to restart the service:

Sep 13 12:08:54 localhost.localdomain systemd[1]: Starting Load Kernel Modules...
-- Subject: Unit systemd-modules-load.service has begun start-up
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit systemd-modules-load.service has begun starting up.
Sep 13 12:08:54 localhost.localdomain audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-modules-load comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
Sep 13 12:08:54 localhost.localdomain systemd-modules-load[19806]: Failed to find module 'vboxdrv'
Sep 13 12:08:54 localhost.localdomain audit[19802]: USER_END pid=19802 uid=0 auid=1000 ses=2 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 msg='op=PAM:session_close grantors=pam_keyinit,pam_limits,pam_keyinit,pam_limits,pam_systemd,pam_unix acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
Sep 13 12:08:54 localhost.localdomain audit[19802]: CRED_DISP pid=19802 uid=0 auid=1000 ses=2 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 msg='op=PAM:setcred grantors=pam_env,pam_fprintd acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
Sep 13 12:08:54 localhost.localdomain sudo[19802]: pam_unix(sudo:session): session closed for user root
Sep 13 12:08:54 localhost.localdomain systemd-modules-load[19806]: Failed to find module 'vboxnetflt'
Sep 13 12:08:54 localhost.localdomain systemd-modules-load[19806]: Failed to find module 'vboxnetadp'
Sep 13 12:08:54 localhost.localdomain systemd-modules-load[19806]: Failed to find module 'vboxpci'
Sep 13 12:08:54 localhost.localdomain systemd[1]: systemd-modules-load.service: Main process exited, code=exited, status=1/FAILURE
Sep 13 12:08:54 ...
(more)
edit retag flag offensive close merge delete

Comments

After looking around some more, this may have something to do with SELinux, as suggested on rpmfusion.

Also, this problem seems identical to this other question on ask.FedoraProject that was never answered.

bob323 gravatar imagebob323 ( 2018-09-13 11:08:14 -0600 )edit

2 Answers

Sort by » oldest newest most voted
1

answered 2018-09-13 12:38:59 -0600

Rabin gravatar image

Seems like VirtualBox-kmod-5.2.18 is no yet compatible with kernel 4.18.5-200.fc28.x8664, I run akmod to force the rebuild, and it failed as well, looking in the log file (/var/cache/akmods/VirtualBox/5.2.18-2-for-4.18.5-200.fc28.x8664.failed.log) I see many error regarding "incompatible types"

2018/09/13 20:13:41 akmodsbuild: /tmp/akmodsbuild.ZZxBEdrz/BUILD/VirtualBox-kmod-5.2.18/_kmod_build_4.18.5-200.fc28.x86_64/vboxsf/utils.c:81:17: error: incompatible types when assigning to type ‘struct timespec64’ from type ‘struct timespec’

I think we need to wait for updated package of virtualbox-kmod

edit flag offensive delete link more

Comments

Looks like you were right, I just updated this morning and found an update for kmod-VirtualBox waiting. Just to be sure, I re-ran sudo akmods and restarted the VirtualBox signing service, which succeeded. I tried starting my VM and it runs just fine.

bob323 gravatar imagebob323 ( 2018-09-14 08:35:33 -0600 )edit

This strange, I have installed 5.2.18 from the Oracle repository on F28 and could build the kernel modules for 4.18.5 without problems, and all VMs are still working fine. So this can't be a generic incompatibility between VBox 5.2.18 and 4.18.5, this problem must be something specific to akmod resp. the akmod build of VirtualBox.

Axel Sommerfeldt gravatar imageAxel Sommerfeldt ( 2018-09-14 14:25:02 -0600 )edit
0

answered 2018-09-24 22:07:11 -0600

cubanzee gravatar image

I also had lots of problems with VBox, lots of errors, wouldn't run, getting hung up with kernal errors, tried adding all different dependencies and Service Tools, then I gave up and decided to try "Boxes". Wow, what a difference...!

After the download I pointed it to an .iso file, it started loading, and it worked right away. No problems at all. Who ever made that program... WAY TO GO. Nice work...! I suggest you try Boxes. Very easy virtualization product. (I am using Fedora, and it started SUSE with no issues.)

[Does anyone know who designed that program...?]

edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Question Tools

2 followers

Stats

Asked: 2018-09-13 10:26:19 -0600

Seen: 231 times

Last updated: Sep 24