You are not logged in.
Pages: 1
Today I've updated my pc and I've got this kernel panic at when virtualbox machine is automatically started at boot. Reverting virtualbox from 7.2.10 to 7.2.8 solves the issue.
https://panic.archlinux.org/panic_repor … 3852379505
This is the panic on another pc https://panic.archlinux.org/panic_repor … 3864352881
Last edited by Xwang (2026-06-17 06:36:03)
Offline
[ 8.183285] ? rtmpLinuxAllWrapper+0x52/0x70 [vboxdrv dea7de75ea5ed2c85657bf447ed9da7772030467]Maybe related to vboxdrv module. Do you use virtualbox-host-modules-arch or virtualbox-host-dkms?
Offline
[ 8.183285] ? rtmpLinuxAllWrapper+0x52/0x70 [vboxdrv dea7de75ea5ed2c85657bf447ed9da7772030467]Maybe related to vboxdrv module. Do you use virtualbox-host-modules-arch or virtualbox-host-dkms?
I use the virtualbox-host-dkms , I'm pretty sure it is related to this and I think I have to revert virtualbox because indeed the 7.0.11 and lts only work if the virtualbox is not installed
Offline
It is not the kernel, it is virtualbox!!!! Reverting to 7.2.8 solves the kernel panic. I've updated title and first message.
Last edited by Xwang (2026-06-16 22:27:06)
Offline
You're not alone... see https://forums.virtualbox.org/viewtopic.php?p=558412
Offline
Can you work around the issue with 7.2.10 by in VM Settings -> System -> Processor tab and uncheck "Enable Nested VT-x/AMD-V" or by blacklisting kvm_intel?
Edit:
https://gitlab.archlinux.org/archlinux/ … k_items/15
https://github.com/VirtualBox/virtualbox/issues/711
Last edited by loqs (2026-06-16 23:42:16)
Offline
Can you work around the issue with 7.2.10 by in VM Settings -> System -> Processor tab and uncheck "Enable Nested VT-x/AMD-V" or by blacklisting kvm_intel?
Edit:
https://gitlab.archlinux.org/archlinux/ … k_items/15
https://github.com/VirtualBox/virtualbox/issues/711
Unchecking "Enable Nested VT-x/AMD-V" does not solve the issue. Is blacklisting kvm_intel meant to to do the same or should I try that too?
Offline
sorry for this semi-hijack: with linux come with kvm out of the box is there any reason to use anything else but kvm like vbox or vmware?
do they offer something kvm can't do?
Offline
same here last night got major disaster of kernel panic bootloader all because play with vm settings and power off machine
Offline
Same issue here with virtualbox 7.2.10-1 and virtualbox-host-modules-arch on kernel 7.0.12-arch1-1 (Intel CPU).
Launching any VM causes an instant host hard freeze due to a conflict with KVM, even when no KVM guests are active.
Temporary workaround to unload KVM before starting VirtualBox:
sudo rmmod kvm_intel kvmOffline
so I think that best solution at this moment is to wait for fix with new version of Virtualbox?
Offline
so I think that best solution at this moment is to wait for fix with new version of Virtualbox?
7.2.10-2 contains https://gitlab.archlinux.org/archlinux/ … 0f97f6305a.
Last edited by loqs (2026-06-17 14:31:12)
Offline
Actually, after having kvm_amd and kvm disabled at boot for as long as I can remember (cmdline option
kvm.enable_virt_at_load=0I've now had to flip it to
kvm.enable_virt_at_load=1to get virtualbox working.
Ryzen 5900X 12 core/24 thread - RTX 3090 FE 24 Gb, Asus B550-F Gaming MB, 128Gb Corsair DDR4, Fractal Design Define 7 XL, 5 HD (2 NvME PCI, 4SSD) + 1 x optical.
Linux user #545703
/ is the root of all problems.
Offline
Actually, after having kvm_amd and kvm disabled at boot for as long as I can remember (cmdline option
kvm.enable_virt_at_load=0I've now had to flip it to
kvm.enable_virt_at_load=1to get virtualbox working.
Offline
virtualbox 7.2.10-3 fixed issue
Last edited by infoslaw (2026-06-17 22:19:47)
Offline
Roken wrote:Actually, after having kvm_amd and kvm disabled at boot for as long as I can remember (cmdline option
kvm.enable_virt_at_load=0I've now had to flip it to
kvm.enable_virt_at_load=1to get virtualbox working.
I'd missed that. Removing it completely from the kernel options works just fine.
Thank you.
Ryzen 5900X 12 core/24 thread - RTX 3090 FE 24 Gb, Asus B550-F Gaming MB, 128Gb Corsair DDR4, Fractal Design Define 7 XL, 5 HD (2 NvME PCI, 4SSD) + 1 x optical.
Linux user #545703
/ is the root of all problems.
Offline
Nice. Virtualbox-7.2.10-2 worked just fine, but virtualbox-7.2.10-3 now prevents any VM from starting, whining about kvm modules. What the h*** the -3 version was supposed to fix?
Offline
Nice. Virtualbox-7.2.10-2 worked just fine, but virtualbox-7.2.10-3 now prevents any VM from starting, whining about kvm modules. What the h*** the -3 version was supposed to fix?
Please post the command you are using and all the output it generates also the output of `lsmod`
Offline
Solved after a second Pacman -Syu
I think I have the same problem, kernel module mismatch. But I have reinstalled virtualbox and kernel modules
lsmod output:
serio_raw 20480 0
vboxnetflt 45056 0
vboxnetadp 28672 0
vboxdrv 700416 2 vboxnetadp,vboxnetflt
kvm_amd 258048 0
ccp 221184 1 kvm_amd
kvm 1474560 1 kvm_amdThanks
Last edited by gorneman (2026-06-21 17:23:35)
Offline
cyberpunkrocker wrote:Nice. Virtualbox-7.2.10-2 worked just fine, but virtualbox-7.2.10-3 now prevents any VM from starting, whining about kvm modules. What the h*** the -3 version was supposed to fix?
Please post the command you are using and all the output it generates also the output of `lsmod`
Sorry I've been AFK for the weekend.
Trying to start a VM from the virtualbox gui, I get this popup with an error:
AMD-V is being used by another hypervisor (VERR_SVM_IN_USE).
VirtualBox can't enable the AMD-V extension. Please disable the KVM kernel extension, recompile your kernel and reboot (VERR_SVM_IN_USE).
Result Code:
NS_ERROR_FAILURE (0x80004005)
Component:
ConsoleWrap
Interface:
IConsole {6ac83d89-6ee7-4e33-8ae6-b257b2e81be8}and of course, all the kvm modules are loaded. Virtualbox-7.2.10-2 had nice scripts which prevented kvm modules from being loaded, but these were removed from 7.2.10-3, breaking virtualbox Why?
Offline
and of course, all the kvm modules are loaded. Virtualbox-7.2.10-2 had nice scripts which prevented kvm modules from being loaded, but these were removed from 7.2.10-3, breaking virtualbox Why?
Offline
Yeah, I had read that gitlab entry alrady. So where's the actual fix? Or does the 'fix' work only on official Arch kernels?
Offline
Yeah, I had read that gitlab entry alrady.
Why would you post asking why the change was made when you had already ready the commit message documenting the reason for the change? You do not believe the commit message?
So where's the actual fix? Or does the 'fix' work only on official Arch kernels?
An issue was reported on Arch's gitlab instance. That issue was fixed. Have you opened such an issue?
Offline
Pages: 1