Warning for VirtualBox users and Kernel 6.12 - This may also apply to VMWARE

On Friday 2024-12-06 17:12, Larry Len Rainey wrote:
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 got this from Linux Magazine January 2025 issue.
The parameter is not needed in v6.12.6. If anything, it must have been fixed already (probably in 6.12.2).

Am Dienstag, 24. Dezember 2024, 12:41:21 Mitteleuropäische Normalzeit schrieb Jan Engelhardt:
The parameter is not needed in v6.12.6. If anything, it must have been fixed already (probably in 6.12.2).
Interesting but I somehow doubt that: Just two days ago I installed current Slowroll as a Virualbox VM, still under kernel 6.11.8 Yesterday I zypper dup'ed and rebooted to kernel 6.12.6. This morning, when trying to launch the Slowroll VM it refused to start with an error about AMD-V and KVM which lead me to finding a workaround using the named kernel option. Another reboot and the VM started up just fine. Cheers and happy holidays, Edgar

Season greetings to all I am running a couple of up to date SlowRoll installations[1] as clients on an up to date TW host[2] . The host machine is all AMD. [1] Operating System: openSUSE Tumbleweed-Slowroll 20241202 KDE Plasma Version: 6.2.4 KDE Frameworks Version: 6.8.0 Qt Version: 6.8.0 Kernel Version: 6.11.8-1-default (64-bit) Graphics Platform: X11 Processors: 2 × AMD Ryzen 9 5900HX with Radeon Graphics Memory: 2.9 Gio of RAM Graphics Processor: llvmpipe Manufacturer: innotek GmbH Product Name: VirtualBox System Version: 1.2 [2] 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: X11 Processors: 16 × AMD Ryzen 9 5900HX with Radeon Graphics Memory: 30.8 Gio of RAM Graphics Processor: AMD Radeon Graphics Manufacturer: ASUSTeK COMPUTER INC. Product Name: ROG Strix G513QY_G513QY System Version: 1.0 After updating my host machine to kernel Version: 6.12 when I run VirtualBox Version 7.1.4_SUSE r165100 and try to start the SlowRoll cients I get the following message : ### Powering VM up ... VirtualBox can't enable the AMD-V entension. Please disable the KVM kerenel extension, recompile your kernel and reboot. ### If I revert to a previous snapshot[3] on the host machine everything works fine... [3] # uname -r 6.11.8-1-default Any ideas ? Kind Regards James

Everything similar except intel MB: Micro-Star International Co., Ltd.Product Name: MPG Z790 EDGE WIFI (MS-7D91) and CPU 13th Gen Intel(R) Core(TM) i7-13700KF. VirtualBox works fine. VirtualBox Graphical User Interface Version 7.1.4_SUSE r165100 © 2004-2025 Oracle and/or its affiliates (Qt6.8.1)

On 12/24/24 7:09 AM, Edgar Aichinger via openSUSE Factory wrote:
Am Dienstag, 24. Dezember 2024, 12:41:21 Mitteleuropäische Normalzeit schrieb Jan Engelhardt:
The parameter is not needed in v6.12.6. If anything, it must have been fixed already (probably in 6.12.2).
Interesting but I somehow doubt that:
Just two days ago I installed current Slowroll as a Virualbox VM, still under kernel 6.11.8 Yesterday I zypper dup'ed and rebooted to kernel 6.12.6. This morning, when trying to launch the Slowroll VM it refused to start with an error about AMD-V and KVM which lead me to finding a workaround using the named kernel option. Another reboot and the VM started up just fine.
Cheers and happy holidays,
Edgar
The kernel parameter never worked for me, even now with current release. Blacklisting the module has worked and is still needed to run virtualbox.

Thank you! Removed it and virtual box works like a charm. -------- Ursprüngliche Nachricht -------- Von: Jan Engelhardt <ej@inai.de> An: Larry Len Rainey <llrainey15@gmail.com> Kopie: Factory <factory@lists.opensuse.org> Betreff: Re: Warning for VirtualBox users and Kernel 6.12 - This may also apply to VMWARE Datum: 24.12.2024 12:41:21 On Friday 2024-12-06 17:12, Larry Len Rainey wrote:
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 got this from Linux Magazine January 2025 issue.
The parameter is not needed in v6.12.6. If anything, it must have been fixed already (probably in 6.12.2).

Remove it and the problem persists in my system. Running 6.12.6-1. The kernel parameter 'kvm.enable_virt_at_load=0' still needed in my system. Happy Holidays to everyone and best wishes for the fast approaching New Year!!!

On Wednesday 25 December 2024, Jose Sanz wrote:
Remove it and the problem persists in my system. Running 6.12.6-1. The kernel parameter 'kvm.enable_virt_at_load=0' still needed in my system.
Happy Holidays to everyone and best wishes for the fast approaching New Year!!!
Same with me. Unless I add the kernel parameter I get the AMD-V error message from the VirtualBox manager on starting a VM. Tumbleweed 20241224 AMD Ryzen 5 5600 TUF GAMING B550-PLUS WIFI II GeForce GTX 1650 SUPER driver: nvidia v: 550.135 BOOT_IMAGE=/boot/vmlinuz-6.12.6-1-default root=UUID=453caaf5-5fed-43d8-b823-58f4ded3ab63 resume=/dev/disk/by-label/swap splash=silent quiet showopts libata.force=2.00:noncq acpi_enforce_resources=lax kvm.enable_virt_at_load=0 mitigations=auto Ditto on the New Year too. Michael

On Tuesday 2024-12-24 12:41, Jan Engelhardt wrote:
On Friday 2024-12-06 17:12, Larry Len Rainey wrote:
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 got this from Linux Magazine January 2025 issue.
The parameter is not needed in v6.12.6. If anything, it must have been fixed already (probably in 6.12.2).
JFYI, what I *did* just notice now however was, that starting a VM may just abort: Out of memory condition when allocating memory with low physical backing. (VERR_NO_LOW_MEMORY). Result Code: NS_ERROR_FAILURE (0x80004005) Component: ConsoleWrap Interface: IConsole {6ac83d89-6ee7-4e33-8ae6-b257b2e81be8} Which is weird in its own right, because LOWMEM is usually a thing under 32-bit mode OSes, but not x86_64 Long Mode. This simply happens after reading a lot of big files from disk, and can equally be "cured" by echo 3 >/proc/sys/vm/drop_caches or other methods of dropping the cache, e.g. umounting the fs. VBox is weird...

On Tuesday 2024-12-24 12:41, Jan Engelhardt wrote:
On Friday 2024-12-06 17:12, Larry Len Rainey wrote:
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 got this from Linux Magazine January 2025 issue.
The parameter is not needed in v6.12.6. If anything, it must have been fixed already (probably in 6.12.2).
Thanks to https://bugzilla.suse.com/show_bug.cgi?id=1231018 , I never booted into the new kernel. *sigh* Time to deinstall that graphic grub2. _Now_ I run into the VMX error. Bugs, bugs everywhere /wave

Am 26.12.24 um 02:49 schrieb Jan Engelhardt:
Time to deinstall that graphic grub2.
echo 'GRUB_DISABLE_SUBMENU=y GRUB_TERMINAL="console"' >> /etc/default/grub should be enough ;-) (at least to let you see easily what you are booting). -- Stefan Seyfried "For a successful technology, reality must take precedence over public relations, for nature cannot be fooled." -- Richard Feynman

Snapshot 20250101 solved the problem. No need for the kernel parameter 'kvm.enable_virt_at_load=0' any longer.
participants (10)
-
Craig Andersen
-
Edgar Aichinger
-
GMX
-
Jan Engelhardt
-
Jose Sanz
-
Larry Len Rainey
-
lulis@actcom.net.il
-
Michael Hamilton
-
pralofish45@mailfence.com
-
Stefan Seyfried