Error: VERR_VMX_UNABLE_TO_START_VM if started in a fully virtualized kvm guest

[dancn]

To reproduce the problem:

• start with a debian host with nested virtualization enabled
• install an ubuntu 12.04 using libvirt/kvm
• install virtualbox inside ubuntu without errors or warnings
• run a linux 64 guest inside virtualbox
• the error message refers to the log, that is attached

best

[Frank Mehnert]

The VMLAUCH instruction failed for whatever reason. That could be a bug in VirtualBox as well as a bug in KVM. I will leave this ticket open but we don't have time to debug this.

[ryanuber]

I've run into this as well on Ubuntu 14.04. dancn did you ever find a solution?

[jsp]

Same issue encountered.

Setup: KVM Host-> Win 7 Guest with VirtualBox installed -> WinXP guest

VirtualBox failed to launch WinXP with same error as attached by original poster.

KVM was configured to enable nesting and pass the VMX cpu flag to the Win 7 guest. CPU-Z and Intel's CPU tool inside Win 7 both detected that VT-x was enabled.

Disabling the Hardware virtualization option in VirtualBox ("Enable VT-x/AMD-V") will allow WinXP to start. However, due to performance, this is not optimal.

[dancn]

I never got updates on this bug.

Maybe because trac was not configured with my email at the subscription time.

Anyway I just tried again... and now virtualbox inside kvm works.

Software and version used:

Main OS: Debian GNU/Linux 8.1 (jessie)
Kernel: 4.1.0-rc7 (compiled using debian latest .config and make olddefconfig)
Guest in KVM: Ubuntu 14.04.2 LTS
Kernel in Ubuntu: linux-image-3.16.0-30-generic
Virtualbox in Ubuntu: 4.3.28-100309~Debian~wheezy
Guest in Virtualbox: Ubuntu 14.04.2 LTS