Have we not had this conversation before? There are no GAs for Android, i.e. no Android graphics drivers, therefore there is no possibility that any of VirtualBox graphics controllers will do anything useful. The mere presence of a chipset does not speed anything up, the guest OS has to make use of it.
mpack wrote:Have we not had this conversation before? There are no GAs for Android, i.e. no Android graphics drivers, therefore there is no possibility that any of VirtualBox graphics controllers will do anything useful. The mere presence of a chipset does not speed anything up, the guest OS has to make use of it.
I don't know why you're trying to attack (or disagree with me hard) me all the time.
With 6.1.36 I couldn't make Android x86 work at all. Now at least one VGPU works.
Can I report my experience or you deny even this to me? Should I STFU and log out permanently?
I participate in most discussions here but I am not aware that I disagree with you "all the time". I have a vague memory of discussing the above already, and pointing out pretty much the same facts (which have not changed) and that is what I said above.
And please absorb what I said, as none of it was speculation.
By the way, what exactly counts as "working" to you, as far as the graphics chipset is concerned?
Are you saying that a 64bit Android VM crashes or fails to boot if VMSVGA is selected? Note that none of the available graphics chipsets should actually be relevant in an unsupported OS, but if you use a Linux template then VirtualBox will assume you intend to install Linux and it will select VMSVGA by default in the VM recipe. I'm not aware that this should cause a crash or hang or have any other measurable result (positive or negative) at all - especially when 3D acceleration was disabled as your notes said.
mpack wrote:By the way, what exactly counts as "working" to you, as far as the graphics chipset is concerned?
Are you saying that a 64bit Android VM crashes or fails to boot if VMSVGA is selected? Note that none of the available graphics chipsets should actually be relevant in an unsupported OS, but if you use a Linux template then VirtualBox will assume you intend to install Linux and it will select VMSVGA by default in the VM recipe. I'm not aware that this should cause a crash or hang or have any other measurable result (positive or negative) at all - especially when 3D acceleration was disabled as your notes said.
With 6.1.36 Android x86 was completely unusable with any Virtual GPU: the surfaceflinger process kept crashing all the time or didn't load at all. It made using Android impossible.