macOS - Unable to start the Virtual Device

This article is for Genymotion Desktop users on macOS who need to troubleshoot starting a virtual device.

Audience

This article is intended for Genymotion Desktop users on macOS.

VirtualBox hypervisor is not available on the Mac M series.
QEMU is now the default hypervisor and is recommended over VirtualBox because it provides better compatibility and performances on macOS.
If you were using VirtualBox previously, switch to the QEMU hypervisor.

Genymotion Desktop is designed to run in a physical environment.
Running Genymotion Desktop in a macOS VM, a macOS server, or a macOS Cloud instance is not supported.

There was a compatibility issue with Sequoia 15.2 on Mac M4 and legacy versions of Genymotion Desktop.
To fix this problem, make sure to use the latest versions of Genymotion Desktop.
For more information refer to Apple Mac M series support.
If you installed Genymotion Desktop 3.3.3 or lower on an Apple Mac M series, you first need to purge it before upgrading.

If you are using the QEMU hypervisor, or running on a Mac M series, you need to make sure that macOS firewall does not block local ports connections.
When using the QEMU hypervisor, Genymotion Desktop uses local TCP ports to connect to QEMU.
Port 5555 is used for ADB connections.
Port 6379 is used for REDIS connections.
Port 24297 is used for Audio connections.
Port 24810 is used for Audio connections.
Port 24800 is used for Camera connections.
Port 25000 is used for Render connections.
Port 22468 is used for Render connections.
Make sure that no other tool or software is using any of these local TCP ports.
If the REDIS server tends to use port 6379, this will conflict with Genymotion and QEMU.
To fix this, stop the REDIS server with the command: brew services stop redis.
Or change the "port" directive in your redis.conf configuration file to use another local port.

VirtualBox hypervisor is not available on mac M series.
QEMU is now the default hypervisor and recommended over VirtualBox.
If you were using VirtualBox previously, we recommend switching to the QEMU hypervisor.