Using device/generic/qemu/qemu_x86_64.mk files for QEMU

[Julien Robin]

Hi folks,

I need a little bit of help on building something working on QEMU (on any architecture but let's start with x86_64). And yes as strange at it may seems, I have a professional need of being able to run untouched (or almost untouched) AOSP on QEMU platform ;)

I noticed those files : AOSP_SOURCE_DIRECTORY/device/generic/qemu/qemu_x86_64.mk (and others architectures). Looked like the Holy Grail

I successfully added a vendorsetup.sh file to show both qemu_x86_64-eng and qemu_x86-eng configurations into lunch menu, and built successfully.

But I have troubles running this build on QEMU, be it with the given kernel, or using a self built 4.14-goldfish kernel (working both with the AVD emulator, Android-x86 and Debian, embedding all the drivers : the perfect kernel! It took me some time to have the good kernel build config) or even using the Android-x86 boot structure to boot the resulting built (after having replaced and placed everything in the right place, system files vendor files and ramdisk content with fstab about /cache needed by android-x86 structure...

Android is sure booting but does nothing more after the following init output :

init: init first stage started!

[......]

ueventd: Coldboot took 0.03 secondslogd.auditd: start
logd.klogd: 42157422826
healthd: No battery devices found
healthd: battery none chg=

Is this normal from the qemu_x86_64-eng build?

How to use the AOSP_SOURCE_DIRECTORY/device/generic/qemu/qemu_x86_64.mk files available into AOSP to get some Android build working with QEMU?

Thank you very much in advance

Best regards,

Julien ROBIN

[Dan Willemsen]

These are the instructions on how to use the android emulator (with qemu): https://source.android.com/setup/create/avd

- Dan

--
--
You received this message because you are subscribed to the "Android Building" mailing list.
To post to this group, send email to android-...@googlegroups.com
To unsubscribe from this group, send email to
android-buildi...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-building?hl=en

---
You received this message because you are subscribed to the Google Groups "Android Building" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-buildi...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/android-building/c31b97c5-7642-4a5e-a770-897d3e6a4f07%40googlegroups.com.

[Julien Robin]

I noticed that AVD Emulator is pretty different from upstream QEMU, probably about goldfish and ranchu related things. Using -verbose and -show-kernel I can see which options are used to boot it, but using those options and things working fine with the AVD Emulator (aosp_x86_64-eng for example and android-goldfish-4.14-dev which seems mandatory to get Android 10 working with AVD Emulator) on a real upstream QEMU isn't working fine (GUI isn't starting)

Therefore the documentation about AVD Emulator builds https://source.android.com/setup/create/avd didn't really help me for upstream QEMU.

Can you confirm it's possible to use modern versions of AOSP on upstream QEMU? Are the AOSP/device/generic/qemu/* files usable to do so? Someone did succeed in the past with Android 6 / untouched AOSP and a extended compatibility kernel*, this is why I'm trying with newer versions of AOSP. This was documented here, but it's not up to date anymore : https://www.collabora.com/news-and-blog/blog/2016/09/02/building-android-for-qemu-a-step-by-step-guide/

*I have one based on android-goldfish-4.14-dev which works pretty much everywhere including Debian/Ubuntu on QEMU, aosp_x86_64-eng on AVD emulator and Android-x86 9.0.0. But it's still unable to get the GUI appearing on upstream QEMU using aosp_x86_64-eng builds for example.

Thank you in advance

Julien

On Monday, March 2, 2020 at 10:37:16 PM UTC+1, Dan Willemsen wrote:

These are the instructions on how to use the android emulator (with qemu): https://source.android.com/setup/create/avd

- Dan

On Mon, Feb 24, 2020 at 1:58 PM Julien Robin <julien...@gmail.com> wrote:

Hi folks,

I need a little bit of help on building something working on QEMU (on any architecture but let's start with x86_64). And yes as strange at it may seems, I have a professional need of being able to run untouched (or almost untouched) AOSP on QEMU platform ;)

I noticed those files : AOSP_SOURCE_DIRECTORY/device/generic/qemu/qemu_x86_64.mk (and others architectures). Looked like the Holy Grail

I successfully added a vendorsetup.sh file to show both qemu_x86_64-eng and qemu_x86-eng configurations into lunch menu, and built successfully.

But I have troubles running this build on QEMU, be it with the given kernel, or using a self built 4.14-goldfish kernel (working both with the AVD emulator, Android-x86 and Debian, embedding all the drivers : the perfect kernel! It took me some time to have the good kernel build config) or even using the Android-x86 boot structure to boot the resulting built (after having replaced and placed everything in the right place, system files vendor files and ramdisk content with fstab about /cache needed by android-x86 structure...

Android is sure booting but does nothing more after the following init output :

init: init first stage started!

[......]

ueventd: Coldboot took 0.03 secondslogd.auditd: start
logd.klogd: 42157422826
healthd: No battery devices found
healthd: battery none chg=

Is this normal from the qemu_x86_64-eng build?

How to use the AOSP_SOURCE_DIRECTORY/device/generic/qemu/qemu_x86_64.mk files available into AOSP to get some Android build working with QEMU?

Thank you very much in advance

Best regards,

Julien ROBIN

--
--
You received this message because you are subscribed to the "Android Building" mailing list.
To post to this group, send email to android-...@googlegroups.com
To unsubscribe from this group, send email to

android-...@googlegroups.com

For more options, visit this group at
http://groups.google.com/group/android-building?hl=en

---
You received this message because you are subscribed to the Google Groups "Android Building" group.

To unsubscribe from this group and stop receiving emails from it, send an email to android-...@googlegroups.com.