On 3/12/26 3:59 PM, Michael D. Setzer II wrote:
On 12 Mar 2026 at 13:20, Samuel Sieb wrote:
Date sent: Thu, 12 Mar 2026 13:20:47 -0700
Subject: Re: Fedora has broken VirtualBox with 6.19.6
To: Community support for Fedora users
<[email protected]>
From: Samuel Sieb <[email protected]>
Send reply to: Community support for Fedora users
<[email protected]>
On 3/12/26 12:20 PM, Michael D. Setzer II wrote:
On 12 Mar 2026 at 11:18, Samuel Sieb wrote:
Date sent: Thu, 12 Mar 2026 11:18:27 -0700
Subject: Re: Fedora has broken VirtualBox with 6.19.6
To: [email protected]
From: Samuel Sieb <[email protected]>
Send reply to: Community support for Fedora users
<[email protected]>
On 3/12/26 10:21 AM, Michael D. Setzer II via users wrote:
Lines with error
cat 7.2.6-1-for-6.19.6-200.fc43.x86_64.failed.log | grep -i error
ERROR: modpost: module vboxdrv uses symbol cr4_update_irqsoff
from namespace module:kvm,kvm-amd,kvm-intel, but does not
import it.
ERROR: modpost: module vboxdrv uses symbol cr4_read_shadow
from namespace module:kvm,kvm-amd,kvm-intel, but does not
import it.
ERROR: modpost: module vboxdrv uses symbol __flush_tlb_all from
namespace module:kvm,kvm-amd,kvm-intel, but does not import it.
This isn't Fedora blocking anything, this is a problem with the module.
From what I've found. Works fine with Previous kernel with
Module? But information shows that latest kernel has Fedora
restricking access to only KVM, so VirtualBox can not work with
the restriction??
What information? That doesn't make sense.
AI Overview
VirtualBox 7.1.x is currently incompatible with Linux kernel 6.19.6 on Fedora 43
due to a module building error, requiring either a downgrade to kernel 6.18.x or
disabling KVM modules. To fix, add kvm.enable_virt_at_load=0 to your GRUB boot
arguments, or temporarily remove modules using sudo modprobe -r kvm_intel or
kvm_amd
I can confirm that if I boot with 6.18 kernel it works perfectly, but
booting with 6.19.6 it runs the akmods but it fails, and manually
trying to run it fails.
AI...
Anyway, it's nothing specific to Fedora. It's just a change in the new
kernel that requires changes to the virtualbox module. Just change to
using KVM and avoid all this trouble.
> Known Issues with Kernel 6.19.x
> Specifically for kernel 6.19.6, some users have reported that
> VirtualBox kernel modules (vboxdrv) may fail to build entirely
> because of symbol moves in the upstream kernel. If the above fixes
> do not work:
>
> Never really used KVM. Think I tired on another machine, but it
> didn't work at all. So, kept what has worked for like 20 years.
>
> Has worked with up to 6.18.16, just broken with 6.19.6?
yes
--
_______________________________________________
users mailing list -- [email protected]
To unsubscribe send an email to [email protected]
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/[email protected]
Do not reply to spam, report it:
https://forge.fedoraproject.org/infra/tickets/issues/new
