![]() This solved my issue and Android VM works ok now. Delete and recreate the Android VM in Genymotion (VirtualBox host-only network settings I left 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. Genymotion will recreate the adapter with proper settings (as described in step 1) 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. Normally, if you have all these settings, it should work ok, but it didn't for me. Still in VirtualBox, select the Android VM you have, click Settings button, select Network section. DHCP server enabled checked (on DHCP server tab).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. If you do have an adapter there (vboxnet0) click the edit button. 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. ![]() Start VirtualBox, go to menu File/Preferences menu, go to Network section, select Host-only Networks tab. ![]() These are the steps I followed to fix this, although I'm not sure which one works for you. I had same issue after upgrading from Genymotion 2.0.0 to 2.0.1. I use VirtualBox 4.3.2 under Ubuntu 13.10. Update: Before you read further, I want to notice that I didn't have any problems since I upgraded VirtualBox to 4.3.4.
0 Comments
Leave a Reply. |