The VirtualBox DHCP server has not assigned an IP address to the virtual device

The error message indicates that the VirtualBox DHCP server took too long to assign an IP address to the device.

The error is usually caused by one or more of the following.

Windows

Hyper-V

Hyper-V is Windows virtualization technology.

Hyper-V does not work well with Genymotion and VirtualBox hypervisor.

We recommend turning Hyper-V off when using Genymotion.

To do so, follow these steps:

1. Disable Hyper-V in Windows features. Follow the instructions from the article "How to disable Hyper-V" to disable Hyper-V in Windows features. 2. Disable Memory Integrity. Memory Integrity is a Windows security feature that enforces Hyper-V, even if Hyper-V has been disabled in Windows features. You need to disable Memory Integrity to make sure VirtualBox has access to VT-X/SVM hardware virtualization. Open Windows Security. Go to Device Security > Core isolation details. Turn Memory Integrity off. 3. Verify Hyper-V is properly disabled. Open a PowerShell terminal. Run the command: systeminfo | findstr -i "hyper-v requirements". If Hyper-V is properly disabled, the command should return: Hyper-V Requirements: VM Monitor Mode Extensions: Yes. Otherwise, Hyper-V is still enabled. Make sure that Memory Integrity in Windows Security is disabled as well as Hyper-V in Windows features.

Note: If disabling Hyper-V in Windows features and Memory Integrity in Windows security does not disable Hyper-V, you can try following the guide to completely remove Hyper-V.

Power management

Power management for this issue refers to VirtualBox taking too long to allocate an IP address to the device.

On laptops and notebooks, this issue may occur if the power mode is set to "Save Battery".

To avoid this issue, set the power mode to "Performance" and plug the AC power in.

Virtualization is CPU-intensive and may drain the battery.

Laptops with discrete GPU

Some laptops have a discrete NIVIDIA or AMD GPU alongside an Intel iGPU.

This hardware configuration is known to cause issues on Windows systems (errors, slowness, crashes).

You need to force Windows to use the discrete, high-profile GPU globally to fix this issue.

To do so, follow the instructions from the article "How to fix issues on Windows with laptops using hybrid graphics (dual GPU)?"

Windows Updates

This error may occur after a Windows update.

To fix it, remove and re-install VirtualBox: Uninstall VirtualBox. Reboot your PC. Download VirtualBox recommended version installer for Windows. See the article "VirtualBox recommended versions". Re-install VirtualBox. Reboot your PC. Launch Genymotion and start a device. If an error occurs, reboot your PC and try launching Genymotion Desktop again.

Note: Sometimes, Windows updates re-enable Hyper-V and/or Memory Integrity. If re-installing VirtualBox does not help, verify that Hyper-V and Memory Integrity are properly disabled. If not, repeat the steps from the article "How to disable Hyper-V".

Other

macOS and Linux

It is possible to use QEMU instead of VirtualBox. While not recommended on Windows systems, QEMU has better compatibility and performances on Linux and macOS.

You are trying to run Genymotion Desktop in a virtual machine

Genymotion Desktop has been designed to run in a physical environment, not in a virtual machine. For this reason, Genymotion Desktop will not work if run in a Windows, Linux or macOS VM. For more details, please refer to "Can Genymotion Desktop run in a virtual machine?"

VPN and Firewalls

VPN and Firewalls may interfere with VirtualBox.

See:

Hardware requirements

This error may occur on hardware which does not meet Genymotion Desktop requirements.

The virtual device is using too many CPUs

You cannot use all your CPU cores when running a virtual device. You need to preserve 1 or 2 cores for the operating system.

For example, if your CPU has 8 cores, you should reduce the number of Processors of the virtual device to 6 or less.

You should not need more than 4 CPUs for a virtual device to run Android 10 or above comfortably.

Was this article helpful?

Yes

No

254 out of 728 found this helpful

Related articles