Update: Before you read further, I want to notice that I didn't have any problems since I upgraded VirtualBox to 4.3.4.
I use VirtualBox 4.3.2 under Ubuntu 13.10. I had same issue after upgrading from Genymotion 2.0.0 to 2.0.1.
These are the steps I followed to fix this, although I'm not sure which one works for you.
Step 1. Start VirtualBox, go to menu File/Preferences menu, go to Network section, select Host-only Networks tab.
If you don't have any adapter defined, then you can create one (as indicated below) or you can ignore step 1 and Genymotion will create it when you try to start the VM.
If you do have an adapter there (vboxnet0) click the edit button. In the edit window, you must have DHCP server enabled AND the IP address and allocation pool of the server must be inside same network as the IP of the network controller. For example, I use:
- IPv4 address/netmask: 192.168.56.1/255.255.255.0 (on Adapter tab)
- DHCP server enabled checked (on DHCP server tab)
- Server address/netmask: 192.168.56.100/255.255.255.0
- Server lower/upper address: 192.168.56.100/192.168.56.254
Still in VirtualBox, select the Android VM you have, click Settings button, select Network section. In the Adapter 1 tab, you should have:
- Enable network adapter checked
- Attached to: Host-only adapter
- Name: vboxnet0
Normally, if you have all these settings, it should work ok, but it didn't for me. So I moved to step 2.
Step 2. As indicated by Genymotion, start VirtualBox, go to menu File/Preferences menu, go to Network section, select Host-only Networks tab and delete the defined adapters.
Start your VM in Genymotion. Genymotion will recreate the adapter with proper settings (as described in step 1)
Normally, if step 1 didn't work for you, step 2 should work ok, but it didn't for me. So I moved to step 3.
Step 3. Delete and recreate the Android VM in Genymotion (VirtualBox host-only network settings I left as described in step 1).
This solved my issue and Android VM works ok now. Good luck.
Andrei.
Update: A day after posting answer, when I was first starting a VM in genymotion, it gave again same error again and vboxnetdhcp process crashed (and restarted). On second and later start attempts it worked ok. So it might still be some minor issue there with VirtualBox DHCP process.
Update: The issue seems to reside in virtual Box DHCP server which crashes:
/usr/lib/virtualbox/VBoxNetDHCP --network HostInterfaceNetworking-vboxnet0 --trunk-type netflt --trunk-name vboxnet0 --mac-address 08:00:27:72:4C:7B --ip-address 192.168.56.100 --netmask 255.255.255.0 --verbose
Floating point exception (core dumped)
Deleting and recreating the VM fixed again the issue. Maybe Genymotion sends some invalid data to VBox DHCP that makes it crash (still a VBox bug though).
