VirtualBox

Ticket #10992 (new defect)

Opened 3 years ago

Last modified 3 years ago

Systematic error VERR_VMX_IN_VMX_ROOT_MODE when starting VirtualBox

Reported by: tom_WR Owned by:
Priority: major Component: other
Version: VirtualBox 4.2.0 Keywords:
Cc: Guest type: Linux
Host type: Windows

Description

Host is Windows 7 64 bits running on a Core i5 laptop Guest is Fedora 14 64 bits

I have a systematic fail when launching the VM. Disabled VMware services running in parallel, but no change. Note that I entered the ticket for 4.2.0, but this is also true for the 4.1.x versions.

The image I'm using works fine on other hosts (Linux principally)

Error message abstract (will enter full logs in the ticket):

Failed to open a session for the virtual machine Fedora14-x64-KP.

VirtualBox can't operate in VMX root mode. Please close all other virtualization programs. (VERR_VMX_IN_VMX_ROOT_MODE).

Result Code: E_FAIL (0x80004005) Component: Console Interface: IConsole {1968b7d3-e3bf-4ceb-99e0-cb7c913317bb}

Attachments

Fedora14-x64-KP-2012-09-24-10-36-20.log Download (70.0 KB) - added by tom_WR 3 years ago.
Fedora14-x64-KP-2012-09-21-16-53-55.log Download (69.8 KB) - added by tom_WR 3 years ago.

Change History

Changed 3 years ago by tom_WR

Changed 3 years ago by tom_WR

comment:1 Changed 3 years ago by frank

Sounds to me like you either have another VMM running in parallel to VirtualBox or if you are using the Windows XP compatibility box which in fact does the same.

comment:2 Changed 3 years ago by tom_WR

Hi franck,

I'm pretty sure this is about 'Windows XP compatibility box' Any suggestion for finding the faulty program ?

Note that I have vmware player installed on the same machine, but I have stopped all the related services and i still have the problem.

Thanks

Thomas

comment:3 Changed 3 years ago by tom_WR

As I look into the bug database, I can find similar issue in #10789, with a dell latitude (as my laptop: latitude e6420, 8GB RAM, 500GB HD). Could it be somewhat linked to the Dell BIOS ?

Last edited 3 years ago by tom_WR (previous) (diff)

comment:4 Changed 3 years ago by tom_WR

frank, is there any way we can progress on this ?

comment:5 Changed 3 years ago by frank

You could definitely try to update your host BIOS. If you are sure that you stopped all WinXP compatibility services then VirtualBox should normally run and a buggy BIOS could be certainly the reason.

Note: See TracTickets for help on using tickets.

www.oracle.com
ContactPrivacy policyTerms of Use