virtualbox locks machine if kvm or kqemu modules are loaded

[Christer Edwards]

I don't know if this should be reported under kvm, qemu or virtualbox so I'll leave it generic for now.

In testing virtualization options on my C2D (macbook) I have tried kvm, qemu and virtualbox. I found that if the kvm modules are still loaded into memory (ie; kvm, kvm-intel or even the kqemu module) that virtualbox will lock the machine. The only solution here is to hard power-down the box and bring it back up again. I can duplicate this issue by simply inserting one of those three modules (modprobe kvm, kvm-intel or kqemu) and then starting virtualbox. Once I click "start" on the virtualbox VM the machine locks.

When launching a virtualbox VM without any of those modules loaded the system works fine.

Any other info needed please let me know.

[Patrice Vetsel (vetsel-patrice)]

We do not have virtualbox in our repository, il will invalid it. Please feel free to report your bug directly to virtualbox bugs system http://www.virtualbox.org/wiki/Bugtracker
Thank you for your report.

[komputes (komputes)]

Patrice, virtualbox-ose is in the universe repository.

I would like to confirm this bug. In Ubuntu 8.10 (Intrepid), kvm seems to be loaded at startup if you have the proper CPU extensions. This blocks me from being able to start up any virtualbox machine. virtualbox and kvm need to play nicely side by side, and if that is not possible, one after another. If you have kvm and virtualbox installed, you need to run the following command before opening virtualbox.

$ sudo rmmod kvm_intel kvm

[komputes (komputes)]

This is the error that virtualbox-ose outputs when the kvm module is loaded.

VirtualBox can't operate in VMX root mode. Please disable the KVM kernel extension, recompile your kernel and reboot.
VBox status code: -4011 (VERR_VMX_IN_VMX_ROOT_MODE).

Result Code:
NS_ERROR_FAILURE (0x80004005)
Component:
Console
Interface:
IConsole {e3c6d4a1-a935-47ca-b16d-f9e9c496e53e}