[android-building] Re: Re\: \[android\-building\] Re\: android10.0.0_rxx \: lunch qemu_trusty_arm64\-userdebug fails

Hi, Small update although I haven't been able to hack on this for a while. It runs, and stays running, under the QEMU emulation AND under the KVM on a mobile phone. Mesa graphics stack is initialized and the android animation starts to rotate with virtio acceleration, but there is still somethi

[android-building] Re: Re\: \[android\-building\] Re\: android10.0.0_rxx \: lunch qemu_trusty_arm64\-userdebug fails

Hi, I'm getting pretty close with a legit config. The bootup log is almost entirely clean. See this: https://github.com/jkrh/kvms/blob/master/scripts/run-qemu6-virt-android-super.sh If run with the CPU emulation it generates some SIGILLs from zygote (even with the QEMU MAX cpu), but overall: [

Re: [android-building] Re: android10.0.0_rxx : lunch qemu_trusty_arm64-userdebug fails

Hi, I'd really love to be able to send commands via adb from the host to the guest, but when I run *adb devices* it says *emulator-5554 offline* Any ideas? A lot of what I've come across mentions to turn on USB debugging, but I'm not sure how to do that given our environment Julien walked th

Re: [android-building] Re: android10.0.0_rxx : lunch qemu_trusty_arm64-userdebug fails

I figured out my issue from when I last posted. The problem was I didn't keep the super partitions inside fstab.ranchu which this documentation states is necessary https://source.android.com/devices/tech/ota/dynamic_partitions/implement So my fstab includes - System - Vendor - Product

[android-building] Re: Re\: \[android\-building\] Re\: android10.0.0_rxx \: lunch qemu_trusty_arm64\-userdebug fails

Hi Felix, I took a look again into all my stuff to double check, using the described list of commands* (using Debian 11 x86_64 computer, but was also working on Debian 10) I obtained both "system.img" and "vendor.img" into the output folder. Commands*: source build/envsetup.sh lunch a

Re: [android-building] Re: android10.0.0_rxx : lunch qemu_trusty_arm64-userdebug fails

Hi Julien, Just joining this conversation and I have some questions. I actually do have a physical arm64 device that I am trying to act as a hypervisor to run multiple androids on. I am running Ubuntu 20.04 on the aarch64 host and I believe what you have outlined is of great help, but I am run

[android-building] Re\: \[android\-building\] Re\: android10.0.0_rxx \: lunch qemu_trusty_arm64\-userdebug fails

Hi Julien, I'm trying to replicate your method for building an arm64 build of android that can be run in native QEMU, and have built both AOSP and the 5.10 kernel to your specification. An issue however is that there seems to be no vendor img produced when done in a clean environment. are ot

Re: [android-building] Re: android10.0.0_rxx : lunch qemu_trusty_arm64-userdebug fails

Hi Julien, First of all thank you for provinding the detailed documentation- I'm in the process of attempting to replicate it for my own needs. An issue/concern of mine is the generation of vendor.img after having executed m/make within AOSP and it not creating a vendor.img file. Per the AO

Re: [android-building] Re: android10.0.0_rxx : lunch qemu_trusty_arm64-userdebug fails

Hi, I might be wrong, but maybe the graphics pipeline from the guest to the host GPU with QEMU could look something like this: 1) virgl-gallium, https://gitlab.freedesktop.org/mesa/mesa. Android.mk: BOARD_GPU_DRIVERS=virgl 2) virtio-gpu (guest) 3) virtio-gpu (host) 4) virglrenderer (upstream ve

Re: [android-building] Re: android10.0.0_rxx : lunch qemu_trusty_arm64-userdebug fails

Hi, I tried something like this out of interest on arm64 with my own hypervisor (custom kvm, https://github.com/jkrh/kvms) and indeed I get the android vm up. Thanks! In order to get the AOSP up I first started to port the 'ranchu' machine to qemu6, but the 'android-emu' library I'd need to ha

Re: [android-building] Re: android10.0.0_rxx : lunch qemu_trusty_arm64-userdebug fails

Hi again, Here is the AOSP 10 on ARM64 QEMU version of the procedure I follow. Andoid 5.10 arm64 kernel build included, like for x86_64. Appart from using "vdb" and "vdc" into fstab instead of sdb and sdc, and removing some "rild.rc" file, the approach is the same. With some additionnal informa

Re: [android-building] Re: android10.0.0_rxx : lunch qemu_trusty_arm64-userdebug fails

Here is an more precise/checked guide to AOSP 10 (aosp_x86_64-eng) on QEMU, kernel build and detailed configuration steps included (5.10, let's be up to date!) repo init -u https://android.googlesource.com/platform/manifest -b android-10.0.0_r47 repo sync source build/envsetup.sh lunch aosp_x86

Re: [android-building] Re: android10.0.0_rxx : lunch qemu_trusty_arm64-userdebug fails

Hi Julien, Wow, that's awesome! Thank you very much for the detailed info and description! It'll be a very useful reference for us when trying this out! Again, thanks! Br On Wednesday, May 19, 2021 at 5:48:56 AM UTC+9 julien@gmail.com wrote: > Hi Victor, > > Indeed yes I succeeded in runn

Re: [android-building] Re: android10.0.0_rxx : lunch qemu_trusty_arm64-userdebug fails

Hi Matthew, Can you please provide some guidance for creating the prebuilt, e.g. https://android.googlesource.com/trusty/prebuilts/aosp/+/refs/heads/master/pristine/qemu_trusty_arm64-target_files-7152458.zip? Seems to be related to build/make/tools/releasetools, and tried 'make dist', but gett

Re: [android-building] Re: android10.0.0_rxx : lunch qemu_trusty_arm64-userdebug fails

Hi Mathew, I managed to 'make dist' after working around some errors in build/make and frameworks/base/tools/aapt. Thanks On Tuesday, March 3, 2020 at 2:21:24 PM UTC+9 mma...@google.com wrote: > This target is a testing target used for evaluating our reference > TrustZone implementation. "sto

Re: [android-building] Re: android10.0.0_rxx : lunch qemu_trusty_arm64-userdebug fails

Hi Julien, 郁进, Did either of you manage to run AOSP on upstream QEMU? Thanks On Saturday, July 25, 2020 at 12:21:35 AM UTC+9 yuji...@gmail.com wrote: > This is tremendously helpful. Thanks a lot. > > My work is focusing on kernel, base on arm architecture, I want have > whole view of the runn

Re: [android-building] Re: android10.0.0_rxx : lunch qemu_trusty_arm64-userdebug fails

This is tremendously helpful. Thanks a lot. My work is focusing on kernel, base on arm architecture, I want have whole view of the running kernel. With qemu & qemu monitor & gdb & crash tools, I can stop kernel anywhere, read phy/virt address, registers even system register(with last qemu re

Re: [android-building] Re: android10.0.0_rxx : lunch qemu_trusty_arm64-userdebug fails

Hi 郁进, Recently I focused on making the untouched Android code base working with standard/upstream QEMU (which is a little bit different from the AOSP's emulator, which is a QEMU derivative), focusing on x86_64 builds and "android-x86" project build configurations; the work is still in progress

Re: [android-building] Re: android10.0.0_rxx : lunch qemu_trusty_arm64-userdebug fails

Hi, I found another tickets you submitted to run arm64 android via qemu. I tried to lunch aosp_arm64-eng project, run with android emulator, with qemu args: emulator -kernel ../Android_kernel/out/android-mainline/common/arch/arm64/boot/Image -system xxx .. *-qemu **--monitor tcp:127.0.0.1

Re: [android-building] Re: android10.0.0_rxx : lunch qemu_trusty_arm64-userdebug fails

Many thanks for your answers In fact what I'm trying to do is using QEMU files into AOSP source code to get Android (with GUI) built and running on a standard/upstream QEMU version. This would give the ability of running Android and its future releases without real "porting", on any device r

Re: [android-building] Re: android10.0.0_rxx : lunch qemu_trusty_arm64-userdebug fails

This target is a testing target used for evaluating our reference TrustZone implementation. "storageproxyd" is continuously resetting there because it is not being launched by our test script

Re: [android-building] Re: android10.0.0_rxx : lunch qemu_trusty_arm64-userdebug fails

+Matthew Maurer Do we have any documentation on this target? I think the last time we talked about this target it was only minimally functional. - Dan On Mon, Mar 2, 2020 at 12:51 PM Julien Robin wrote: > I succeeded to find a workaround for the issue I signaled here, editing > device/generic/

[android-building] Re: android10.0.0_rxx : lunch qemu_trusty_arm64-userdebug fails

I succeeded to find a workaround for the issue I signaled here, editing device/generic/trusty/BoardConfig.mk and putting BUILD_QEMU_IMAGES to false, which still gives vendor.img, system.img and userdata.img I then found this kernel https://android.googlesource.com/kernel/common/+/refs/heads/and