Bug 29394 - New lollipop image spins indefinitely, or displays `opengl server is unreachable` when hyper-v is enabled
Summary: New lollipop image spins indefinitely, or displays `opengl server is unreacha...
Status: RESOLVED NOT_REPRODUCIBLE
Alias: None
Product: Xamarin Android Player
Classification: Xamarin
Component: Player ()
Version: unspecified
Hardware: PC Windows
: Normal normal
Target Milestone: ---
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2015-04-24 17:48 UTC by Peter Collins
Modified: 2015-07-20 17:05 UTC (History)
4 users (show)

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

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 NOT_REPRODUCIBLE

Description Peter Collins 2015-04-24 17:48:08 UTC
If I enable hyper-v on my Windows 8.1 PC, I'm no longer able to boot virtual devices that use the new Lollipop images. The device sits on the screen with the spinner ~indefinitely in most cases, however a couple times while reproducing I saw the `opengl server is unreachable` dialog as well.

I am also able to use the KitKat images on this same reproduction environment without any issue. When I disable hyper-v on this system, the same Lollipop device that failed to boot previously now works without any issues.

XAP logs:
https://gist.github.com/pjcollins/78c60f9ab0f42a196900

VirtualBox logs:
https://gist.github.com/pjcollins/8fd9f5aaffd2ad69f597

Environment
Windows 8.1x64 w/ Client Hyper-V enabled
Comment 2 Will Schaller 2015-04-27 12:46:17 UTC
Thanks for the great report Peter, have been able to replicate this exactly. The host-only network is not being set up properly. Will look for a fix ASAP.
Comment 3 Will Schaller 2015-04-28 10:13:26 UTC
Hi Peter, does the machine you saw this on have a touchscreen by any chance?
Comment 4 Peter Collins 2015-04-28 10:26:25 UTC
It does not have a touchscreen, though I was using a 4k monitor on that PC at the time if that may be related in any way.
Comment 5 Mark Simpson 2015-07-20 10:17:47 UTC
I can't see from the logs how this is a problem with the host only network, the device has been assigned an IP.

I have tested this on Windows 10 x64 client with Hyper-V enabled, the Lollipop image runs slow but the user is warned of this once Hyper-V is detected.

Peter - could you retest this in the latest version and report back?
Comment 6 Peter Collins 2015-07-20 17:05:48 UTC
I'm no longer able to reproduce this using the same windows 8.1x64 box with Client Hyper-V enabled.

Tested against XAP 0.4.4 and the latest system images available as of 2015-07-20.