[RESOLVED] Upgraded to 6.12.1 with problem virtualbox
OengusOiw
Status: New User - Welcome
Joined: 02 Dec 2024
Posts: 2
Reply Quote
Hi,
After upgrade to 6.12.1, i have this error to virtualbox :
---------------------------------------------------
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).
Result Code:
NS_ERROR_FAILURE (0X80004005)
Component:
ConsoleWrap
Interface:
IConsole {6ac83d89-6ee7-4e33-8ae6-b257b2e81be8}
-------------------------------------------------
My Virtual machine don't start.
Is it possible to do something?
Please.
Back to top
Insurgent
Status: Curious
Joined: 02 Dec 2024
Posts: 7
Reply Quote
Try add to grub:

:: Code ::
kvm.enable_virt_at_load=0


https://bbs.archlinux.org/viewtopic.php?id=301155
Back to top
OengusOiw
Status: New User - Welcome
Joined: 02 Dec 2024
Posts: 2
Reply Quote
How can I integrate it?

I am a newbie in grub.
Back to top
Insurgent
Status: Curious
Joined: 02 Dec 2024
Posts: 7
Reply Quote
In this case, the first step is to provide the information requested here: https://techpatterns.com/forums/about3030.html.

On the other hand I would recommend you to wait and stay with kernel 6.11, many of these bugs are fixed with time. Modifying kernel parameters without knowing what you are doing may cause your computer to not boot at all.

The following may help others who have sufficient knowledge:
https://lore.kernel.org/kvm/ZwQjUSOle6sWARsr@google.com/T/

*** To clarify this is not a bug nor is it related to liquorix, it is a new feature of the 6.12 kernel version.
Back to top
damentz
Status: Assistant
Joined: 09 Sep 2008
Posts: 1143
Reply Quote
Most systems use the same filesystem layout for grub. With that in mind, you'll want to edit /etc/default/grub.

Update the value for GRUB_CMDLINE_LINUX_DEFAULT to include kvm.enable_virt_at_load=0.

Run sudo update-grub or sudo grub-mkconfig -o /boot/grub/grub.cfg.

I'll mark this thread as resolved as the workaround is pretty straightforward.
Back to top
stevenpusser
Status: Contributor
Joined: 14 Jan 2017
Posts: 90
Reply Quote
We've been looking for a simpler way at MX...

Create text file /etc/modules.d/kvm.conf containing

options kvm enable_virt_at_load=0


and reboot.

kvm module will still load when it's run, it's just not "dog in the manger" blocking the others. I was going to patch the code in the kernel to turn that off, but the next line defined the param, and I thought, "Well, of course!" Will work on other 6.12+ kernels, too.[/code]
:: Code ::

Back to top
DeepDayze
Status: Contributor
Joined: 21 May 2009
Posts: 137
Reply Quote
:: stevenpusser wrote ::
We've been looking for a simpler way at MX...

Create text file /etc/modules.d/kvm.conf containing

options kvm enable_virt_at_load=0


and reboot.

kvm module will still load when it's run, it's just not "dog in the manger" blocking the others. I was going to patch the code in the kernel to turn that off, but the next line defined the param, and I thought, "Well, of course!" Will work on other 6.12+ kernels, too.[/code]
:: Code ::


I've tried this workaround as well and it does not work for me and running 6.12.3.
Back to top
DeepDayze
Status: Contributor
Joined: 21 May 2009
Posts: 137
Reply Quote
The grub kernel command line workaround worked to allow vbox to work on 6.12. I think for some reason putting a file in modules.d to disable the builtin KVM doesn't work for 6.12 or that the option line is incorrect in that kvm.conf file.

Looks like Vbox 7.1.4 will correct this issue but the workaround can remain until 7.1.4 becomes available in Unstable.
Back to top
stevenpusser
Status: Contributor
Joined: 14 Jan 2017
Posts: 90
Reply Quote
:: DeepDayze wrote ::
The grub kernel command line workaround worked to allow vbox to work on 6.12. I think for some reason putting a file in modules.d to disable the builtin KVM doesn't work for 6.12 or that the option line is incorrect in that kvm.conf file.

Looks like Vbox 7.1.4 will correct this issue but the workaround can remain until 7.1.4 becomes available in Unstable.


That is odd, since everyone that's tried it on the Debian-based MX 21 and 23 distros reports that it does work, including me. ¯\_(?)_/¯
Back to top
CatManDan
Status: New User - Welcome
Joined: 11 Dec 2024
Posts: 1
Reply Quote
The path here is wrong. It should be /etc/modprobe.d/kvm.conf, not /etc/modules.d/kvm.conf

The content is still:

:: Code ::
options kvm enable_virt_at_load=0


With that, my system still is able to use Virtualbox w/o having to do anything else.
Back to top
Display posts from previous:   

All times are GMT - 8 Hours