GenyMotion Unable to start the Genymotion virtual

Question

When I run Genymotion, I get the following error:

Unable to start the Genymotion virtual device.

Unable to configure the network adapter for the virtual device.

Please, check the following points:
From VirtualBox, in the main parameters of software, check a network adapter "Host-only" is present. From VirtualBox, in the Genymotion virtual device parameters, check the first network interface has the type "Host-only". If no, then set this parameter manually.

How can I fix that?

Answer 1

I was struggling with this for a while and finally found a solution on Windows 10.

Steps:

Network and Sharing Center > Change Adapter Settings > Right Click on VirtualBox Host-Only Network ( If you have multiple do the following to all of them ) > Properties > Check the VirtualBox NDUS6 Bridged Networking Driver

Answer 2

For VIrtual Box 5.x - the settings from above comments are set automatically

Now for the error:

1.Make sure that you have enough Processor(s) and Base Memory - so the PC can support VM configuration(I use 1 procesor and 1024MB for all VM's)

2.Delete any unused VM from Genymotion and Oracle VirtualBox Manager - seems to reserve their configuration, though you use it or not(that specific VM)

Answer 3

I had a same kind of issue starting Genymotion on Ubuntu 16.04 and solved it in this way https://medium.com/@avanvitharana/genymotion-on-ubuntu-16-04-cb8ef8fc70e9#.6y0bgmmjb

Answer 4

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).

Answer 5

After you have updated the latest GenyMotion Version to 2.10 from 2.02...

1. Open GenyMotion
2. Go to the List of your 2.02 Devices
3. Left click the item and then right click on the menu to **Delete all your 2.02 Virtual Devices
4. Click the Add button at the top to add a New Device. Log into your account
5. Select the device you want. You can only select one device at a time
6. Click the Next button. Notice the Version number says - 2.10. There is other info about the device here.
7. Your device will start downloading to your GenyMotion Folder on the Drive **C. 8 After you download it, double click it to open up the Virtual Device like you normally would.
8. Repeat for other device you want

** C:\%Users%\AppData\Local\Genymobile\Genymotion\deployed

Answer 6

it worked for me when I start Gennymotion in Admin mode