kernel-6.12.1 breaks VirtualBox hosts by default
Ian Laurie via test <[email protected]>
| Newsgroups | gmane.linux.redhat.fedora.testers |
|---|---|
| Message-ID | <[email protected]> |
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 -- _______________________________________________ test 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://pagure.io/fedora-infrastructure/new_issue