Fix VirtualBox "can't operate in VMX root mode" when KVM is loaded
The kernel-parameters.txt entry for kvm.enable_virt_at_load matches the record. Arch virtualbox is 7.2.20. The 7.2 changelog has 7.2.2 (released September 10 2025) with "Use KVM APIs on kernel 6.16.0 and newer for acquiring/releasing VT-x", which covers Intel only. VirtualBox issue #81, about VERR_SVM_IN_USE on AMD, has a maintainer comment from 2025-12-12 saying the AMD fix was backported to 7.2.x for the next maintenance release, which was 7.2.6 on 2026-01-20. A user then confirmed AMD working on 7.2.6 with kernel 6.17 and the dmesg line vboxdrv: Enabled hardware-virtualization using KVM. So the version floor for AMD is 7.2.6, not 7.2.2. The cause and fix are corrected for that. limine-mkinitcpio exists and omarchy-windows-vm exists, so the rest stands. Second audit confirmed the corrected text: The earlier correction holds and is restated so it survives: the AMD-V floor is VirtualBox 7.2.6, not 7.2.2. Re-checked VirtualBox issue #81 in full: maintainer ramshven on 2025-09-17 says the 7.2.2 fix covers Intel only and that the KVM API needed is exported only from kernel 6.16.0, on 2025-12-12 says the AMD fix was backported to 7.2.x for the next maintenance release, and a user on 2026-02-06 shows 7.2.6 r172322 on kernel 6.17 logging 'vboxdrv: Enabled hardware-virtualization using KVM'. The 7.2 changelog dates 7.2.2 to September 10 2025 and 7.2.6 to January 20 2026, with the 7.2.2 entry 'Use KVM APIs on kernel 6.16.0 and newer for acquiring/releasing VT-x'. Arch's virtualbox package is 7.2.20-1 (archlinux.org JSON). On this workstation /sys/module/kvm/parameters/enable_virt_at_load exists and reads Y, limine-mkinitcpio exists, omarchy_hooks.conf includes modconf so a modprobe.d option is carried into the UKI, and omarchy-windows-vm mounts /dev/kvm, so the warning against blacklisting kvm stands. Not exercised: VirtualBox is not installed here.
Symptom
Every VirtualBox VM refuses to start after a kernel update:
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).
On AMD the same thing reads VirtualBox can't enable the AMD-V extension. Please disable the KVM kernel extension, recompile your kernel and reboot (VERR_SVM_IN_USE). libvirt VMs work fine.
Cause
Since Linux 6.12, KVM enables hardware virtualization as soon as kvm_intel or kvm_amd loads (kvm.enable_virt_at_load defaults to on), so VirtualBox finds VT-x or AMD-V already taken. On kernel 6.16 and newer VirtualBox acquires virtualization through KVM's API instead: for Intel VT-x from 7.2.2 (released 2025-09-10), and for AMD-V from 7.2.6 (released 2026-01-20), after the fix tracked in VirtualBox issue #81. Current Arch (virtualbox 7.2.20, kernel 7.x) therefore no longer hits this. Seeing it now means a kernel older than 6.16, or VirtualBox older than 7.2.2 on Intel or older than 7.2.6 on AMD (a pinned package, an AUR binary build or Oracle's installer).
Fix
Check what you are running:
VBoxManage --version
uname -r
journalctl -k -b | grep vboxdrv # 'Enabled hardware-virtualization using KVM' means the new path works
The real fix is to update so you have kernel 6.16 or newer and VirtualBox 7.2.2 or newer on Intel, 7.2.6 or newer on AMD. Omarchy 4: omarchy update. Plain Arch: sudo pacman -Syu. Then reboot.
If you must stay on an old VirtualBox, stop KVM grabbing virtualization at load. KVM still works, it enables virtualization only while a KVM VM is running, so you just cannot run both at once:
echo 'options kvm enable_virt_at_load=0' | sudo tee /etc/modprobe.d/kvm-virtualbox.conf
sudo limine-mkinitcpio # Omarchy 4: rebuild the UKI in case kvm is in the initramfs
sudo mkinitcpio -P # plain Arch instead
Reboot. For the current boot only: sudo modprobe -r kvm_intel (or kvm_amd), which fails while a KVM VM is running.
Do not blacklist kvm as old guides say. Omarchy's Windows VM (omarchy-windows-vm), libvirt and the Android emulator all need it.
Verify
cat /sys/module/kvm/parameters/enable_virt_at_load prints N if you used the option, and a VirtualBox VM starts. On an updated system, journalctl -k -b | grep vboxdrv shows Enabled hardware-virtualization using KVM.
Sources
- https://forums.virtualbox.org/viewtopic.php?t=112828
- https://www.virtualbox.org/wiki/Changelog
- https://github.com/VirtualBox/virtualbox/issues/81
- https://raw.githubusercontent.com/torvalds/linux/master/Documentation/admin-guide/kernel-parameters.txt
- https://wiki.archlinux.org/title/VirtualBox
- https://archlinux.org/packages/extra/x86_64/virtualbox/
- https://www.virtualbox.org/wiki/Changelog-7.2