vBox 3.2.4 r62467 on Ubuntu 10.04 64 bit crashing on startup

[sdavmor]

Haven't used vBox in 7 weeks or so. Here's the message I'm getting:

Failed to open a session for the virtual machine Win2KOEM.
AMD-V is being used by another hypervisor. (VERR_SVM_IN_USE).
VirtualBox can't enable the AMD-V extension. Please disable the KVM
kernel extension, recompile your kernel and reboot (VERR_SVM_IN_USE).

Result Code: NS_ERROR_FAILURE (0x80004005)
Component: Console
Interface: IConsole {6375231a-c17c-464b-92cb-ae9e128d71c3}

There's no other hypervisor running on this box. vBox is the only one
I've ever installed. A quick check confirms this (no output from lsmod
| grep kvm).

I tried disabling AMD-V but I get the same message. Looking at past
posts on similar issues I think I'd like to try:

export VBOX_HWVIRTEX_IGNORE_SVM_IN_USE=1

I tried from the CLI to run this via VboxMange for the VM in question:

VBoxManage export Win2KOEM VBOX_HWVIRTEX_IGNORE_SVM_IN_USE=1

but that doesn't seem to be it either. A quick glance at the vBox help
suggests that I'm misunderstanding the export command. Since I don't
know what I'm doing I'll stop poking at it and ask here for help.

Where does one go to put that instruction into vBox? Or is there
another hack that will get me round this?

[sdavmor]

Post by sdavmor
Failed to open a session for the virtual machine Win2KOEM.
AMD-V is being used by another hypervisor. (VERR_SVM_IN_USE).
VirtualBox can't enable the AMD-V extension. Please disable the KVM
kernel extension, recompile your kernel and reboot (VERR_SVM_IN_USE).
Result Code: NS_ERROR_FAILURE (0x80004005)
Component: Console
Interface: IConsole {6375231a-c17c-464b-92cb-ae9e128d71c3}
There's no other hypervisor running on this box. vBox is the only one
I've ever installed. A quick check confirms this (no output from lsmod
| grep kvm).
I tried disabling AMD-V but I get the same message. Looking at past
export VBOX_HWVIRTEX_IGNORE_SVM_IN_USE=1
VBoxManage export Win2KOEM VBOX_HWVIRTEX_IGNORE_SVM_IN_USE=1
but that doesn't seem to be it either. A quick glance at the vBox help
suggests that I'm misunderstanding the export command. Since I don't
know what I'm doing I'll stop poking at it and ask here for help.
Where does one go to put that instruction into vBox? Or is there
another hack that will get me round this?

Completely de-installing v 3.2.4 then installing the new 3.2.6 took
care of my crash at startup of vBox issue.