Should suggest unloading KVM module instead of recompiling kernel

[Anssi Hannula]

When kernel module kvm-intel or kvm-amd is loaded and VirtualBox errors out with VERR_VMX_IN_VMX_ROOT_MODE, it shows help text "Please disable the KVM kernel extension, recompile your kernel and reboot".

It should check if kvm-intel/kvm-amd are loaded and instruct to remove that module instead. It is a lot easier than a kernel recompilation. At least Mandriva Linux has been shipping kvm as modules in the default kernels for quite some time now.

[Frank Mehnert]

Well, it depends on the kernel if there is a module or if the code is compiled into the kernel. But we will probably extend the message a little bit.

[Anssi Hannula]

You can also check /proc/modules to see if it is a module.

[Marko O.]

Unloading Kvm module or recompiling kernel is not needed, since in 3.0 of Virtualbox, it was working on the same machine just fine. Seems like Virtualbox is not willing to cexist with current KVM installations anymore, even if it was announced that that bug will be avoided with switch that would say Virtualbox to avoid such behavior in case of older kvm implementations that does not unset Vt bits when not used.

This way, everyone installing new Virtualbox on server with long term release, will realize that Virtualbox does not want to work in the presence of the other virtualization environments, even if not used. Please allow for Virtualbox to override this situation fith current in-production instalaltions, or users will be forced to stay with 3.0 that actually works and does not misbihave like this.

[Sander van Leeuwen]

Don't spread nonsense. VirtualBox does not claim AMD-V nor VT-x when not used. Unlike KVM until fairly recently.

[Frank Mehnert]

Shouldn't be relevant anymore with recent Linux kernels.