Android-x86 6.0.1 R2 not support on VMWare Workstation 9

[Wesley Henrique]

Hello, Android-x86 6.0.1 R2 no start VMWare Workstation 9, black screen virtualization, my configuration:


Intel Pentium Dual Core E5500 2.80Mhz VT-x

Asus P5GC-MX/1333

3GB RAM DDR2

Intel 945G

Intel GMA950 256MB 64Bits DDR2 (Onboard) + Nvidia Geforce GT 240 1GB 128Bits DDR3 (Onboard

Windows 7 Home Premium SP1 32bits


my processor support VT-x, not started. Thank you.

[Chih-Wei Huang]

Yes. VMware was broken in 6.0-r2.
Will be fixed in 6.0-r3.
Or you can build from source to get the fix.

2017-04-22 9:57 GMT+08:00 Wesley Henrique <wes...@gmail.com>:
> Hello, Android-x86 6.0.1 R2 no start VMWare Workstation 9, black screen
> virtualization, my configuration:
>
> Intel Pentium Dual Core E5500 2.80Mhz VT-x
>
> Asus P5GC-MX/1333
>
> 3GB RAM DDR2
>
> Intel 945G
>
> Intel GMA950 256MB 64Bits DDR2 (Onboard) + Nvidia Geforce GT 240 1GB 128Bits
> DDR3 (Onboard
>
> Windows 7 Home Premium SP1 32bits

--
Chih-Wei
Android-x86 project
http://www.android-x86.org

[Thisara Kasun]

Hi chih-wei,

what's the current state of the nougat-x86 branch,
and Mesa 17.x on Android-x86?

Just out of curiosity if an rc will be released in the
near future.

Thanks!

[fguy]

no problems

суббота, 22 апреля 2017 г., 4:57:21 UTC+3 пользователь Wesley Henrique написал:

[Wesley Henrique]

You VMWare version?.

--
You received this message because you are subscribed to a topic in the Google Groups "Android-x86" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/android-x86/gp2qxm7dKWw/unsubscribe.
To unsubscribe from this group and all its topics, send an email to android-x86+unsubscribe@googlegroups.com.
To post to this group, send email to andro...@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.

[fguy]

12.5 - In it android the same way it just does not start

воскресенье, 23 апреля 2017 г., 20:27:45 UTC+3 пользователь Wesley Henrique написал:

You VMWare version?.

2017-04-23 6:59 GMT-03:00 fguy <fguy...@gmail.com>:

no problems

суббота, 22 апреля 2017 г., 4:57:21 UTC+3 пользователь Wesley Henrique написал:

Hello, Android-x86 6.0.1 R2 no start VMWare Workstation 9, black screen virtualization, my configuration:

--
You received this message because you are subscribed to a topic in the Google Groups "Android-x86" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/android-x86/gp2qxm7dKWw/unsubscribe.

To unsubscribe from this group and all its topics, send an email to android-x86...@googlegroups.com.

[mike ross]

Partition your system and install..

Just saying..

Mike

Sent with AquaMail for Android
http://www.aqua-mail.com

You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86...@googlegroups.com.

[Chih-Wei Huang]

2017-04-23 17:59 GMT+08:00 fguy <fguy...@gmail.com>:
> no problems
>

You have not enabled 3D hardware acceleration.
(just software renderer via LLVM)

When enabled the renderer is

GL Renderer: Gallium 0.4 on SVGA3D; build: RELEASE; LLVM;

Make sure you have checked
'Accelerate 3D graphics" in the Display settings
(It would warn you 3D acceleration is not supported in
the guest operating system. But it's just a false alarm.
Don't worry about that)

When 3D graphics enabled 6.0-r2 can't boot.
Try the just released 6.0-r3.
3D hardware acceleration should work.

[fguy]

The "Accelerate 3D graphics" option is missing in "Developers" - instead of it there is an option "Force GPU rendering". Enabling this option does not change anything for 6.0-r2. I'm downloading 6.0-r2 with the parameters "nomodeset vga=874".

I downloaded version 6.0-r3 without additional parameters on the vmware pro 12.5.Unfortunately, games "Fox Adventures" (with arm install) and "Defense Zone 3" start with a black screen (there is a sound from the game). "Fox adventures" works only in 6.0-r1, DZ3 in 7.1.

понедельник, 24 апреля 2017 г., 10:44:36 UTC+3 пользователь Chih-Wei Huang написал:

[Chih-Wei Huang]

2017-04-24 18:02 GMT+08:00 fguy <fguy...@gmail.com>:
> The "Accelerate 3D graphics" option is missing in "Developers" - instead of
> it there is an option "Force GPU rendering". Enabling this option does not
> change anything for 6.0-r2.

Hmm? I meant in the VMware UI instead
of Android-x86's settings.

> I'm downloading 6.0-r2 with the parameters
> "nomodeset vga=874".

With this option 3D hw acceleration is disabled.

> I downloaded version 6.0-r3 without additional parameters on the vmware pro
> 12.5.Unfortunately, games "Fox Adventures" (with arm install) and "Defense
> Zone 3" start with a black screen (there is a sound from the game). "Fox
> adventures" works only in 6.0-r1, DZ3 in 7.1.

OK. Need debugging.

[fguy]

2017-04-24 18:02 GMT+08:00 fguy <fguy...@gmail.com>:
> The "Accelerate 3D graphics" option is missing in "Developers" - instead of
> it there is an option "Force GPU rendering". Enabling this option does not
> change anything for 6.0-r2.

Hmm? I meant in the VMware UI instead
of Android-x86's settings.

Sorry. I was thinking about the options in android - in the vmvare of course this option is enabled.

I use the guest OS "Windows 7 x64" and add 2 lines to the vmx file:

mouse.vusb.enable = "FALSE"
mouse.vusb.useBasicMouse = "TRUE"

This allows you to get more variants of graphic resolutions than in Linux when using "vga=ask" in the loader.

 

> I'm downloading 6.0-r2 with the parameters
> "nomodeset vga=874".

With this option 3D hw acceleration is disabled.

Android 7.1 collected after October 2016 and android 6.0-r2 work in vmware only with these options.

[Chih-Wei Huang]

2017-04-24 18:54 GMT+08:00 fguy <fguy...@gmail.com>:
>> > I'm downloading 6.0-r2 with the parameters
>> > "nomodeset vga=874".
>>
>> With this option 3D hw acceleration is disabled.
>
> Android 7.1 collected after October 2016 and android 6.0-r2 work in vmware
> only with these options.

Yes. That's what I called "broken".
It has been fixed in 6.0-r3.