Bug 2211675

Summary:	VirtualBox akmods breaks after upgrading to Fedora 37
Product:	[Fedora] Fedora	Reporter:	Basic Six <drbasic6>
Component:	akmods	Assignee:	Nicolas Chauvet (kwizart) <kwizart>
Status:	CLOSED COMPLETED	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	37	CC:	hdegoede, hobbes1069, kwizart, leigh123linux, negativo17, nicolas.vieville, travier
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-06-02 06:00:15 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Basic Six 2023-06-01 13:02:04 UTC

After upgrading to Fedora 37, VirtualBox won't start anymore because:
WARNING: The vboxdrv kernel module is not loaded.

In the past, it would usually be unusable after the upgrade because akmods simply skipped the rebuild, see this bug:
https://bugzilla.redhat.com/show_bug.cgi?id=1474969

In Fedora 37, running akmods manually does not show such a hint that it skipped something:

# akmods
Checking kmods exist for 6.2.15-200.fc37.x86_64            [  OK  ]
# systemctl restart vboxdrv
Job for vboxdrv.service failed because the control process exited with error code.
# modprobe vboxdrv
modprobe: FATAL: Module vboxdrv not found in directory /lib/modules/6.2.15-200.fc37.x86_64

The release notes do not seem to mention a known bug regarding VirtualBox.
https://fedoraproject.org/wiki/Releases/37/ChangeSet

So what are Fedora users supposed to do after upgrading to get their virtualization working again?


Reproducible: Always

Steps to Reproduce:
1. Use Fedora dn VirtualBox for years; never upgrade to the latest release when it's out immediately, instead wait for some time for bugs to get fixed.
2. Some months later, upgrade. VirtualBox is broken again, can't work with vms. Apparently haven't waited long enough for bugs to get fixed?
3. Get help debugging and repairing the system broken by the upgrade...

Comment 1 leigh scott 2023-06-02 06:00:15 UTC

File the issue against VirtualBox at rpmfusion.


https://bugzilla.rpmfusion.org/enter_bug.cgi

Comment 2 leigh scott 2023-06-02 07:08:06 UTC

(In reply to leigh scott from comment #1)
> File the issue against VirtualBox at rpmfusion.
> 
> 
> https://bugzilla.rpmfusion.org/enter_bug.cgi

Also see.

https://bugzilla.redhat.com/show_bug.cgi?id=2011120