The latest test day kernel-6.12.1-200.fc41.x86_64 was working great for me until I tried to launch a VirtualBox VM.
"VirtualBox can't operate in VMX root mode. Please disable the KVM kernel extension, recompile your kernel and reboot (VERR_VMX_IN_VMX_ROOT_MODE)."
Recompile you kernel? After I picked myself off the floor and did some searching I came across a fix that seems to work. Fix is to type the following:
sudo modprobe -r kvm_intel
This allows VirtualBox to work however it breaks launching QEMU/KVM virtual machines until you undo it with this:
sudo modprobe kvm_intel
This is a bit nasty. If I boot kernel-6.11.10 I can run VirtualBox and QEMU/KVM VMs no problem (obviously not at the same time).
Is this expected behavior with 6.12 or is it somehow specific to me?
Can't we have the module unloaded *by default* and have QEMU/KVM load it as required? Then unload it when the last VM exits? Seems useless having it loaded all the time, especially since it breaks VirtualBox.
-- Ian Laurie FAS: nixuser | IRC: nixuser TZ: Australia/Sydney
On 30/11/24 18:50, Ian Laurie via test wrote:
Is this expected behavior with 6.12 or is it somehow specific to me?
Can't we have the module unloaded *by default* and have QEMU/KVM load it as required? Then unload it when the last VM exits? Seems useless having it loaded all the time, especially since it breaks VirtualBox.
Not just me.
Upstream bug:
https://www.virtualbox.org/ticket/22248
Worth reading the kernel thread:
https://lore.kernel.org/kvm/ZwQjUSOle6sWARsr@google.com/T/
This just makes life more difficult for a regular user.
-- Ian Laurie FAS: nixuser | IRC: nixuser TZ: Australia/Sydney
On Sunday, December 1st, 2024 at 4:28 PM, Ian Laurie via test test@lists.fedoraproject.org wrote:
On 30/11/24 18:50, Ian Laurie via test wrote: Not just me.
Upstream bug:
https://www.virtualbox.org/ticket/22248
Worth reading the kernel thread:
https://lore.kernel.org/kvm/ZwQjUSOle6sWARsr@google.com/T/
This just makes life more difficult for a regular user.
-- Ian Laurie FAS: nixuser | IRC: nixuser TZ: Australia/Sydney
It isn't uncommon for a new kernel to break VirtualBox, requiring it to need to be updated. Should Fedora hold back a newer kernel for third-party software they don't ship? I don't think so. I use the native hypervisor that has been part of the Linux kernel since 2007 which doesn't break because of kernel updates. I realize VirtualBox has some features that KVM doesn't have and vice versa... but it isn't that difficult for a VirtualBox user to hold back on a kernel update until VirtualBox gets updated. You'll get used to it.
-- TYL,Scott Dowdle (406) 750-3319 [cell] (406) 994-3931 [work]
On 2/12/24 10:37, Scott Dowdle via test wrote: versa... but it isn't that difficult for a VirtualBox user to hold back on a kernel update until VirtualBox gets updated. You'll get used to it.
This is a lot more serious that the *routine* host kernel compatibility problems that happen in new kernel streams (that I am well used to). Those get fixed very promptly.
I would be surprised if this gets fixed any time soon.
-- Ian Laurie FAS: nixuser | IRC: nixuser TZ: Australia/Sydney
On Monday, December 2, 2024, Ian Laurie via test < test@lists.fedoraproject.org> wrote:
On 2/12/24 10:37, Scott Dowdle via test wrote: versa... but it isn't that difficult for a VirtualBox user to hold back on a kernel update until VirtualBox gets updated. You'll get used to it.
This is a lot more serious that the *routine* host kernel compatibility problems that happen in new kernel streams (that I am well used to). Those get fixed very promptly.
I would be surprised if this gets fixed any time soon.
Well, there is a workaround which restores the old behavior and the suggestion from the upstream thread of adding a modprobe snippet to the virtual box rpm also sounds reasonable.
-- Ian Laurie FAS: nixuser | IRC: nixuser TZ: Australia/Sydney -- _______________________________________________ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-leave@lists.fedoraproject.org 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.or g/archives/list/test@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infra structure/new_issue
-
drago01 -
Ian Laurie -
Scott Dowdle