virtualbox.org

I *might* end up reporting this as a bug, but I wanted to get people's thoughts first.

The setup:

I have VBox 4.3.6 on a Win7 host running a Win7 guest. On that guest, I've downloaded and extracted the Android ADT bundle (from developer.android dot com).

Expected behavior:

If I manually invoke (that is, browse through Windows and double click) the ADT Eclipse, then select File > Import > Android > Existing code, then click browse, then everything works exactly like it's supposed to -- in particular, the browse dialog works. Screenshot: i.imgur dot com/7mDVNrW.png.

The unexpected result:

But if I invoke the ADT Eclipse through guestcontrol:
Then the browse dialog is blank and non-responsive. Screenshot: i.imgur dot com/Quo7cZ6.png.

This happens consistently. Does anyone have any thoughts? Is there any additional information I can provide to help figure this out?

"guestcontrol" requires VBox Guest Additions software running in the guest - and no GAs have been written for Android. I wouldn't expect that to change until Android x86 shows a marked increase in popularity.

The guest, which is Win7, has Guest Additions installed.

As I see this you are actually running an Android emulator, right? That may be an issue. Have you tried to actually run commands against the guest itself?

No Android emulator. All I'm running is Eclipse.

Post (zipped) VM log file please.

Attached. Though, I did a quick text search, and I don't see my guestcontrol invocation in there. Is there another log I should be grabbing? Or a way to make this one more verbose?

I downloaded Eclipse standard and observed the same issue, so now we can forget all mentions of "Android". This issue affects Eclipse, and I have a simpler scenario and a more useful error message now.

If I start Eclipse normally (that is, double click in Windows), and I select File > Open, then I get the Open File dialog as expected.

But if I start Eclipse from guestcontrol and I select File > Open, then I get the error:

Location is not available
C:\Windows\system32\config\systemprofile\Desktop refers to a location that is unavailable.

Sounds like you aren't logged in as the correct user.

Logged in as "Developer", the only user on the machine, and guestcontrol command is also set to use username "Developer".