macOS - Unable to start the Virtual Device

Virtual machines, servers and Cloud services (AWS, GCP, Azure, ...)

Genymotion Desktop has been designed to run in a physical environment, not in a virtual machine. For this reason, running Genymotion Desktop in a macOS VM, a mac server or a macOS Cloud instance is not supported.

For more details, please refer to the following articles:

• Can Genymotion Desktop run in a virtual machine?
• Can Genymotion Desktop run on a server?
• Can Genymotion Desktop run in a Cloud service (AWS, Google Cloud, MS Azure, Alibaba, etc.)?

Mac M4 and macOS Sequoia 15.2

Due to a breaking change introduced in macOS 15.2 on Apple Mac M4 models, Genymotion Desktop may not work on this configuration at first.

To fix this problem, please refer to: I have upgraded macOS Sequoia to 15.2 and Genymotion Desktop has stopped working

Upgrading from Genymotion Desktop 3.3.3 or lower (mac M)

If you tried to install Genymotion Desktop 3.3.3 or lower on an Apple mac M series, you first need to purge it before upgrading.

For more details, please refer to this article: Apple Mac M series support

QEMU

Security & Privace issue

If you are using QEMU hypervisor, or running on a mac M series, you need to make sure that macOS firewall does not block local ports connections. We recommend the following settings:

Some local TCP ports are not available

When using QEMU hypervisor, Genymotion Desktop uses the following local TCP ports to connect to QEMU:

• 5555 (ADB)
• 6379 (REDIS)
• 24297 (Audio)
• 24810 (Audio)
• 24800 (Camera)
• 25000 (Render)
• 22468 (Render)

Make sure that no other tool or software are using any one of those local TCP ports.

For example, REDIS server tends to use local port 6379 which will conflict with Genymotion and QEMU. To fix this, you can either stop REDIS server with the following command:

brew services stop redis

or change the "port" directive in your redis.conf configuration file, to make REDIS server use another local port.

VirtualBox

From Genymotion Desktop 3.6.0 onward, QEMU is the default hypervisor and should be preferred over VirtualBox: it provides better compatibility and performances on macOS. If you were using VirtualBox previously, we recommend switching to QEMU hypervisor.