It won’t fully shutdown, so you’ll still have to kill the virtual device. I’ve had no problems after “powering off” the device with the (virtual) power button. Ideally you would reboot your device using adb, but this hasn’t worked for me. You should see the following dialog pop up: (Note this may only work for versions 2.7.2 and later of Genymotion.) Drag and drop the zip package to the virtual device.(These latter steps must be done for each device.) (I’ve installed “stock”, but anything down to “nano” should do.) Select the Android release that corresponds to your virtual device Android version.Many write-ups will tell you to install both an ARM-x86 translator, and an ARM version of GP. Fortunately, you can install a bundle containing GP yourself. Many apps depend on Google Play (GP) services. The number after “inet” is the IP address you need. For example, on Linux or OSX, you can use ifconfig. To check, you can use any tool that lists the information for your network interfaces. I find this generally ends up as 192.168.56.1. To connect to a service on the host machine, you need to use the IP address of this interface. The connection happens through a virtual interface named “vboxnet0”. The HO device allows connecting to the host machine. Genymotion sets up two, a NAT service to connect to the outside world, and a “host-only” (HO) device. Virtualbox has several networking modes used to expose a guest virtual machine (in this case, an emulated Android device). Genymotion achieves this by running an x86 version of Android in Virtualbox. I’ve used it for years, and highly recommend it for any serious developer. Genymotion makes a drop-in replacement that’s blazingly fast. The standard Android emulator can be painfully slow. I wanted to make note of a couple of quick tips for Android development around emulators.

Genymotion virtualbox network settings