Welcome to the Treehouse Community

Want to collaborate on code errors? Have bugs you need feedback on? Looking for an extra set of eyes on your latest project? Get support with fellow developers, designers, and programmers of all backgrounds and skill levels here with the Treehouse Community! While you're at it, check out some resources Treehouse students have shared here.

Looking to learn something new?

Treehouse offers a seven day free trial for new students. Get access to thousands of hours of content and join thousands of Treehouse students and alumni in the community today.

Start your free trial

Android Android Tools Getting Started with Genymotion Creating a Genymotion Emulator

Neil Gittens
Neil Gittens
1,826 Points
Posted by Neil Gittens
Neil Gittens
1,826 Points

Unable to start the virtual device. VirtualBox cannot start the Virtual device

I am getting the follow error when trying to run Genymotion for the first time.

Unable to start the virtual device. VirtualBox cannot start the Virtual device. To find out the cause of the problem, start the virtual device from the virtual box.

I am also having a problem with virtual box when I open Oracle VM VirtualBox Manager

Failed to open a session for the virtual machine Google Nexus 4 - 4.4.4 - API 19 - 768x1280.

VT-x is disabled in the BIOS for both all CPU modes (VERR_VMX_MSR_ALL_VMX_DISABLED).

Result Code: E_FAIL (0x80004005) Component: ConsoleWrap Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}

Can anyone help?

I've search for solution on the forum and on google.

Neil Gittens
Neil Gittens
1,826 Points
Neil Gittens
Neil Gittens
1,826 Points

found the answer on another forum.

Had to make a change in the bios. Hope this will work for anyone who have this same problem.

1 Answer

Reena Turak
seal-mask
.a{fill-rule:evenodd;}techdegree
Reena Turak
iOS Development Techdegree Student 5,566 Points
Reena Turak
.a{fill-rule:evenodd;}techdegree
Reena Turak
iOS Development Techdegree Student 5,566 Points

In my case we have 2 VM active at a time that's why the error was. to solve the issue we disabled the old VM (hyper -V) and restarted the system. now its working fine.