Develop Reference

Visual studio android emulator will not start fully

I create a blank cordova application in visual studio 2015 and start debugging with the visual studio android emulators (first with the lollipop and then kitkat). XDE starts and the screen displays OS is starting.... It stays like that for quite a while until it displays
The emulator is unable to connect to the device operating system;
The device did not response to the connect request.
Some functionalities might be disabled'
After closing the dialog, it stays there forever until I kill the emulator. Killing the emulator triggers an error from visual studio.
Could not start emulated device 'VS Emulator Lollipop Phone'.
When I open hyper-v, I see the vm in the list and shown as running. When I connect, I see the console screen as below

I know this issue has been around for a while now, but I have just found a new solution for people who may still encounter this issue...
I had the same issue (stuck on "OS Is Starting") for API v 21 & 22. API v23 images would start, but could not debug - the app would crash as soon as it launched.
The following fixed the issue:
Shut down the emulator
Open Hyper-V manager
Go to the settings for the Android Image
Expand the "Processor" configuration node
Go to the "Compatibility" node
Check the "Migrate to a physical computer with a different processor version" option
Apparently it has something to do with newer Processor architectures being incompatible with the Android images or something like that - don't really care, as long as it works :)

I was running into the same issue. I did try to disable OpenGL by deleting: GuestDisplayProvider = "VsEmulator.OpenGLGuestDisplay" in xdesku.xml, as suggested in other answers.
At first, the virtual machine would boot up (you could connect to it from Hyper-V manager), but the emulator window itself would not connect to the machine (stuck on "OS is starting", then failing after a looooong while with the following message: "The emulator is unable to connect to the device operating system: Couldn't auto-detect the guest system IP address. Some functionality might be disabled.")
This answer https://stackoverflow.com/a/31698124/1010492 and that one https://stackoverflow.com/a/14402740/1010492 helped me solve the connectivity issue, and I was able to have the Virtual Machine displayed inside the emulator window.
However, the emulator wasn't working properly (scaling issues, no Home, Back, etc. buttons) until I put back the line "VsEmulator.OpenGLGuestDisplay" and after removing my profiles and rebooting a number of times.
To sum up, if you are encountering the same issue on an Hyper-V enabled computer, you may want to try the --over conscious-- following steps:
Ideally, uninstall any other Virtualisation software such as VMWare, Virtual Box and VPN clients such as Cisco VPN (if you cannot
do that, please be vigilant at step 13)
Reboot
In the "Visual Studio Emulator for Android" dialog, delete all installed device profiles
Remove All Hyper-V virtual switches - go to Hyper-V > Virtual switch manager > Remove all virtual switches
Run XdeCleanup.exe (usually in "C:\Program Files (x86)\Microsoft XDE\10.0.10240.0")
Also remove any extra virtual network adapters left in "Control Panel > Network and Internet > Network Connections" (after following
the previous steps, you should normally be left with only physical
adapters)
Make sure Network Sharing is disabled on all network adapters (right click, Properties, Sharing, untick "Allow other network users
to connect through this computer's Internet connection")
If ever you deleted the line GuestDisplayProvider="VsEmulator.OpenGLGuestDisplay" in xdesku.xml
(usually in "C:\Program Files (x86)\Microsoft
XDE\10.0.10240.0\SKUs\Android"), NOW IS A GOOD TIME TO PUT IN BACK.
Reboot
You may want to try to repair the emulators: go to Programs and Features > Microsoft Visual Studio Emulator for Android > Change and
hit "Repair" (although I have to say this always fails for me)
Reboot
Open the Visual Studio Emulator for Android, and install then run one of the profiles (eg: 7'' KitKat (4.4) XHDPI Tablet -- Similar to
Asus Google Nexus 7)
It may already work, but if not you should make sure that your network adapters are setup properly. Stop your emulator, then Go to
Control Panel > Network and Internet > Network Connections, and right
click the vEthernet adapters, then Properties and make sure you only
have the following boxes ticked in the Networking list (as explained
in Interference from other virtualization or networking software and
drivers: Client for Microsoft Networks, QoS Packet Scheduler, File
and Printer Sharing for Microsoft Networks, Microsoft LLDP Protocol
Driver, Link-Layer Topology Discovery Mapper I/O Driver, Link-Layer
Topology Discovery Responder, Internet Protocol Version 6 (TCP/IPv6),
Internet Protocol Version 4 (TCP/IPv4)
Reboot
Try to start the emulator again in "Visual Studio Emulator for Android"
If it still doesn't work, try to delete and recreate the profiles, and loads of reboots...
There are probably some redundants steps here, but I think it covers everything you should try (the key seems to be making sure that the network adapters are setup properly). If I've missing some things or if you think some steps are useless, please comment.

After alot of searching I got this working. Hope this helps. I found it in the comments on MSDN Article for Android Emulator with Visual Studio 2015
The new images might work if you disable OpenGL by going to Program Files (or Program Files x86 if you're on a 64-bit machine) \ Microsoft XDE \ 10.0.0.0 \ SKUs \ Android \ xdesku.xml and deleting this line: GuestDisplayProvider = "VsEmulator.OpenGLGuestDisplay". However, without OpenGL turned on you will not be able to take advantage of many of the new features

On my system I got it working again after enabling the disabled vEthernet (Internal Ethernet Port Windows Phone Emulator Internal Switch) again.
I didn't have to reboot.

I went through the steps in #Gyum Fox answer and still no joy for me.
While the Visual Studio Emulator for Android creates the first emulator instance, several virtual network switches are also created. For a laptop, typically three vEthernet instances are created; one for the wired LAN, one for the Wi-Fi, and another internal virtual switch for guest to host connections.
In my case, the vEthernet for the wired LAN was created successfully and then the Visual Studio Emulator for Android process would hang. This is observable from the Hyper-V Manager and the Virtual Switch Manager action.
Using the Virtual Switch Manager I successfully created the missing Wi-Fi virtual switch with these steps. Well, ultimately it worked. Read on.
Under the Virtual Switches list, select New virtual network switch…
Under What type of virtual switch do you want to create?, select External.
Under the External network: drop-down, select the Wi-Fi adapter.
Click the Create Virtual Switch button.
Change the Name: to match the name of your Wi-Fi adapter.
Click the Apply button.
In my case though, after clicking Apply, a failure message indicated the Wi-Fi adapter was bridged. Hmmm.
I started the View Network Connections control panel applet and the Wi-Fi adapter did not show it was bridged. (When a network bridge exists, the Status column has the word Bridged appended.) I suspect there was some dusty digital bits lurking somewhere in the registry.
Here is what cleared the issue for me.
Right-click on the Wi-Fi device.
Select Add to Bridge.
Right-click on the Wi-Fi device, again.
Select Remove from Bridge.
Now, go back up to the steps to create the virtual switch for the Wi-Fi network. The steps should complete successfully now.
And now, you can go back to creating the Android emulators you want.
One final thought… If you aren’t seeing any virtual switches being created, I suspect that could mean the wired LAN might have the dusty digital bits hanging you up. In that case, I’d try add-and-remove-from-bridge trick on the wired LAN adapter to see if that clear things up for you.
And, now I suppose that just doing the add-and-remove-from-bridge trick on the network adapter without creating the virtual switch might suffice. For me, the creation of the virtual switch was proof that the issue was corrected. YMMV ;-)

I found my issue was related to the windows firewall with some enterprise policies my company applied to all PCs. Once I stopped the Windows Firewall service it worked just fine.

I also had this issue and it was not just for android emulators but for all windows phone emulators.
This is what i did to fix the issue
Uninstall the Genymotion and Virtual Box (I had these in my system and this did not solve the issue)
Removed all Virtual adapters. this is the tricky part. None of adapters could not delete from Hyper-V virtual Manager. I had to use powershell and run
remove-vmswitch -Name "The name of V Adapter" -force
Also, from this I was not able to delete all the adapters and I found this link "https://social.technet.microsoft.com/Forums/windowsserver/en-US/e49df568-4f4c-47b7-b30c-952d1e26ca58/cant-remove-failed-virtual-switch-from-hypervs-virtual-switch-manager?forum=winserverhyperv" and deleted all virtual adapters
reboot the computer
After this there was not any v adapters in Hyper-V virtual Manager
Run the XdeCleanup.exe (just in case)
Also, I disabled the firewall from my virus guard
After this I was able to run the emulator from "Visual Studio Emulators for Android"

I'm adding a separate answer though the insight provided by Gyum Fox provided the clues I needed to try other stuff ...
[NOTE: The last time I was able to use the emulators (~3 weeks ago) I had wireless disabled and was using a wired connection on my Dev laptop. I ran out of space on my switch so re-enabled the wireless as the sole connectivity option. This may be totally coincidental, but read on and I'll let y'all decide.]
After following Gyum's steps without success, I decided to turn off the wireless and then try launching the emulator.
Wouldn't you know it ... it worked without an issue! 8-}
Once I had the emulator running, I re-enabled the wireless and the emulator picked up the connectivity.
I'm not a network guy so I'm not even gonna attempt to understand. It's a minor PITA but hey ... if it works!!! ;-}

On my machine I could start the emulator but I got an OpenGL error when trying to deploy and debug. I realized my issues started after I installed Docker. On a whim I decided to shut down Docker and disable the vEthernet (DockerNAT) Network Connection. This fixed my issue. Now, whenever I need to use the Andoird emulator I have to shut down Docker. Then when I'm done debugging I enable/restart Docker.

One of the reason I was having this issue is that I did not install the Android SDK on the default location. So I had to follow these instructions in order to be able to debug my application: https://msdn.microsoft.com/en-us/library/mt228282.aspx#ADB
I had to create the folder "Android SDK Tools" and add the Key "Path" with the value to my SDK, which in my case it was "E:\Android\Android_SDK"

Genymotion - The virtual device got no IP Address

I already tried doing this. Genymotion refuses to start with "The Genymotion virtual device could not get an IP address." but nothing happend.
And also here Not able to start Genymotion device.
Is it me? Who is being forsaken? Or is it my Lenovo laptop who's specs are just AMD-E1 Dual Core 1.0ghz (But I can run VS Studio 2013 just fine)
4gb RAM
Windows 8.1
But I found something weird. in most of the tutorial here in stackoverflow. in the File -> Preference -> Network the host-only network is vboxnet0 whilst on me it is VirtualBox Host-Only Ethernet Adapter I tried checking the Adapter and DHCP settings nothing is wrong.
Here is a printscreen when I try running it in Virtualbox

I have faced the same issue with genymotion. Follow these steps, may you can solve the issue
Open Oracle VM Virtual box
Select the custom phone ->right click->settings->General->Basic
Change the type to your current OS
Choose Version of the windows
In My case: I'm using Windows 10 -so, I Chose other Windows(64 bit)

I also struggled a few days fixing this issue. In my case, I restart the computer and enable the virtualization technology in BIOS. Then start up computer, open VM Virtual Box, choose a virtual device, go to Settings-General-Basic-Version, choose ubuntu(64 bit), save the settings then start virtual device from genymotion, everything is ok now.

Okay so I found a solution to run an emulator of an Android device via an alternative method.
First, run the emulator from Virtualbox UI. It should boot as in the question above. Let it finish booting until the home screen appears .
Then, run the same device from Genymotion UI.
And voila.
Note that, if you have just created a device in Genymotion, you will need to run it from there the first time. Even if/when it fails, this is still necessary, otherwise it can't be started from VirtualBox interface. After that first run, the emulator will run from VirtualBox, as well, and the above procedure will work.
After this, you will have two windows open - VirtualBox device window with Android emulator running, which is where you will use the device; and Genymotion window with device controls. It is a crazy setup but it works!
Note also that the screen rotation won't work.

I also had the same issue. First start your virtual box. Then in Setting go to General there you have to change the type of your OS to your current OS save it and it runs perfectly.

My VirtualBox Version:5.2.22, after those step ,solved my problem. Hope it helps you too.
Step 1: Find your emulator network adapter
Step 2: Open Global Tools
Step 3: change IP of your device then apply
Step 4: Click DHCP server tab
Step 5: Change Server Address and Address Bounds depending on your Wifi router then apply
Step 6: Start your device from Genymotion

I have had the same issue. Setting->General->Basic and change version 32 bit to 64 bit. Then it worked well.

Just simply change the Network mode in the Configure virtual device.
If it's not work, log off the computer, logon again and run Genymotion Device first of all.

It's simple!
Open Oracle VM Virtual
RIGHT-CLICK your phone -> settings -> General ->
Type: Choose your operating
Version: Windows version
DONE!!!!!!!!!!!!!!

What worked for me was reducing the number of processors from 4 to 2. My Mac Pro defaulted to 4 when I created the VM.

I have faced the same issue, and fixed it by downloading a new virtual device from genymotion

I fixed it by enabling Virtualization (VTx) in my BIOS.

What worked for me is by turning on Hardware Virtualization if in any case its already turned on / enable, just turn it off and turn it on back again. Then restart your PC.
cheers

I had the same problem and have tried a lot of solutions. In my case the problem was that my CPU does not support Virtualization Technology, which is required by most of Genymotion Devices, so it can't be solved.
The most recent Genymotion Virtual Device that works for me is Nexus 4 with Android 4.4.4 API 19.

Please look in this answer https://stackoverflow.com/a/21486549/2034822 which solved my problem. Hope it helps you too.

Somehow this issue is related to my device's memory settings.
Here is what I ended up doing to solve this problematic case :
Open Virtual Box
Choose your device, then open Settings (either by clicking yellow gear icon in menu bar or by right click -> Settings
There should a warning about the device if it is using too much memory. If there is not don't worry about it.
Open System tab, change the Base memory to 1024 MB (anything below 1024 is fine)
Save Settings and go back to Genymotion, start your device again and see if it works

I was facing the same issue on Mac OS Sierra. I simply quit VBoxNetDHCP and ran the Genymotion virtual device again - this time it ran smoothly. This is how you can try the same:
Open Activity Monitor (You can use Spotlight Search for this) -> Select the CPU tab -> in the search bar on the right enter DHCP -> in the results, if visible, select VBoxNetDHCP -> click on the cross button on the top left -> choose Quit -> Re-run your virtual device and it should work this time :)

Click the Genymotion Icon and open the Genymotion Device Manager. Click on Start. One the device tries to start it will give you the error. Close the error, and click on refresh on the Genymotion Device Manager and then Start again. That solves the problem for me.

for this problem first check your machine has enabled Virtualization Technology in bios setting.
It generally goes disabled when you open your laptop or computer board and rewired hard disk state or take out CMOS battery for replacing or cleaning purpose.
In some Intel based board it comes disabled by default. And virtualization technology is needed when you partition a computer to work as if it has several computers, allowing systems to run many operating system(like in a virtual box, VMware) at the same time.
restart of computer> go to the bios setting(by pressing esc,f1,...f12 could be any according to the type of board)> then enabled virtualization technologies (by searching on a tab menus)> save and restart your machine> now you can change setting of your virtual device(not necessary) from right clicking on that device and go to the setting>general>basic>change the version to 64 bit.... and you are ready to go

If those answers are not working
go to windows features and uncheck hyper-v

I fixed it by unchecking "Enable EFI (special OSes only)" on virtualbox device settings -> system

For me it is fixed by plugging in the power into my laptop. I guess when its just on battery, something goes wrong like CPUs going to sleep or something

Genymotion Android 4.4.2 Api 19 doesn't boot anymore

I'm using Genymotion with 4.4.2 API19 custom phone 7. Genymotion is not able to boot. So I boot from the virtual box. After a untracked pid series on the virtual box, it starts the android logo, the disk light show some activity, but nothing happen. I've tried everything from you suggestions. What could I do now? Any idea is well accepted! Thanks in advance! best regards Paul.

I had a similar problem, but wouldn't even see the Android logo. It turned out to be caused by connecting to the VPN at my workplace.
The reason for that is because the DHCP server range used by my VirtualBox host-only adapter was in conflict with that on the network at work.
Preferences -> Network -> Host-only Networks -> Double-click -> change the IP address and DHCP server to different values. Then reboot your host machine to ensure the setting change it applied (VirtualBox won't apply the changes until all VMs using the network are closed, and some processes seem to hang around for some time).

Open your virtual box and power off your virtual device , and then open genymotion and delete your device and add it again , if you add your previous device exactly , there will not need to any download

Not able to start Genymotion device

I am getting an error when I try to start Genymotion. It says
The Genymotion Virtual device could not obtain an IP address.For an
unknown reason, VirtualBox DHCP has not assigned an IP address to
virtual device. Run the VirtualBox software to check for issues
Can someone please tell me how to start it?

I had this same issue and here are the specific configuration that I needed to get this to work.
First, go to the VirtualBox preferences -> Network.
For the "Host-only Networks" tab, focus on the vboxnet0.
Click the icon on the left that looks like a screwdriver.
For the Adapter tab, fill in the IPv4 Network Address as 192.168.56.1
Fill in the IPv4 Network Mask as 255.255.255.0
For the DHCP Server tab, select the check box for Enable Server to enable the server
Fill in the Server Address as 192.168.56.100
Fill in the Server Mask as 255.255.255.0
Fill in the Lower Address Bound as 192.168.56.101
Fill in the Upper Address Bound as 192.168.56.254
The DHCP server part is what was not correct for me and it fixed my problem.

This worked for me..
Open Virtual Box and select your mobile VM. Right click->Settings
Change Promiscuous mode to Allow VMS and click ok

In virtualbox, go to the settings / network, and remove all host only networks. Make sure to go to the global settings of virtualbox, not the settings of your specific VM.
The settings screen should look like this:
Then restart your emulator in Genymotion.

I think you should configure your VirtualBox network adapter:
The adapter's IP address has to be in the same network
(192.168.56.0/24 by default) as DHCP server's IP address and DHCP's IP
address bounds. If all those addresses are not in the same network,
then your Genymotion virtual device might not be able to start.
https://cloud.genymotion.com/page/faq/#collapse-blank
Or check log files to get a clue:
For each platform, the log files are stored here:
Windows Vista/7/8: C:\Users\USER\AppData\Local\Genymobile
Windows XP: C:\Documents and Settings\USER\Local settings\Application Data\Genymobile
Linux: /home/USER/.Genymobile
Mac: /Users/USER/.Genymobile
https://cloud.genymotion.com/page/faq/#collapse-logs

If you are using a Windows PC, check this first (this list looks quite long, but the first three bullets will let you know if Hyper-V could be your problem, and the next five bullets will tell you if this answer will solve your problem - just a few moments!):
Open a good old-fashioned command prompt (not a PowerShell) with admin privileges and type:
bcdedit
Enter
Take a look for an item in the list called: hypervisorlaunchtype.
If hypervisorlaunchtype isn't in the list, or is Off, exit this answer and take a look at one of the other answers on this page.
If hypervisorlaunchtype is in the list and is set to Auto, Hyper-V is installed and is enabled.
Disable hypervisorlaunchtype by typing
bcdedit /set hypervisorlaunchtype off
Enter
Reboot
Try to start your Genymotion device again.
If it still fails enable hypervisorlaunchtype by typing into an admin command prompt:
bcdedit /set hypervisorlaunchtype Auto
Enter
Reboot
Exit this answer and take a look at one of the other answers on this page.
Otherwise, if your Genymotion device now starts, you have a choice:
If you don't need Hyper-V remove it by un-checking it in Turn Windows Features On or Off and exit this question.
If you do need Hyper-V, allow easy enabling and disabling as per Scott Hanselman's blog post, which I will outline in the following bullets:
You can leave the default as Off and then add an item to the boot menu that allows you to switch it on, or vice versa.
If you are leaving the default as Off type the following into the admin command prompt:
bcdedit /copy {current} /d "Hyper-V"
Enter
and you will get a response like this:
The entry was successfully copied to {ff-23-113-824e-5c5144ea}.
then type:
bcdedit /set {ff-23-113-824e-5c5144ea} hypervisorlaunchtype auto
Enter
(ensuring you swap the GUID for the one your call to copy above gave you)
That's it, your done. (In order to switch between the two hold down the Shift key when you go for a Restart and then select Other Operating Systems on the blue screen and then Hyper-V on the subsequent screen and your OS will restart with Hyper-V enabled.)
If you want Hyper-V to be enabled by default type into your admin command prompt:
bcdedit /set hypervisorlaunchtype Auto
Enter
(which will revert the default boot to enabling Hyper-V)
Then type the following in the admin command prompt:
bcdedit /copy {current} /d "No Hyper-V"
Enter
and you will get a response like this:
The entry was successfully copied to {ff-23-113-824e-5c5144ea}.
then type:
bcdedit /set {ff-23-113-824e-5c5144ea} hypervisorlaunchtype off
Enter
(ensuring you swap the GUID for the one your call to copy above gave you)
That's it, you're done. (As with off by default above, in order to switch between the two hold down the Shift key when you go for a Restart and then select Other Operating Systems on the blue screen and Hyper-V on the subsequent screen and your OS will restart with Hyper-V enabled.)
This comment and this answer to the question you are currently reading lead me to the resolution in my case and I am adding this answer to outline simple steps to take before you spend a lot of time on any solution - that comment and answer do get you where this answer will take you, but I have laid it out step-by-step in the hope that you can save time.
Background:
This article by Scott Hanselman gave me the meat of what I have outlined, with this comment on that blog post by Jonathan Dickinson helping with my background understanding and preventing me disappearing down a rabbit hole, but this article by Derek Gusoff fine tuned the steps above.

VMs used to work for me under Genymotion 2.0.0. with default RAM and CPU settings and VirtualBox 4.3.2 (on ubuntu 13.10). Upgrading to 2.0.1 made them stop working and give the error you mentioned.
I tried various fixes as I described here: https://stackoverflow.com/a/20018833/2527118, but in summary what fixed my problem was to delete VM and recreate it (same source and settings) in GenyMotion. You might want to try the other fixes (less destructive) before doing that.
Andrei

In my case, I restart the computer and enable the virtualization technology in BIOS. Then start up computer, open VM Virtual Box, choose a virtual device, go to Settings-General-Basic-Version, choose ubuntu(64 bit), save the settings then start virtual device from genymotion, everything is ok now.

After trying all of these answers, to no avail, I managed to get it up by first running the device from Vbox, leaving it open, and then running the device from Genymotion... In my case this was the ONLY way after trying several different devices (Samsung S4/S6 etc), network/DHCP settings and modes and so on...

In my case, Global Settings matters.
After I changed my global network setting with DHCP Servers on, I could start my genymotion virtual device.
cmd+, or File > Settings
Network
Host only Network
select vboxnet0, click driver icon
Check DHCP on
I blogged it. http://okjsp.tistory.com/1165644212 (sorry for korean, but you can see it from images)

I struggled quite a long time fixing this issue. In my case it was a combination of 2 answers that got it to work. Visual studio enabled my Hyper-V. I had to turn it off as suggested by LanderV. After this, I had to delete the Host-only network adapter in Virtualbox like Sammys said.

For me it was related to the lack of virtual resources (Ram and CPU). Go to the virtual box, right click on device -> Setting and increase the value of each resource.

Try downgrading to Virtual Box 4.2.18, if you are using 4.3.X.
I had a similar situation to yours.
I was using Genymotion 1.3.0 on Win7, with latest Virtual Box 4.3.2. Genymotion broke down after a computer shutdown, and never worked again.
I kinda stumbled onto this solution. After downgrading, Genymotion survived one shutdown now.
P.S. Changing network/resources settings in Virtual Box didn't help me, so I'm putting this up and hope it helps.

First of All, Make Sure to Enable Virtualization Technology under BIOS settings.

Try this: Remove virtual device in Genymotion and Add again the same or other device.
(you will lose your settings and apps in that device)

I had to change Adapter's address to: 192.168.56.100.
Then it worked.

(Windows 8) In my case i have changed default RAM from 1GB to 2GB on Genymotion and it gave this error. When i changed it back to 1GB it worked.

In my case, i started device from genymotion and then started the device from Virtualbox as well. It helped me.

try to clear the cache in genymotion Setting -> Misc -> Clear cache.
Check this image
maybe it will solve the problem.

Here is a trick i use. Go to http://androvm.org/blog/download/ and download the latest AndroidVm.
Genymotion is the extention of AndroidVM.

This problem keeps cropping up intermittently on my computer and usually, it happens when my computer is running low on system resources (mostly available RAM) and a sure-fire way to fix this (this at least has always worked for me) is to disable the VirtualBox Host-Only Network adapter and re-enable it.
If you have multiple virtual adapters, you'll have to find out which of those is used by Genymotion's virtual device and disable and re-enable it. You can find that out by starting VirtualBox and looking here:
You can read about enabling/disabling virtual adapters here

I'm running OSX. The solutions suggested didn't work for me. I'm using OSX Yosemite. I restarted my Mac then I uninstalled VirtualBox by launching the uninstall script (which is shown when you launch the dmg of VirtualBox) then reinstalled it. I also uninstalled and reinstalled Genymotion. Now everything is working smooth.

I've had this issue and none of the suggestions I found anywhere helped, unfortunately.
The good news, however, is that the latest versions work without any hacks!
I'm referring to Windows 7 host here.
genymotion-2.5.4.exe
VirtualBox-5.0.5-102814-Win.exe (download from test builds)
Edit: This stopped working again after updates so I gave up on Genymotion. The new Android emulator in SDK performs just as well, has great functionaly, and works without hiccups.

I'm using Windows 10 and had the same problem. I resolved it updating the VirtualBox to version 5.1.5. I hope it can help.

Mine was working fine on Windows 10 (Creator update edition) but then suddenly stopped working after I had been messing with Homegroups and trying to share a file between our office network. Not really sure what caused it. Has taken me over a week of doing all of the various suggestions above with no luck. Finally, ran a few things that fixed it at last!
IMPORTANT: To be honest, of all the things I ran below, I don't really know which one fixed it. I have a feeling that the IPv6 disabling tool would probably solve this straight away without the additional stuff. Maybe worth running that first to see what happens!
Here's what fixed mine:-
Removed virtual devices from Genymotion
Went into VirtualBox (Files -> Virtual Host Manager) and removed the host only adapters.
Opened command prompt as administrator. Type "cmd" into your search windows search bar, right-click on it and select "Run as Administrator").
Ran the following commands in order to put everything back to defaults and reset it all.
netsh winsock reset catalog reference
netsh int ipv4 reset reset.logsame as above
ipconfig /release
ipconfig /renew
Disable IPV6 using Microsoft's tool found here Disable IPv6 or its components (I downloaded and ran the one called Disabled IPv6 on all nontunnel interfaces)
Restarted computer
I was using Avast anti-virus. Uninstalled that too to completely remove that from the equation temporarily. I had already been disabling it temporarily whilst trying all the other solutions with no luck. Figured I'd uninstall it for certainty.
Installed Genymotion 2.12.0-vbox (with VirtualBox which should be 5.2.6)
After it installs, open up Oracle VM VirtualBox and go to File->Check for updates and you should be told there's an update to 5.2.8 at the time of this post. Install that.
Now go to GenyMotion and add a new device. Should work! (I didn't tweak anything in VirtualBox, didn't change anything to anything else - it just worked as is for me).
Good luck!

For me, I had to use host's internal GPU chip to connect display instead of external GPU. In my case, at first, I used GTX 970 chip, but Genymotion doesn't boot emulator. After I connect monitor to internal GPU chip inside CPU, it works.

Genymotion didn't get an ip address from virtual box

I've installed genymotion about 2 days ago and I've been facing the same problem every time I tried to start a device.
After I downloaded a device in genymotion (Nexus S - 4.2.2 - API 17 - 480*800) I launched it.
Then after a box poped up telling me I have to wait, I got this error:
The virtual terminal genymotion didn't get an ip address. For an
unknown reason the virtualbox's dhcp servor didn't assign an ip adress
to the virtual terminal. Please launch virtualbox to find a solution
to this problem
I can't figure out how to solve this problem.
I looked up on many websites but it seems as if I'm the only one to get this error.
I'm on Windows XP-SP3.
My graphic card is a radeon HD 3600 driver up to date.
Does anyone have any idea?
Thank you.

Try downgrading to Virtual Box 4.2.18, if you are using 4.3.X.
I had a similar situation to yours.
I was using Genymotion 1.3.0 on Win7, with latest Virtual Box 4.3.2. Genymotion broke down after a computer shutdown, and never worked again.
I kinda stumbled onto this solution. After downgrading, Genymotion survived one shutdown now.

All Android VMs used to work for me under Genymotion 2.0.0. with default RAM and CPU settings and VirtualBox 4.3.2 (on ubuntu 13.10). Upgrading to 2.0.1 made them stop working and give the error you mentioned.
I tried various fixes as I described here: https://stackoverflow.com/a/20018833/2527118, but in summary what fixed my problem was to delete VM and recreate it (same source and settings) in GenyMotion. You might want to try the other fixes (less destructive) before doing that.
Andrei

I try to solve this for 6 days and in the end, I realized I needed to uninstall then re install virtual box so I can get their default settings then change my network settings as explained better in this link. It explains in depth how the ip address works with the virtual machine, and how the chances of it trying to use a static ip address are very likely.
https://askubuntu.com/questions/232876/how-to-let-a-virtualbox-guest-running-windows-access-the-internet
let your network settings be handled by themselves if you've tried everything, maybe this will allow your VM to use its own IP address and stop trying to use your Physical devices IP address.
Hope this helps.

I had the problem with the IP error, too. As I have a real Samsung Galaxy S2, I downloaded the vitual version 2.3.7 Api 10 in Genimotion. All IP settings were correct, the sequence of starting the programms didn`t matter. The IP error reoccured :( .
Finaly, I tried to use another virtual device: Custom Tablet 5.1.0 API 22. It loaded and worked, but very slow. WhatsApp got stuck on the installation process :( . As this article on Heisse.de recomended to use the Nexus S 4.1.1 for WhatsApp, I tried this third vitual device and everything worked fine :) !
http://www.heise.de/download/special-whatsapp-auf-pc-mac-und-linux-nutzen-152241.html?hg=1&hgi=3&hgf=false

I know this post is old. But my answer is just for someone who google this issue and hopefully it may help them since I also stuck on it for a long time and fix it fortunately.
This is my way to fix the problem:
First of all, I had configured all the settings what the people said on the internet like the following link: Not able to start Genymotion device
I found that it's still failed to run the VM on GenyMotion.
So I tried to remove all the existing Host-only Network like vboxnet0 or vboxnet1(According to the official website of GenyMotion, it said that it will regenerate a new one when there is no any vboxnet)
Finally, I tried to restart the VM on　GenyMotion, suddenly I run it successfully without any errors message
Notes: I disabled the adaptor 2, 3 and 4 before I was gonna tried the above actions.

As other have said, you have to install Virtual Box. In my case (using Ubuntu 16.04), I had to enable the 'virtualization' in Bios. Once that was setup, I was able to set the 'OS' to use 'Ubuntu 64bit' in 'settings/general' tab.
Other possible solutions include, configuring Virtual Box further, including reducing the RAM usage (in settings), in 'Network' tab in settings, under 'advanced' options, disabling the 'cable connected' option & setting 'Promiscuous mode' to 'allow all'.

IN case a Genymotion device cannot obtain an IP address any more, you might want to check the configuration in the VM-Ware settings: I got this fixed by removing the "promiscous mode" from the network adapter 1 settings - see screenshot.
The promiscous setting may lead to difficulties in obtaining an IP address in the genymotion simulator