Re: Fedora has broken VirtualBox with 6.19.6
On Sat, 2026-03-14 at 09:09 -0400, Robert McBroom via users wrote: > Noticed in several iterations that dnf removal of a kernel looks like > it > is removing the entire OS. Letting things be until the specified > kernel > is removed by an update works. Strange Why are you removing the kernel? Just boot an earlier one. poc -- ___ 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
Re: Fedora has broken VirtualBox with 6.19.6
On 3/13/26 7:59 AM, Michael D. Setzer II via users wrote: On 12 Mar 2026 at 17:46, Samuel Sieb wrote: Date sent: Thu, 12 Mar 2026 17:46:09 -0700 Subject:Re: Fedora has broken VirtualBox with 6.19.6 To: Community support for Fedora users From: Samuel Sieb Send reply to: Community support for Fedora users On 3/12/26 4:46 PM, Michael D. Setzer II wrote: Again the 6.18.16 kerenel works fine, but 6.19.6 kernel fails. So, it is something Fedora has done. Perhaps it will be fixed. But the one page had said Fedora had restricted things to KVM only, so virtualbox couldn't get access to the features required to build the akmods Why do you keep saying it's something Fedora did? All Fedora did was update the kernel to 6.19. It's a problem with virtualbox, nothing specific to Fedora. You're getting bad information or else misinterpreting it. Just took a look at updates testing, and it shows a kernel update along with lots of others. Then did a look with just kernel updates. No VirtualBox or akmods showing. Not sure why it is showing removal of 6.17.1 and 6.18.16? Had recently updated machine from FC42 to FC43. No fc42 files in /boot? 4:44am here, so not going to test it at this time. But interesting that an update to kernel 6.19.7 is in the works. rpm -qa | grep kernel-core kernel-core-6.18.16-200.fc43.x86_64 kernel-core-6.17.1-300.fc43.x86_64 kernel-core-6.19.6-200.fc43.x86_64 Did just check an autoremove, and it showed no fc42 kernel # dnf autoremove PackageArch Version Repository Size Removing: python3-jsonschemanoarch 4.23.0-6.fc43 fedora906.7 KiB python3-jsonschema-specifications noarch 2024.10.1-6.fc43fedora 46.2 KiB python3-referencing noarch 0.36.2-5.fc43 fedora336.5 KiB python3-rpds-py x86_64 0.27.0-2.fc43 fedora747.8 KiB Transaction Summary: Removing: 4 packages After this operation, 2 MiB will be freed (install 0 B, remove 2 MiB). Is this ok [y/N]: y Running transaction [1/5] Prepare transaction 100% | 3.0 B/s | 4.0 B | 00m01s [2/5] Removing python3-jsonschema-0:4.23.0-6.fc43.noarch 100% | 3.2 KiB/s | 120.0 B | 00m00s [3/5] Removing python3-jsonschema-specifications-0:2024.10.1-6.fc43.noarch 100% | 4.6 KiB/s | 47.0 B | 00m00s [4/5] Removing python3-referencing-0:0.36.2-5.fc43.noarch 100% | 5.0 KiB/s | 51.0 B | 00m00s [5/5] Removing python3-rpds-py-0:0.27.0-2.fc43.x86_64 100% | 13.0 B/s | 20.0 B | 00m02s Complete! Interesting if nothing else? Perhaps when it gets to updates repo. # dnf update kernel* --enablerepo=updates-testing Updating and loading repositories: Repositories loaded. PackageArchVersion Repository Size Removing: kernel-core x86_64 6.17.1-300.fc43 fedora 97.9 MiB kernel-devel x86_64 6.18.16-100.fc42 updates 80.9 MiB kernel-modules-core x86_64 6.17.1-300.fc43 fedora 68.3 MiB Upgrading: kernel-devel-matched x86_64 6.19.7-200.fc43 updates-testing 0.0 B replacing kernel-devel-matched x86_64 6.19.6-200.fc43updates 0.0 B kernel-tools x86_64 6.19.7-200.fc43 updates-testing 918.1 KiB replacing kernel-tools x86_64 6.19.6-200.fc43 updates 918.1 KiB kernel-tools-libs x86_64 6.19.7-200.fc43 updates-testing 30.3 KiB replacing kernel-tools-libs x86_64 6.19.6-200.fc43 updates 30.3 KiB Installing: kernelx86_64 6.19.7-200.fc43 updates-testing 0.0 B kernel-core x86_64 6.19.7-200.fc43 updates-testing 98.0 MiB kernel-devel x86_64 6.19.7-200.fc43 updates-testing 87.5 MiB kernel-modulesx86_64 6.19.7-200.fc43 updates-testing 96.2 MiB kernel-modules-core x86_64 6.19.7-200.fc43 updates-testing 70.6 MiB kernel-modules-extra x86_64 6.19.7-200.fc43 updates-testing 4.2 MiB Transaction Summary: Installing: 6 packages Upgrading: 3 packages Replacing: 3 packages R
Re: Fedora has broken VirtualBox with 6.19.6
> On 13 Mar 2026, at 18:45, Dave Close wrote: > > FWIW, my observation is that Fedora kernel updates seem to come in pairs. You get one new kernel a week on average. No pairing going on that I have noticed. Often the first kernel of a new series can flush out bugs then the following kernels usually have regress fixes as upstream releases them. As you always have 3 kernels by default if you are hit with a regression then report the bug and use the previous kernel for a while longer. Barry -- ___ 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
Re: Fedora has broken VirtualBox with 6.19.6
On Fri, 2026-03-13 at 11:19 -0500, Roger Heflin wrote: > This is a kernel change that breaks the module, it is not a fedora > specific change. The kernel makes this sort of change to make their > code better in some manner all of the time and these sorts of changes > break out-of-tree modules all of the time. As others have said, it's a kernel problem, not a Fedora problem. The *current* kernel that Fedora uses, which *may* be different than the kernels in other distros. But, at some time, those other distros *may* have a problem with the *next* kernel they use. -- uname -rsvp Linux 3.10.0-1160.119.1.el7.x86_64 #1 SMP Tue Jun 4 14:43:51 UTC 2024 x86_64 (yes, this is the output from uname for this PC when I posted) Boilerplate: All unexpected mail to my mailbox is automatically deleted. I will only get to see the messages that are posted to the mailing list. -- ___ 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
Re: Fedora has broken VirtualBox with 6.19.6
https://discussion.fedoraproject.org/t/fedora-43-virtualbox-not-working-with-kernal-6-19-6/183037 -- ___ 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
Re: Fedora has broken VirtualBox with 6.19.6
"Michael D. Setzer II" wrote: >But interesting that an update to kernel 6.19.7 is in the works. FWIW, my observation is that Fedora kernel updates seem to come in pairs. My guess is that the second of each pair corrects something(s) wrong with the first. I generally don't reboot on the first, waiting for the second. -- Dave Close, Compata, Irvine CA +1 714 434 7359 [email protected] [email protected] "We consider too much the good luck of the early bird and not enough the bad luck of the early worm." -- Franklin Roosevelt -- ___ 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
Re: Fedora has broken VirtualBox with 6.19.6
On 13 Mar 2026 at 16:54, Barry wrote: From: Barry Subject:Re: Fedora has broken VirtualBox with 6.19.6 Date sent: Fri, 13 Mar 2026 16:54:19 + To: [email protected], [email protected] Copies to: [email protected], "Michael D. Setzer II" Send reply to: Community support for Fedora users > > > > On 13 Mar 2026, at 16:47, Michael D. Setzer II via users > > wrote: > > > > Just took a look at updates testing, and it shows a kernel update > > along with lots of others. Then did a look with just kernel updates. > > No VirtualBox or akmods showing. > > You could ask over on the rpmfusion mailing list is the maintainers of 3rd > party virtualbox know of a fix yet. > Just to note: Issue has been fixed. akmods-0.6.2-9.fc43.noarch was updated, afterwards the akmods no longer fails to build, and VirtualBox works. Checked site, and only a few things listed, and none that seemed to talk about this issue? BUGS https://bugz.fedoraproject.org/akmods Have sent a message to maintainer and author to see if they will note what the cause and solution was? Just interested. MAINTAINER Richard Shaw AUTHOR Thorsten Leemhuis > If you want to migrate to kvm maybe start a new topic and ask for help in > migrating. > I personally converted vmware images to kvm a while ago, hopefully the > migrate from virtbox is no harder. > Someone earlier said they had successfully done a migration might be able to > offer insights Thanks will look at it again, last time I looked at it, it seems that the KVM was a much bigger deal than VirtualBox. Took over G4L project in 2004, and it has worked fine to test the ISO images and now grub4dos image files with both bios and uefi loaders, and now update to initramfs since the initrd is scheduled to be phased out by 1/2027. Just test the boot and simple test. Can also, boot the kernels for testing directly from grub menu, but that requires rebooting machine. cat 5454d68084c145e496d5ce383b5147de-0-G4L.conf title G4L 0.70 version 0.G4L linux /bz6x19.7 initrd /initramfs.lzma $tuned_initrd grub_users $grub_users grub_arg --unrestricted grub_class fedora Project just boots to ram, and runs in ram. Also, have a kernel 7.0.rc3 kernel testing. Thanks. > > Barry > -- > ___ > 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 ++ Michael D. Setzer II - Computer Science Instructor (Retired) mailto:[email protected] mailto:[email protected] mailto:[email protected] Guam - Where America's Day Begins G4L Disk Imaging Project maintainer http://sourceforge.net/projects/g4l/ ++ -- ___ 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
Re: Fedora has broken VirtualBox with 6.19.6
On Fri, 2026-03-13 at 11:01 +1000, Michael D. Setzer II via users wrote: > Don't understand your logic??? > It works with 6.18.16 but doesn't work with 6.19.6 kernel. > Nothing else changes. VirtualBox is the same.akmods is the same. > Only variable in the situation is the changes from kernel 6.18.16 to > 6.19.6. So, something was changed in the build of 6.19.6. akmods is a system that *dynamically* recompiles a kernel module when a new module is installed. This means that virtual box has a kernel module used for virtualization that isn't accepted in the kernel sources itself. This means that everytime a new kernel is installed on your system it needs to compile the module from source code. If the kernel has changed any function that the virtual box module uses, it won't compile. That is why everyone says this is not a Fedora issue. The virtualbox package and akmod have a version of the kernel module that is no longer compatible with a newer kernel which is why it fails to compile with the newer kernel. You'd have the same problem on any distro until virtualbox comes out with a newer version that is compatible with the newer kernel. -- ___ 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
Re: Fedora has broken VirtualBox with 6.19.6
> On 13 Mar 2026, at 16:47, Michael D. Setzer II via users > wrote: > > Just took a look at updates testing, and it shows a kernel update > along with lots of others. Then did a look with just kernel updates. > No VirtualBox or akmods showing. You could ask over on the rpmfusion mailing list is the maintainers of 3rd party virtualbox know of a fix yet. If you want to migrate to kvm maybe start a new topic and ask for help in migrating. I personally converted vmware images to kvm a while ago, hopefully the migrate from virtbox is no harder. Someone earlier said they had successfully done a migration might be able to offer insights Barry -- ___ 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
Re: Fedora has broken VirtualBox with 6.19.6
On 12 Mar 2026 at 17:46, Samuel Sieb wrote: Date sent: Thu, 12 Mar 2026 17:46:09 -0700 Subject:Re: Fedora has broken VirtualBox with 6.19.6 To: Community support for Fedora users From: Samuel Sieb Send reply to: Community support for Fedora users > On 3/12/26 4:46 PM, Michael D. Setzer II wrote: > > Again the 6.18.16 kerenel works fine, but 6.19.6 kernel fails. So, it > > is something Fedora has done. Perhaps it will be fixed. But the one > > page had said Fedora had restricted things to KVM only, so > > virtualbox couldn't get access to the features required to build the > > akmods > > Why do you keep saying it's something Fedora did? All Fedora did was > update the kernel to 6.19. It's a problem with virtualbox, nothing > specific to Fedora. You're getting bad information or else > misinterpreting it. Just took a look at updates testing, and it shows a kernel update along with lots of others. Then did a look with just kernel updates. No VirtualBox or akmods showing. Not sure why it is showing removal of 6.17.1 and 6.18.16? Had recently updated machine from FC42 to FC43. No fc42 files in /boot? 4:44am here, so not going to test it at this time. But interesting that an update to kernel 6.19.7 is in the works. rpm -qa | grep kernel-core kernel-core-6.18.16-200.fc43.x86_64 kernel-core-6.17.1-300.fc43.x86_64 kernel-core-6.19.6-200.fc43.x86_64 Did just check an autoremove, and it showed no fc42 kernel # dnf autoremove PackageArch Version Repository Size Removing: python3-jsonschemanoarch 4.23.0-6.fc43 fedora906.7 KiB python3-jsonschema-specifications noarch 2024.10.1-6.fc43fedora 46.2 KiB python3-referencing noarch 0.36.2-5.fc43 fedora336.5 KiB python3-rpds-py x86_64 0.27.0-2.fc43 fedora747.8 KiB Transaction Summary: Removing: 4 packages After this operation, 2 MiB will be freed (install 0 B, remove 2 MiB). Is this ok [y/N]: y Running transaction [1/5] Prepare transaction 100% | 3.0 B/s | 4.0 B | 00m01s [2/5] Removing python3-jsonschema-0:4.23.0-6.fc43.noarch 100% | 3.2 KiB/s | 120.0 B | 00m00s [3/5] Removing python3-jsonschema-specifications-0:2024.10.1-6.fc43.noarch 100% | 4.6 KiB/s | 47.0 B | 00m00s [4/5] Removing python3-referencing-0:0.36.2-5.fc43.noarch 100% | 5.0 KiB/s | 51.0 B | 00m00s [5/5] Removing python3-rpds-py-0:0.27.0-2.fc43.x86_64 100% | 13.0 B/s | 20.0 B | 00m02s Complete! Interesting if nothing else? Perhaps when it gets to updates repo. # dnf update kernel* --enablerepo=updates-testing Updating and loading repositories: Repositories loaded. PackageArchVersion Repository Size Removing: kernel-core x86_64 6.17.1-300.fc43 fedora 97.9 MiB kernel-devel x86_64 6.18.16-100.fc42 updates 80.9 MiB kernel-modules-core x86_64 6.17.1-300.fc43 fedora 68.3 MiB Upgrading: kernel-devel-matched x86_64 6.19.7-200.fc43 updates-testing 0.0 B replacing kernel-devel-matched x86_64 6.19.6-200.fc43updates 0.0 B kernel-tools x86_64 6.19.7-200.fc43 updates-testing 918.1 KiB replacing kernel-tools x86_64 6.19.6-200.fc43 updates 918.1 KiB kernel-tools-libs x86_64 6.19.7-200.fc43 updates-testing 30.3 KiB replacing kernel-tools-libs x86_64 6.19.6-200.fc43 updates 30.3 KiB Installing: kernelx86_64 6.19.7-200.fc43
Re: Fedora has broken VirtualBox with 6.19.6
On Fri, Mar 13, 2026 at 11:02 AM Michael D. Setzer II via users wrote: > > On 12 Mar 2026 at 21:30, Richard Kimberly Heck wrote: > > Date sent: Thu, 12 Mar 2026 21:30:21 -0400 > Subject: Re: Fedora has broken VirtualBox with 6.19.6 > To: [email protected] > From: Richard Kimberly Heck > Send reply to: Community support for Fedora users > > > > On 3/12/26 7:46 PM, Michael D. Setzer II via users wrote: > > > Again the 6.18.16 kerenel works fine, but 6.19.6 kernel fails. So, it > > > is something Fedora has done. > > > > Unless I'm mistaken, the problem is caused by changes within the kernel > > itself, not by anything to do with Fedora. Responsibility to adapt to > > those changes seems to lie with the authors of VirtualBox, since it is > > the modules they need that will not build with the new kernel. > > > > I've seen some pages that show if works with other distros, but > specifically says it doesn't work with Fedora, and only option is to > boot with 6.18.16 on Fedora at momment. > Specifically said that Fedora was only allowing access to low level > CPU functions to KVM, so the VirtualBox can not get the required > access. Will have to see if they can update the akmods to allow it to > build. Adding "Fedora" in search generally shows those links. > > Currently have 8 linux machines all running Fedora 43. > All above your statement means is that NO ONE on the other distros has YET booted a 6.19.X kernel and NOTICED that it does not work and posted about it. It is not a definitive proof of anything except what I just stated. This is a kernel change that breaks the module, it is not a fedora specific change. The kernel makes this sort of change to make their code better in some manner all of the time and these sorts of changes break out-of-tree modules all of the time. -- ___ 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
Re: Fedora has broken VirtualBox with 6.19.6
On 12 Mar 2026 at 21:30, Richard Kimberly Heck wrote: Date sent: Thu, 12 Mar 2026 21:30:21 -0400 Subject:Re: Fedora has broken VirtualBox with 6.19.6 To: [email protected] From: Richard Kimberly Heck Send reply to: Community support for Fedora users > On 3/12/26 7:46 PM, Michael D. Setzer II via users wrote: > > Again the 6.18.16 kerenel works fine, but 6.19.6 kernel fails. So, it > > is something Fedora has done. > > Unless I'm mistaken, the problem is caused by changes within the kernel > itself, not by anything to do with Fedora. Responsibility to adapt to > those changes seems to lie with the authors of VirtualBox, since it is > the modules they need that will not build with the new kernel. > I've seen some pages that show if works with other distros, but specifically says it doesn't work with Fedora, and only option is to boot with 6.18.16 on Fedora at momment. Specifically said that Fedora was only allowing access to low level CPU functions to KVM, so the VirtualBox can not get the required access. Will have to see if they can update the akmods to allow it to build. Adding "Fedora" in search generally shows those links. Currently have 8 linux machines all running Fedora 43. I build kernels from kernel.org for my own project G4L Latest has bz6x19.7 bz7x0.rc3 Have no issues with those, but is not using beyond text display. Build in most disk and networking devices for disk imaging, and recently moved from initrd setup going to be phased out 1/2027? Found lots of bad info on how to fix that, but eventually only required like 3 minor line changes. Right now booting to 6.18.16 allows it to work. > Riki > > > -- > ___ > 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 ++ Michael D. Setzer II - Computer Science Instructor (Retired) mailto:[email protected] mailto:[email protected] mailto:[email protected] Guam - Where America's Day Begins G4L Disk Imaging Project maintainer http://sourceforge.net/projects/g4l/ ++ -- ___ 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
Re: Fedora has broken VirtualBox with 6.19.6
On 3/12/26 7:46 PM, Michael D. Setzer II via users wrote: Again the 6.18.16 kerenel works fine, but 6.19.6 kernel fails. So, it is something Fedora has done. Unless I'm mistaken, the problem is caused by changes within the kernel itself, not by anything to do with Fedora. Responsibility to adapt to those changes seems to lie with the authors of VirtualBox, since it is the modules they need that will not build with the new kernel. Riki -- ___ 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
Re: Fedora has broken VirtualBox with 6.19.6
On 12 Mar 2026 at 17:46, Samuel Sieb wrote: Date sent: Thu, 12 Mar 2026 17:46:09 -0700 Subject:Re: Fedora has broken VirtualBox with 6.19.6 To: Community support for Fedora users From: Samuel Sieb Send reply to: Community support for Fedora users > On 3/12/26 4:46 PM, Michael D. Setzer II wrote: > > Again the 6.18.16 kerenel works fine, but 6.19.6 kernel fails. So, it > > is something Fedora has done. Perhaps it will be fixed. But the one > > page had said Fedora had restricted things to KVM only, so > > virtualbox couldn't get access to the features required to build the > > akmods > > Why do you keep saying it's something Fedora did? All Fedora did was > update the kernel to 6.19. It's a problem with virtualbox, nothing > specific to Fedora. You're getting bad information or else > misinterpreting it. Don't understand your logic??? It works with 6.18.16 but doesn't work with 6.19.6 kernel. Nothing else changes. VirtualBox is the same.akmods is the same. Only variable in the situation is the changes from kernel 6.18.16 to 6.19.6. So, something was changed in the build of 6.19.6. 2nd why does attempt to remove 6.19.6 result in DNF wanting to remove/change 77 packages? Difference on boot entries. cat 5454d68084c145e496d5ce383b5147de-6.19.6-200.fc43.x86_64.conf 5454d68084c145e496d5ce383b5147de-6.18.16-200.fc43.x86_64.co nf title Fedora Linux (6.19.6-200.fc43.x86_64) 43 (Workstation Edition) version 6.19.6-200.fc43.x86_64 linux /vmlinuz-6.19.6-200.fc43.x86_64 initrd /initramfs-6.19.6-200.fc43.x86_64.img $tuned_initrd options root=UUID=de10a0a9-fd86-4625-a768-67477a8a802d ro rhgb quiet $tuned_params grub_users $grub_users grub_arg --unrestricted grub_class fedora title Fedora Linux (6.18.16-200.fc43.x86_64) 43 (Workstation Edition) version 6.18.16-200.fc43.x86_64 linux /vmlinuz-6.18.16-200.fc43.x86_64 initrd /initramfs-6.18.16-200.fc43.x86_64.img $tuned_initrd options root=UUID=de10a0a9-fd86-4625-a768-67477a8a802d ro rhgb quiet $tuned_params grub_users $grub_users grub_arg --unrestricted grub_class fedora 6.18.16 works 6.19.6 doesn't. So, how can you say it isn't something that Fedora did. The only idfference is the kernel and the initramfs from 18.16 to 19.6. > > -- > ___ > 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 ++ Michael D. Setzer II - Computer Science Instructor (Retired) mailto:[email protected] mailto:[email protected] mailto:[email protected] Guam - Where America's Day Begins G4L Disk Imaging Project maintainer http://sourceforge.net/projects/g4l/ ++ -- ___ 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
Re: Fedora has broken VirtualBox with 6.19.6
On 3/12/26 4:46 PM, Michael D. Setzer II wrote: Again the 6.18.16 kerenel works fine, but 6.19.6 kernel fails. So, it is something Fedora has done. Perhaps it will be fixed. But the one page had said Fedora had restricted things to KVM only, so virtualbox couldn't get access to the features required to build the akmods Why do you keep saying it's something Fedora did? All Fedora did was update the kernel to 6.19. It's a problem with virtualbox, nothing specific to Fedora. You're getting bad information or else misinterpreting it. -- ___ 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
Re: Fedora has broken VirtualBox with 6.19.6
On 12 Mar 2026 at 16:06, Samuel Sieb wrote: Date sent: Thu, 12 Mar 2026 16:06:42 -0700 Subject:Re: Fedora has broken VirtualBox with 6.19.6 To: Community support for Fedora users From: Samuel Sieb Send reply to: Community support for Fedora users > 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 > > > > From: Samuel Sieb > > Send reply to: Community support for Fedora users > > > > > >> 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 > >>> Send reply to:Community support for Fedora users > >>> > >>> > >>>> 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. As I had said, some time ago on another machine had tried the KVM with instruction that said it would convert the VirtualBox setup, and it totally didn't work. So opted to stick with something that worked for what I needed. Have a project that creates boot images that use syslinux, grub4dos bios, and grub4dos uefi. With Virtual box it works fine. Even with recent conversion from initrd to initramfs since kernel 6.17.x is reporting the initrd is going to go away in 1/2027. Again the 6.18.16 kerenel works fine, but 6.19.6 kernel fails. So, it is something Fedora has done. Perhaps it will be fixed. But the one page had said Fedora had restricted things to KVM only, so virtualbox couldn't get access to the features required to build the akmods So, perhaps rpmfusion with come up with an update that will allow the akmods to work. Just it was working fine, and now it isn't, and only change is the kernel that is booted. Thanks for your time, right now, just going to use 6.18.16 since it works and 6.19.6 does not. > > > 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
Re: Fedora has broken VirtualBox with 6.19.6
On 12 Mar 2026 at 22:40, C. Linus Hicks wrote: From: "C. Linus Hicks" To: Fedora Users Subject: Re: Fedora has broken VirtualBox with 6.19.6 Date sent: Thu, 12 Mar 2026 22:40:17 + Send reply to: Community support for Fedora users > On Thu, Mar 12, 2026, at 12:20 PM, Michael D. Setzer II via users wrote: > >> 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?? > >> > >> So, module can't build because of restriction Fedora just installed? > >> Perhaps they will find a way to get around issue with an update. > >> > >> So, works with 6.18.16 but fails with 6.19.6, so only change is > >> Fedora Kernel. So currently have to boot with 6.18.16 to have it > >> work? > >> > >> So change in 6.19.6 causes problem. > > > >Correct. The problem is that it is failing when trying to build the kernel > >modules for the 6.19 kernel. > > > >The was a "last straw" event for me. I have played with Qemu / KVM before > >was still using VirtualBox. I just re-installed KVM and created a fedora > >install. All well. I will next work on >converting some old Windows VMs and > >if that goes well I will fully un-install VirtualBox. > > > What version of VirtualBox are you running? rpm -qa | grep -i VirtualBox VirtualBox-kmodsrc-7.2.6-1.fc43.noarch VirtualBox-server-7.2.6-1.fc43.x86_64 VirtualBox-vnc-7.2.6-1.fc43.x86_64 kmod-VirtualBox-7.2.6-1.fc43.x86_64 VirtualBox-webservice-7.2.6-1.fc43.x86_64 VirtualBox-devel-7.2.6-1.fc43.x86_64 virtualbox-guest-additions-7.2.6-1.fc43.x86_64 kmod-VirtualBox-6.18.16-200.fc43.x86_64-7.2.6-1.fc43.x86_64 akmod-VirtualBox-7.2.6-1.fc43.x86_64 VirtualBox-7.2.6-1.fc43.x86_64 If I boot with kernel 6.18.16 Virtual Box works fine. If I boot with kernel 6.19.6 it tries to build akmods but it fails. manually running akmods fails. > > VirtualBox introduced initial support for Linux kernel 6.19 in VirtualBox > 7.2.6, released on January 28, 2026. This version includes the necessary > updates to handle changes to low-level CPU functions and kernel module > compilation required for the 6.19 kernel. > > Key Details on 6.19 Support: > * Initial Support: VirtualBox 7.2.6 is the first release to provide "initial > support" for the 6.19 kernel (which was officially released on Feb 8, 2026). > * Fixes: The update specifically addresses issues with compiling kernel > modules, which arise from stricter handling of low-level CPU functions (such > as the CR4 register) moved into a protected namespace in the 6.19 kernel. > > > This topic: https://forums.virtualbox.org/viewtopic.php?t=114417 > > Reports that the module build issue is fixed in 6.19.06 but I have not > verified this. > > > > -- > ___ > 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 ++ Michael D. Setzer II - Computer Science Instructor (Retired) mailto:[email protected] mailto:[email protected] mailto:[email protected] Guam - Where America's Day Begins G4L Disk Imaging Project maintainer http://sourceforge.net/projects/g4l/ ++ -- ___ 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
Re: Fedora has broken VirtualBox with 6.19.6
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 From: Samuel Sieb Send reply to: Community support for Fedora users 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 Send reply to: Community support for Fedora users 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
Re: Fedora has broken VirtualBox with 6.19.6
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 From: Samuel Sieb Send reply to: Community support for Fedora users > 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 > > Send reply to: Community support for Fedora users > > > > > >> 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. akmods Checking kmods exist for 6.19.6-200.fc43.x86_64[ OK ] Building and installing VirtualBox-kmod[FAILED] Building rpms failed; see /var/cache/akmods/VirtualBox/7.2.6-1-for-6.19.6-200.fc43.x86_64.fa iled.log for details Figured I just downgrade kernel to g back to 6.18.16 booted to 6.18.16-200.fc43.x86_64 # dnf downgrade kernel-core*6.19.6* Updating and loading repositories: Repositories loaded. The lowest available version of the "kernel-core.x86_64" package is already installed, cannot downgrade it. Nothing to do. tried to remove 6.19.6 and it comes with message that it is going to remove 77 packages?? dnf remove kernel*6.19.6* Package Arch Version Repository Size Removing: kernel x86_646.19.6-200.fc43 updates 0.0 B kernel-core x86_646.19.6-200.fc43 updates 98.9 MiB kernel-develx86_646.19.6-200.fc43 updates 87.5 MiB kernel-devel-matchedx86_646.19.6-200.fc43 updates 0.0 B kernel-headers x86_646.19.6-200.fc43 updates 6.9 MiB kernel-modules x86_646.19.6-200.fc43 updates 95.9 MiB kernel-modules-core x86_646.19.6-200.fc43 updates 70.6 MiB kernel-modules-extrax86_646.19.6-200.fc43 updates 4.2 MiB kernel-toolsx86_646.19.6-200.fc43 updates918.1 KiB kernel-tools-libs x86_646.19.6-200.fc43 updates 30.3 KiB Removing dependent packages: akmod-VirtualBoxx86_647.2.6-1.fc43 rpmfusion-free-updates 48.6 KiB akmods noarch0.6.2-9.fc43
Re: Fedora has broken VirtualBox with 6.19.6
On Thu, Mar 12, 2026, at 12:20 PM, Michael D. Setzer II via users wrote: >> 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?? >> >> So, module can't build because of restriction Fedora just installed? >> Perhaps they will find a way to get around issue with an update. >> >> So, works with 6.18.16 but fails with 6.19.6, so only change is >> Fedora Kernel. So currently have to boot with 6.18.16 to have it >> work? >> >> So change in 6.19.6 causes problem. > >Correct. The problem is that it is failing when trying to build the kernel >modules for the 6.19 kernel. > >The was a "last straw" event for me. I have played with Qemu / KVM before was >still using VirtualBox. I just re-installed KVM and created a fedora install. >All well. I will next work on >converting some old Windows VMs and if that >goes well I will fully un-install VirtualBox. What version of VirtualBox are you running? VirtualBox introduced initial support for Linux kernel 6.19 in VirtualBox 7.2.6, released on January 28, 2026. This version includes the necessary updates to handle changes to low-level CPU functions and kernel module compilation required for the 6.19 kernel. Key Details on 6.19 Support: * Initial Support: VirtualBox 7.2.6 is the first release to provide "initial support" for the 6.19 kernel (which was officially released on Feb 8, 2026). * Fixes: The update specifically addresses issues with compiling kernel modules, which arise from stricter handling of low-level CPU functions (such as the CR4 register) moved into a protected namespace in the 6.19 kernel. This topic: https://forums.virtualbox.org/viewtopic.php?t=114417 Reports that the module build issue is fixed in 6.19.06 but I have not verified this. -- ___ 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
Re: Fedora has broken VirtualBox with 6.19.6
On Thu, Mar 12, 2026, at 12:20 PM, Michael D. Setzer II via users wrote: > 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?? > > So, module can't build because of restriction Fedora just installed? > Perhaps they will find a way to get around issue with an update. > > So, works with 6.18.16 but fails with 6.19.6, so only change is > Fedora Kernel. So currently have to boot with 6.18.16 to have it > work? > > So change in 6.19.6 causes problem. Correct. The problem is that it is failing when trying to build the kernel modules for the 6.19 kernel. The was a "last straw" event for me. I have played with Qemu / KVM before was still using VirtualBox. I just re-installed KVM and created a fedora install. All well. I will next work on converting some old Windows VMs and if that goes well I will fully un-install VirtualBox. -- ___ 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
Re: Fedora has broken VirtualBox with 6.19.6
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 Send reply to: Community support for Fedora users 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. So, module can't build because of restriction Fedora just installed? Perhaps they will find a way to get around issue with an update. So, works with 6.18.16 but fails with 6.19.6, so only change is Fedora Kernel. So currently have to boot with 6.18.16 to have it work? So change in 6.19.6 causes problem. That's more likely to be a kernel change that the module needs to be adjusted for. And again, why aren't you just using the supplied VM anyway instead of trying to make virtualbox work? -- ___ 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
Re: Fedora has broken VirtualBox with 6.19.6
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 Send reply to: Community support for Fedora users > 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?? So, module can't build because of restriction Fedora just installed? Perhaps they will find a way to get around issue with an update. So, works with 6.18.16 but fails with 6.19.6, so only change is Fedora Kernel. So currently have to boot with 6.18.16 to have it work? So change in 6.19.6 causes problem. > -- > ___ > 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 ++ Michael D. Setzer II - Computer Science Instructor (Retired) mailto:[email protected] mailto:[email protected] mailto:[email protected] Guam - Where America's Day Begins G4L Disk Imaging Project maintainer http://sourceforge.net/projects/g4l/ ++ -- ___ 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
Re: Fedora has broken VirtualBox with 6.19.6
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. -- ___ 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
Re: Fedora has broken VirtualBox with 6.19.6
On 12 Mar 2026 at 12:09, Patrick O'Callaghan wrote: Subject: Re: Fedora has broken VirtualBox with 6.19.6 From: Patrick O'Callaghan To: [email protected] Date sent: Thu, 12 Mar 2026 12:09:37 + Send reply to: Community support for Fedora users > On Thu, 2026-03-12 at 21:44 +1000, Michael D. Setzer II via users > wrote: > > Tried to run VirtualBox and it fails with akmod issue. > > Found solutions for other distros, but only option for Fedora is to > > boot with an older kernel. > > > > Seems Fedora has restrict access to KVM thus not allowing > > VirtualBox to work? > > > > The error is caused by VirtualBox trying to use low-level CPU > > functions (CR4, TLB) now restricted to KVM > > > > akmods > > Checking kmods exist for 6.19.6-200.fc43.x86_64 [ OK ] > > Building and installing VirtualBox-kmod [FAILED] > > Building rpms failed; see > > /var/cache/akmods/VirtualBox/7.2.6-1-for-6.19.6-200.fc43.x86_64.fa > > iled.log for details > > > > Some things say to wait for rpmfusion to come up with update, but > > not sure how they can make a patch if Fedora has restricted to only > > KVM? > > What does the log actually say? First, I can confirm that booting with the previous 6.18.16-200.fc43.x86_64 kernel has VirtualBox opens fine. Sie of the log file is 18395 Mar 12 21:41 7.2.6-1-for-6.19.6-200.fc43.x86_64.failed.log /var/cache/akmods/VirtualBox$ wc -l 7.2.6-1-for-6.19.6-200.fc43.x86_64.failed.log 203 7.2.6-1-for-6.19.6-200.fc43.x86_64.failed.log 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. make[3]: *** [/usr/src/kernels/6.19.6-200.fc43.x86_64/scripts/Makefile.modpost:1 47: Module.symvers] Error 1 make[2]: *** [/usr/src/kernels/6.19.6-200.fc43.x86_64/Makefile:2044: modpost] Error 2 make[1]: *** [/usr/src/kernels/6.19.6-200.fc43.x86_64/Makefile:248: __sub-make] Error 2 make: *** [Makefile:248: __sub-make] Error 2 error: Bad exit status from /var/tmp/rpm-tmp.9rjfZf (%build) RPM build errors: 2026/03/12 21:41:53 akmodsbuild: + CFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -march=x86-64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -mtls-dialect=gnu2 -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer ' 2026/03/12 21:41:53 akmodsbuild: + CXXFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -march=x86-64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -mtls-dialect=gnu2 -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer ' 2026/03/12 21:41:53 akmodsbuild: + LDFLAGS='-Wl,-z,relro -Wl,--as-needed -Wl,-z,pack-relative-relocs -Wl,-z,now -specs=/usr/lib/rpm/redhat/redhat-hardened-ld -specs=/usr/lib/rpm/redhat/redhat-hardened-ld-errors -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -Wl,--build-id=sha1 -specs=/usr/lib/rpm/redhat/redhat-package-notes ' 2026/03/12 21:41:53 akmodsbuild: ERROR: modpost: module vboxdrv uses symbol cr4_update_irqsoff from namespace module:kvm,kvm-amd,kvm-intel, but does not import it. 2026/03/12 21:41:53 akmodsbuild: ERROR: modpost: module vboxdrv uses symbol cr4_read_shadow from namespace module:kvm,kvm-amd,kvm-intel, but does not import it. 2026/03/12 21:41:53 akmodsbuild: ERROR: modpost: module vboxdrv uses symbol __flush_tlb_all from namespace module:kvm,kvm-amd,kvm-intel, but does not import it. 2026/03/12 21:41:53 akmodsbuild: make[3]: *** [/usr/src/kernels/6.19.6-200.fc43.x86_64/scripts/Makefile.modpost:1 47: Module.symvers] Error 1 2026/03/12 21:41:53 akmodsbuild: make[2]: *** [/usr/src/kernels/6.19.6-200.fc43.x86_64/Makefile:2044: modpost] Error 2 2026/03/12 21:41:53 akmodsbuild: make[1]: *** [/usr/src/kernels/6.19.6-200.fc43.x86_64/Makefile:248: __sub-make] Error 2 2026/03/12 21:41:53 akmodsbuild: make: *** [Makefile:248: __s
Re: Fedora has broken VirtualBox with 6.19.6
On Thu, 2026-03-12 at 21:44 +1000, Michael D. Setzer II via users wrote: > Tried to run VirtualBox and it fails with akmod issue. > Found solutions for other distros, but only option for Fedora is to > boot with an older kernel. > > Seems Fedora has restrict access to KVM thus not allowing > VirtualBox to work? > > The error is caused by VirtualBox trying to use low-level CPU > functions (CR4, TLB) now restricted to KVM > > akmods > Checking kmods exist for 6.19.6-200.fc43.x86_64 [ OK ] > Building and installing VirtualBox-kmod [FAILED] > Building rpms failed; see > /var/cache/akmods/VirtualBox/7.2.6-1-for-6.19.6-200.fc43.x86_64.fa > iled.log for details > > Some things say to wait for rpmfusion to come up with update, but > not sure how they can make a patch if Fedora has restricted to only > KVM? What does the log actually say? poc -- ___ 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
