[Pkg-virtualbox-devel] Bug#584680: Bug#584680: [virtualbox-ose-dkms] After installing kernel source and headers and reinstalling VirtualBox, Virtualbox says to disable KVM extension

[Michael Gilbert]

On Sun, 06 Jun 2010 15:15:36 +0200 Sacra Mateos wrote:

> Package: virtualbox-ose-dkms
> Version: 3.2.0-dfsg-1
> 
> --- Please enter the report below this line. ---
> 
> I cannot run VirtualBox even following Mike's suggestions.
> 
> After installing kernel source and headers and reinstalling VirtualBox, 
> Virtualbox says to disable KVM extension  There seems to be some modules 
> created but the virtual device cannot boot.
> 
>  > this error means you're missing the linux-headers-2.6.32-trunk-amd64
>  > package.  do you have it installed?  note that the *32-trunk* kernel
>  > version is rather old, and some additional dkms compatibility was
>  > added in the *32-3* version.  you should really want to be running the
>  > latest kernel releases.
> 
>  > mike
> 
> I reinstalled the linux kernel headers and source.
> 
>      Do I need to uncompress the source tar file in a directory?
>      Where do I put it, /usr/share/linux ?

you don't need to do anything.  dkms automatically finds the headers in
their default installation path.

> I compiled VirtualBox running Linux 2.6.32-trunk-amd64.
> I rebooted and compiled VirtualBox running Linux 2.6..32-3-amd64
> 
> VirtualBox doesn't produce the kernel modules in trunk-amd64.
> VirtualBox seem to be somewhat producing something because I'm able to 
> boot the virtual device but I get this error message:
> 
> 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).

you're probably going to have to invest quite a bit of effort to get
things working for *-trunk* if that's what you really want.  if you
boot into *-3*, things should work (at least according to your attached
apt log).  kvm and vbox should be able to coexist just fine, but running
"sudo rmmod kvm" will make sure kvm isn't loaded.  the output of
"lsmod | grep vbox" would also be useful.

mike