Re: [android-building] Which QEMU/KVM command line would run mini_emulator (or other) builds ?

[Joerg Pleumann]

Hi,

unfortunately I cannot help you. But I have similar problems with the emulator 
alone. I want to use it to be able to create customized Android 9.x images 
including Google apps (we’re partner) before we have access to the real 
hardware for a project. It took me a while to find out that only the aosp_* 
lunches would support the emulator at all (some others did, occasionally, but 
most likely because the emulator had already been built, but normally the 
*-qemu.img files were missing, so it would not boot at all). I also have some 
sort of freezing, maybe the same that you see. Sometimes the emulator works 
fine for a while, sometimes it freezes immediately after boot, and each input 
event takes a minute to process. I have a pretty powerful machine, so that 
can’t be the root cause, and I already tried raising the RAM available to the 
emulator.

The emulator in Android studio works fine, on the other hand. So it is 
possible. But maybe some tweaks to the build are necessary.

Maybe someone from Google can point us into the right direction.

Best regards
Joerg

> Am 11.04.2019 um 18:37 schrieb julien.robi...@gmail.com:
> 
> Hello everybody,
> 
> Does anybody here know the correct KVM command to run one of the following 
> builds (few lines below) ?
> I'm really stuck and I definitely need some help - also I'm pretty sure that 
> it's just a matter of typing a command with the correct parameters into 
> "append" (kernel parameters) and others things. But I didn't find the good 
> ones.
> 
> I'm struggling to run Android with QEMU/KVM, which is a little bit different 
> compared to the official "emulator" command. 
> I'm doing this, because I'm trying to learn how to run Android on 
> generic/upstream kernel supported platforms (like Intel based laptop, or just 
> QEMU/KVM).
> 
> I've tried a lot of the available standard "lunch" choices from 
> android-9.0.0_r35 branch, but it seems that only aosp_-eng are running 
> out of the box with the emulator, but not with KVM/QEMU.
> I also captured what are the "QEMU" parameters used by the Emulator but lot 
> of them aren't recognized by the standard QEMU/KVM version, and so it doesn't 
> work.
> 
> mini_emulator doesn't work with "emulator" but seems to go further than the 
> others once started in KVM (but it freezes really quickly)
> 
> aosp_arm-eng
> aosp_arm64-eng
> aosp_mips-eng
> aosp_mips64-eng
> aosp_x86-eng
> aosp_x86_64-eng
> aosp_car_arm-userdebug
> aosp_car_arm64-userdebug
> aosp_car_x86-userdebug
> aosp_car_x86_64-userdebug
> mini_emulator_arm64-userdebug
> m_e_arm-userdebug
> m_e_mips64-eng
> m_e_mips-userdebug
> mini_emulator_x86_64-userdebug
> mini_emulator_x86-userdebug
> uml-userdebug
> aosp_crosshatch-userdebug
> aosp_blueline-userdebug
> aosp_cf_x86_auto-userdebug
> aosp_cf_x86_phone-userdebug
> aosp_cf_x86_tablet-userdebug
> aosp_cf_x86_tablet_3g-userdebug
> aosp_cf_x86_tv-userdebug
> aosp_cf_x86_wear-userdebug
> aosp_cf_x86_64_auto-userdebug
> aosp_cf_x86_64_phone-userdebug
> aosp_cf_x86_64_tablet-userdebug
> aosp_cf_x86_64_tablet_3g-userdebug
> aosp_cf_x86_64_tv-userdebug
> aosp_cf_x86_64_wear-userdebug
> cf_x86_auto-userdebug
> cf_x86_phone-userdebug
> cf_x86_tablet-userdebug
> cf_x86_tablet_3g-userdebug
> cf_x86_tv-userdebug
> cf_x86_wear-userdebug
> cf_x86_64_phone-userdebug
> cf_x86_64_tablet-userdebug
> cf_x86_64_tablet_3g-userdebug
> cf_x86_64_tv-userdebug
> cf_x86_64_wear-userdebug
> aosp_marlin-userdebug
> aosp_marlin_svelte-userdebug
> aosp_sailfish-userdebug
> aosp_walleye-userdebug
> aosp_walleye_test-userdebug
> aosp_taimen-userdebug
> hikey-userdebug
> hikey64_only-userdebug
> hikey960-userdebug
> Thank you in advance
> 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-building@googlegroups.com
> To unsubscribe from this group, send email to
> android-building+unsubscr...@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-building+unsubscr...@googlegroups.com 
> .
> For more options, visit https://groups.google.com/d/optout 
> .

-- 
-- 
You received this message because you are subscribed to the "Android Building" 
mailing list.
To post to this group, send email to android-building@googlegroups.com
To unsubscribe from this group, send email to
android-building+unsubscr...@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" 

[android-building] Best way to create custom emulator-only lunch

[Joerg Pleumann]

Hi,

I haven't paid much attention to the emulator in the last 5-10 years 
because we almost always had a matching hardware at hand. Now I am in need 
of creating a custom lunch that is emulator-only, running on x86. I tried 
to clone some of the existing x86 lunches and added my modifications, but 
always ended up with something that did not boot. The kernel did, but it 
didn't proceed to the system partition. I also did not see a 
system-qemu.img in my output folder. Funny thing is, if I use the original 
lunches they boot properly, but I don't want to change those. Is there 
anything hard-wired in the build system that does not like my cloned target?

Best regards
Joerg
 

-- 
-- 
You received this message because you are subscribed to the "Android Building" 
mailing list.
To post to this group, send email to android-building@googlegroups.com
To unsubscribe from this group, send email to
android-building+unsubscr...@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-building+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.