Return to site

Android emulator for xamarin on mac execution failed after closing

broken image

broken image

Go to C:\Users\AppData\Local\Microsoft\VisualStudioEmulator\Android\Containers\Local\Devices.Make the amount of resources required by your Android emulator lower Try to allow your Windows 10 virtual machine dynamic resources or set its memory allocation higher then it is.You can resolve this in the following manner: Go to Hardware -> CPU & Memory -> Advanced settingsĪfter you resolve this issue, it is possible that you will still get an error that your emulator couldn't start as it requires 2GB RAM to run, which is not a small amount considering that we are already running a VM.Save all the work on your virtual machine.This functionality is possible but disabled in Parallels by default to avoid performance bottlenecks, as most use cases don't require such functionality.

broken image

When you try to start an emulator in Visual studio, you are effectively trying to start a virtual machine inside another virtual machine. Issue why Android emulator is failing to start for you is not with Xamarin in this instance, but lies in a fact that you are already running a virtual machine on your Mac (e.g.

broken image

Not sure if I'm maybe late to the party, but here is an explanation of the issue and a simple solution that might help at least others with the same problem.