Bug 33322 - Network Failure - Could not configure host-only network
Summary: Network Failure - Could not configure host-only network
Status: RESOLVED DUPLICATE of bug 30212
Alias: None
Product: Xamarin Android Player
Classification: Xamarin
Component: Player ()
Version: unspecified
Hardware: PC Windows
: --- normal
Target Milestone: ---
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2015-08-24 07:32 UTC by Adam Hartley [MSFT]
Modified: 2015-08-24 10:08 UTC (History)
5 users (show)

Tags:
Is this bug a regression?: ---
Last known good build:


Attachments
Logs (8.84 KB, application/zip)
2015-08-24 07:32 UTC, Adam Hartley [MSFT]
Details


Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and 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 Links.

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.

Related Links:
Status:
RESOLVED DUPLICATE of bug 30212

Description Adam Hartley [MSFT] 2015-08-24 07:32:03 UTC
Created attachment 12615 [details]
Logs

When trying to create a device the following error message occurs:

Network Failure - Could not configure host-only network. Please reboot the computer and try again.

Rebooting makes no difference as the error is persistent.

Log files attached.

OS: Windows 10
Comment 2 Mark Simpson 2015-08-24 09:00:10 UTC
I have had success in using the latest (5.0.2) build of VirtualBox and XAP 0.4.4.

*** This bug has been marked as a duplicate of bug 30212 ***