Warning for VirtualBox users and Kernel 6.12

English Virtualization
,
1

VirtualBox 7.1.4 has support for Kernel 6.12 but you have to include a parameter to the kernel command line in the bootup or VirtualBox will not start.

kvm.enable_virt_at_load=0

I added it to /etc/default/grub

I got this from Linux Magazine January 2025 issue.

8 Likes
2

Thank you Larryr; very helpful heads-up…

3

Agreed; I might have lost hours on needless troubleshooting on today’s DUP to the 20241220 snapshot if I hadn’t seen this post. Thank you, Larryr.

1 Like
4

this is a kernel parameter or do you add the line to anywhere in /etc/default/grub ? and thank you

5

Yes, it is a kernel parameter to be added to GRUB_CMDLINE_LINUX_DEFAULT=

1 Like
6

Hello,
I have the error message

VM Name: Win10

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 I added your kernel parameter to /etc/default/grub.

The line is now:

GRUB_CMDLINE_LINUX_DEFAULT=“splash=silent quiet security=apparmor mitigations=off kvm.enable_virt_at_load=0”

But when trying to start Virtualbox, I still get the same error message.
Any ideas?

My computer configuration is:

Operating System: openSUSE Tumbleweed 20241222
KDE Plasma Version: 6.2.4
KDE Frameworks Version: 6.9.0
Qt Version: 6.8.1
Kernel Version: 6.12.6-1-default (64-bit)
Graphics Platform: Wayland
Processors: 16 Ă— AMD Ryzen 7 7840HS with Radeon 780M Graphics
Memory: 13,3 GiB of RAM
Graphics Processor: AMD Radeon 780M
Manufacturer: LENOVO
Product Name: 83AM
System Version: IdeaPad Pro 5 14APH8

Thanks,
Johannes

7

Did you recreate initrd? When you manually add the parameter to the grub file, you need to run dracut. If you use YaST Bootloader instead, it is done automatically.

8

No, when you manually add parameters to the grub file, you need to run update-bootloader --config.

2 Likes
9

Thanks to “hui” and “arvidjaar”
After updating the bootloader it works again… (in my case, I used yast).

Thanks,
Johannes

10

Hello everyone.
I’ve been testing in vm virtualbox, for about 15 days, Debian Trixie (testing) and Fedora 41 Mate both with kernel 6.12.5.
Neither of the 2 has problems.

I take this opportunity to wish everyone my best
Merry Christmas and a happy new year!!! :grinning: :grinning:
Bye

11

Same problem, updating bootloader and it’s work again, thanks for the tip

12

I added kvm.enable_virt_at_load=0 in YaST under System -> Boot loader and now it says “The VM session was aborted. NS_ERROR_FAILURE (0x80004005)”.

image

image

13

works for me too.
thanks

14

OMG, what a mess…

Can/should this kernel parameter be removed in the future?

1 Like