You are not logged in.
Morning,
today I upgraded to kernel 6.12.arch1-1 and virtualbox-host-modules-arch 7.1.4-10 from testing and my virtualbox installation stopped working with the following error:
VirtualBox can't enable the AMD-V extension. Please disable the KVM kernel extension, recompile your kernel and reboot (VERR_SVM_IN_USE)
downgrading to kernel 6.11.9.arch1-1 and virtualbox-host-modules 7.1.4-9 solved the issue. AMD-V is enabled in BIOS and no BIOS settings were changed at all.
Any ideas?
Last edited by Harey (2024-11-24 09:12:32)
Linux is like a wigwam: No Gates, no Windows and an Apache inside
Offline
Anybody can give it a test with Intel hardware? I guess it is the same there...
And anybody can try with boot parameter
kvm.enable_virt_at_load=0
? Guess that prevents the issue, not sure about side effects.
ArchLinux - make it simple & lightweight
Offline
Anybody can give it a test with Intel hardware? I guess it is the same there...
And anybody can try with boot parameter
kvm.enable_virt_at_load=0
? Guess that prevents the issue, not sure about side effects.
can confirm boot param works on amd, no obvious side effects from the outset.
Offline
Hey, sorry for the late answer but I can also confirm that virtualbox works on 6.12. with
kvm.enable_virt_at_load=0
enabled.
Does this mean I have to keep this in my grub.cfg from now on or will the kernel config be changed?
Greetings
Harvey
Linux is like a wigwam: No Gates, no Windows and an Apache inside
Offline
No. Drop that boot parameter, then update your system and make sure virtualbox 7.1.4-2 is included.
ArchLinux - make it simple & lightweight
Offline
Confirmed. Removed boot parameter and all works as it should out-of-the-box. Thank you! Setting topic to 'Solved'
Last edited by Harey (2024-11-24 09:12:51)
Linux is like a wigwam: No Gates, no Windows and an Apache inside
Offline
No. Drop that boot parameter, then update your system and make sure virtualbox 7.1.4-2 is included.
I'm also issue on AMD, Zen 3 with qemu+kvm under linux-zen 6.12.
Downgrading to 6.11.9 solves the issue.
I have CPU cores isolated for the VM. Those lock at 100% usage when Windows starts booting in the VM, and new processes don't spawn until I force the VM off.
Boot parameter did not help.
Looks to be unrelated, sorry for spam. I may make a new thread.
Last edited by Ranguvar (Yesterday 19:47:48)
Offline