I had the same problem on Windows 8.1, Genymotion 2.4.0 and VirtualBox (tried with both 4.3.12 and 4.3.26). I found a temporary solution through the following steps:
- In Virtual Box: Settings\Network\Host-only Networks remove all host-only Networks
- Disable the Ethernet connection in Control Panel\Network and Internet\Network Connections
- Enable the WiFi connection
- Start Genymotion. After starting successfully a Virtual Machine, it is necessary to remove all host-only networks, close genymotion and open it again to make it work
I know it might not be a solution if you are not lucky enough to have multiple network connections, but it might give you some suggestions for alternative paths to follow.
I am pretty sure our firewall has a configuration that disturbs VirtualBox while creating the Host-only Network (which you can find in Virtual Box\Settings\Network\Host-only Networks).
I am not sure this is related, but on my Ethernet network connection, ping is disabled, whereas it works normally on my WiFi connection.
When Genymotion starts it searches for a valid Host-Only Ethernet Adapter in VirtualBox. if it doesn't find it, it tries to create a new one based on your active network connection. My theory is that if your network connection has some firewall limitations (some sort of blocked ports) the newly created Host-Only Ethernet Adapter doesn't have a valid IP configuration and therefore Genymotion fails to start. If you try to start several times Genymotion, you will find as many Host-only Networks as attempts.
Switching to a network connection that allows to create a valid Host-Only Ethernet Adapter solves the problem and, in my case, created automatically a working Host-only Network with the following parameters (Virtual Box\Settings\Network\Host-only Networks):
Adapter
- IPv4Address: 192.168.31.101
- IPv4 Network Mask: 255.255.255.0
DHCP Server
- Enabled
- Server Address: 192.168.31.100
- Server Mask: 255.255.255.0
- Lower Address Bound: 192.168.31.101
- Upper Address Bound: 192.168.31.254
I had similar problems with previous versions of Genymotion and I was able to successfully use the workaround described here: Not able to start Genymotion device