Bug 26739 - Xamarin Android Player fails to start VirtualBox VM
Summary: Xamarin Android Player fails to start VirtualBox VM
Status: RESOLVED DUPLICATE of bug 24237
Alias: None
Product: Xamarin Android Player
Classification: Xamarin
Component: Player ()
Version: unspecified
Hardware: Macintosh Mac OS
: Normal major
Target Milestone: ---
Assignee: Bugzilla
Depends on:
Reported: 2015-02-04 12:32 UTC by Louis Taljaard
Modified: 2015-05-13 09:27 UTC (History)
3 users (show)

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

XAP log (19.81 KB, application/octet-stream)
2015-02-04 12:32 UTC, Louis Taljaard
Vbox.log (46.86 KB, application/octet-stream)
2015-02-04 12:38 UTC, Louis Taljaard
VBox.log.1 (79.38 KB, application/octet-stream)
2015-02-04 12:39 UTC, Louis Taljaard
VBox.log.2 (79.44 KB, application/octet-stream)
2015-02-04 12:39 UTC, Louis Taljaard

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:

Description Louis Taljaard 2015-02-04 12:32:14 UTC
Created attachment 9642 [details]
XAP log

My Xamarin Android Player used to work fine. But somewhere over December/early January it stopped. I can open the app, install and update new virtual devices like Nexus 7 (Kitkat) or Nexus 4 (Jelly Bean). But when I click the Run/Play icon, the virtual device seems to load up properly and the phone VM screen briefly displays in a new popup window, but then the popup window disappears. The icon in XAP then shows a Stop button, i.e. it seems to still be running in the background. But when I try to run my app from Xamarin Studio, there is no error reported, it simply does not start. Due to this problem, I have today (4 Feb 2015) deleted the Xamarin Android Player from my Apps folder, as well as VirtualBox, and reinstalled the latest app from http://developer.xamarin.com/guides/android/getting_started/installation/android-player/ and this installed XAP version 0.1.1(1) and the name of the disk image that I downloaded is "XAP-Beta-14.49-v0.1.1.dmg". This also installed a new VirtualBox for me, and the VirtualBox version is 4.3.12 r93733. From the VirtualBox console it also shows that the VM as running, I can even see the current time (in H:mm format which updates itself every minute) shown on the screen with the Unlock Phone icon in the Preview window from the VirtualBox console, so I'm pretty sure the VirtualBox VM itself is running fine. It's just that XAP can't seem to connect to it. I'm also uploading the log file from my /Library/XAP/Log folder, it shows all log entries made from the point where I pressed the Play button up to the point where the popup screen mysteriously disappeared.

I've seen bug 25619 and mine is probably similar to that, but I thought I would log a new one here with more detail and to bring it to your attention that this is not only an isolated incident for one user.

Comment 1 Louis Taljaard 2015-02-04 12:33:36 UTC
Oh yes, this happens on my macbook air as well as my iMac, so it's not only one computer that's affected.
Comment 2 Louis Taljaard 2015-02-04 12:38:37 UTC
Created attachment 9644 [details]

I'm also attaching the VirtualBox log files: file 1 of 3.
Comment 3 Louis Taljaard 2015-02-04 12:39:11 UTC
Created attachment 9645 [details]

I'm also attaching the VirtualBox log files: file 2 of 3.
Comment 4 Louis Taljaard 2015-02-04 12:39:39 UTC
Created attachment 9646 [details]

I'm also attaching the VirtualBox log files: file 3 of 3.
Comment 5 Will Schaller 2015-05-13 09:27:02 UTC

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