Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
Mono organizations on
GitHub to continue tracking issues. Bugzilla will remain
available for reference in read-only mode. We will continue to work
on open Bugzilla bugs, copy them to the new locations
as needed for follow-up, and add the new items under Related
Our sincere thanks to everyone who has contributed on this bug
tracker over the years. Thanks also for your understanding as we
make these adjustments and improvements for the future.
Please create a new report on
Developer Community or GitHub with
your current version information, steps to reproduce, and relevant error
messages or log files if you are hitting an issue that looks similar to
this resolved bug and you do not yet see a matching new report.
Created attachment 11240 [details]
When customer tries to launch a Android Player image, it fails with below error message:
No suitable Host-only networks found, unable to create Nexus 4
OS Version: Windows 10 Enterprise Insider Preview
This is caused by this issue in VirtualBox:
VirtualBox doesn't yet have official support for Windows 10, and consequently neither does the Android Player. This will hopefully be fixed in VirtualBox 5.0, which is currently in Beta testing.
*** Bug 32788 has been marked as a duplicate of this bug. ***
*** Bug 33134 has been marked as a duplicate of this bug. ***
XAP 0.4.4 is now working for me on windows 10 after installing the latest 5.0.x test build of VirtualBox.
DL link to use as a workaround for the meantime:
Sorry Peter Collins,
Still not working. Even though i install the VirtualBox 5.0.3 and XAP 0.4.4 on windows 10. but issue is still there.
In my scenario I had a rather fresh install of Windows 10 Pro x64. I installed XAP first, and then downloaded the latest test build of Virtual Box and installed it over the version of Virtual Box that XAP installs. I always launch and manage the virtual devices using the XAP Device Manager, and generally never use the Virtual Box interface.
Unfortunately Windows 10 is still not officially supported by VirtualBox or the Android Player, so any additional issues that you are encountering with VirtualBox/XAP on Windows 10 are upstream until they've released official support.
*** Bug 33322 has been marked as a duplicate of this bug. ***
Fixed in 0.5.0+, will also work with 0.4.4 if using VirtualBox 5.0.2 or newer.
I have checked this issue and now it's working fine i.e. now Android player launches successfully and also able to run android application successfully on XAP.
=== Xamarin Studio ===
Version 5.10 (build 811)
Installation UUID: 0e0b91ee-55ec-4538-bba2-9b20c10d7c6b
Microsoft .NET 4.0.30319.42000
GTK+ 2.24.22 (MS-Windows theme)
=== Xamarin.Profiler ===
=== Xamarin.Android ===
Version: 6.0.0 (Enterprise Edition)
Android SDK: E:\android-sdk
Supported Android versions:
2.3 (API level 10)
4.0.3 (API level 15)
4.1 (API level 16)
4.2 (API level 17)
4.3 (API level 18)
4.4 (API level 19)
4.4.87 (API level 20)
5.0 (API level 21)
5.1 (API level 22)
6.0 (API level 23)
SDK Tools Version: 24.3.4
SDK Platform Tools Version: 22
SDK Build Tools Version: 22.0.1
Java SDK: C:\Program Files\Java\jdk1.7.0_71
java version "1.7.0_71"
Java(TM) SE Runtime Environment (build 1.7.0_71-b14)
Java HotSpot(TM) Client VM (build 24.71-b01, mixed mode, sharing)
=== Xamarin Android Player ===
Location: C:\Program Files\Xamarin Android Player\DeviceManager.exe
=== Build Information ===
Release ID: 510000811
Git revision: 34cd31ea72536afab530c14d9220b286075e83cd
Build date: 2015-09-30 11:21:35-04
Xamarin addins: 8e6fccfc0c19a7e0b7b11be925f09751d827eb5c
Build lane: monodevelop-windows-cycle6
=== Operating System ===