Bug 31483 - Virtualbox: could not insert 'vboxdrv': Unknown symbol in module
Summary: Virtualbox: could not insert 'vboxdrv': Unknown symbol in module
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 8
Hardware: All Linux
Priority: Normal major
Target Milestone: ---
Assignee: Thomas Backlund
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-02-01 09:30 CET by papoteur
Modified: 2023-02-05 09:55 CET (History)
1 user (show)

See Also:
Source RPM: virtualbox-7.0.6-1.mga8.src.rpm
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description papoteur 2023-02-01 09:30:36 CET 
Description of problem:
févr. 01 09:24:39 systemd[1]: Starting VirtualBox host kernel driver loader...
févr. 01 09:24:39 modprobe[26183]: modprobe: ERROR: could not insert 'vboxdrv': Unknown symbol in module, or unknown paramet>
févr. 01 09:24:39 systemd[1]: vboxhost.service: Main process exited, code=exited, status=1/FAILURE
févr. 01 09:24:39 systemd[1]: vboxhost.service: Failed with result 'exit-code'.
févr. 01 09:24:39 systemd[1]: Failed to start VirtualBox host kernel driver loader.

Any Virtualbox machine can't be launched

Version-Release number of selected component (if applicable):
virtualbox 7.0.6
uname -a
Linux YZenbook.home 5.15.88-desktop-1.mga8 #1 SMP Sat Jan 14 15:00:41 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
rpm -qa|grep virtualbox
virtualbox-7.0.6-1.mga8
virtualbox-kernel-desktop-latest-7.0.6-1.mga8
virtualbox-kernel-5.15.88-desktop-1.mga8-7.0.6-1.mga8
virtualbox-kernel-5.15.82-desktop-1.mga8-7.0.4-1.2.mga8
Morgan Leijström 2023-02-01 10:32:40 CET

See Also: (none) => https://bugs.mageia.org/show_bug.cgi?id=25819

Morgan Leijström 2023-02-01 10:33:14 CET

Assignee: bugsquad => tmb
CC: (none) => fri

Comment 1 papoteur 2023-02-05 09:55:48 CET 
After uninstalling dkms-virtualbox, reboot, then reinstalling it, it works.

Resolution: (none) => FIXED
Status: NEW => RESOLVED
Note You need to log in before you can comment on or make changes to this bug.