Android 5.1+ under Proxmox (QEMU)

[Josep Mateu Clemente]

Before posting this, believe me I've spent time doing research and trying out multiple ISOs before assuming this would be the best way (and nearing to the only) to continue forward.

I've been trying to run Android-x86 under Proxmox (which, for the sake of shortness, is a QEMU on the Web Software) using QEMU 2.5. The results are as follows:

- Android 4.4-r3; Boots/Installs without problems. Network connection is troublesome without proper DHCP.
- Android 5.1-rc1: Boots to the 'Android' screen, doesn't get through that.
- Android 6.0/.1-rc3: Boots until 'starting adbd' - when in debug mode - afterwards it seems to hang on an infinite loop.

All the ISOs work correctly under Virtualbox or QEMU under an Ubuntu Machine. Settings appear to be the same (but I posted https://forum.proxmox.com/threads/differences-between-qemu-2-5-ubuntu-and-qemu-2-5-on-proxmox.25482/ just in case the issue lies with Proxmox).

Now I'm no expert in Android-x86 customizations so I'd like to ask for community help in sorting this out, as I assume anyone going the same path will find the same issues as stated here.

[Chih-Wei Huang]

2016-01-06 0:41 GMT+08:00 Josep Mateu Clemente <jmcle...@opera.com>:
> Before posting this, believe me I've spent time doing research and trying out multiple ISOs before assuming this would be the best way (and nearing to the only) to continue forward.
>
> I've been trying to run Android-x86 under Proxmox (which, for the sake of shortness, is a QEMU on the Web Software) using QEMU 2.5. The results are as follows:
>
> - Android 4.4-r3; Boots/Installs without problems. Network connection is troublesome without proper DHCP.
> - Android 5.1-rc1: Boots to the 'Android' screen, doesn't get through that.
> - Android 6.0/.1-rc3: Boots until 'starting adbd' - when in debug mode - afterwards it seems to hang on an infinite loop.

First, I suggest you enlarge the ram to 1GB at least, 2GB better.
5.1 and later version require more memory.

> All the ISOs work correctly under Virtualbox or QEMU under an Ubuntu Machine. Settings appear to be the same (but I posted https://forum.proxmox.com/threads/differences-between-qemu-2-5-ubuntu-and-qemu-2-5-on-proxmox.25482/ just in case the issue lies with Proxmox).
>
> Now I'm no expert in Android-x86 customizations so I'd like to ask for community help in sorting this out, as I assume anyone going the same path will find the same issues as stated here.

You need to check the logcat to see what happened, of course.
In particular, compare the working and not working cases
to find the differences.


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

[Josep Mateu Clemente]

As an addition, I'll give a look to the logcats but I can bet that libhoudini is the key item here (as it hasn't been ported to lollipop or further as stated in other posts).

[Chih-Wei Huang]

2016-01-07 23:36 GMT+08:00 Josep Mateu Clemente <jmcle...@opera.com>:
> As an addition, I'll give a look to the logcats but I can bet that
> libhoudini is the key item here (as it hasn't been ported to lollipop or
> further as stated in other posts).

What issue did you talk about exactly?

If you meant the "unable to boot to Home" issue,
it definitely unrelated to libhoudini.