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

3 months ago · Updated

This error means that VirtualBox DHCP server took too long, or failed, to assign an IP address to the device. It is usually caused by the following.

Windows

Hyper-V

On Windows 10/11, this error is usually caused by Hyper-V.

Hyper-V does not work well with Genymotion and VirtualBox hypervisor. We recommend turning it off when using Genymotion.

To do so, follow these steps:

1. Disable Hyper-V in Windows features

Follow the instructions from this article:

How to disable Hyper-V

to disable Hyper-V in Windows features.

2. Disable Memory Integrity

Windows Memory Integrity security features enforces Hyper-V, even if it has been disabled in Windows features. You need to disable this feature to make sure VirtualBox has access to VT-X/SVM hardware virtualization:

Device Security > Core isolation details

3. Verify Hyper-V is properly disabled

Open a PowerShell terminal and run the following command:

systeminfo | findstr -i "hyper-v requirements"

If Hyper-V is properly disabled, it should return the following:

Hyper-V Requirements: VM Monitor Mode Extensions: Yes

Otherwise, Hyper-V is still enabled. Make sure that you have disabled Memory Integrity in Windows Security as well as Hyper-V in Windows features.

Note

If disabling Hyper-V in Windows feature and Memory Integrity in Windows security does not disable Hyper-V, you can try following

this guide

to completely remove Hyper-V.

Power management

This error can also be caused because VirtualBox took too long to allocate an IP to the device. On Laptops and Notebooks, this may happen if you are in "Save Battery" power mode. To avoid this, make sure to set your power mode to "Performance" and plug the AC power in.

Please note that virtualisation is CPU-intensive and may drain your battery.

Laptops with discrete GPU

Some laptops have a discrete NIVIDIA or AMD GPU alongside an Intel iGPU. This type of hardware 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 this 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:

VirtualBox recommended versions

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 compatibilty

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:

Genymotion Desktop and VPN

Genymotion Desktop and firewalls

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 your operating system.

For example, if your CPU has only 8 cores, you should to

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 247 out of 712 found this helpful

Need more help? Request Technical Support

Return to top

Related articles