History

Inseob Kim 72f06a3489 Include microdroid files to virt apex All files to run microdroid is now included to the com.android.virt APEX: - super image - boot images - vbmeta images - bootloader - uboot_env image - cdisk json config Also the documentation README.md and microdroid host tests are updated too. Bug: 184803590 Test: follow instructions on README.md Test: atest MicrodroidHostTestCases Change-Id: I71f0e32ca774b351d9f49af2754f0a1c786c2400		2021-04-12 16:15:38 +09:00
..
Android.bp	Sign the bootloader using avbtool	2021-04-09 11:24:33 +09:00
README.md	Include microdroid files to virt apex	2021-04-12 16:15:38 +09:00
dummy_dtb.img	Build vendor_boot image for microdroid	2021-02-04 23:39:09 +09:00
empty_kernel	Add MicrodroidHostTestCases	2021-03-12 13:36:15 +09:00
fstab	Reland "Add microdroid_vendor"	2021-03-03 14:56:18 +00:00
init.rc	Remove services except for adb	2021-03-11 14:20:24 +09:00
microdroid_cdisk.json	Include microdroid files to virt apex	2021-04-12 16:15:38 +09:00
microdroid_file_contexts	Add microdroid_file_contexts to build image	2021-02-03 14:50:28 +09:00
microdroid_vendor_file_contexts	Reland "Add microdroid_vendor"	2021-03-03 14:56:18 +00:00
plat_sepolicy_vers.txt	Reland "Add microdroid_vendor"	2021-03-03 14:56:18 +00:00
uboot-env.txt	Microdroid uses android boot image header V4	2021-03-05 18:56:34 +09:00

README.md

Microdroid

Microdroid is a (very) lightweight version of Android that is intended to run on on-device virtual machines. It is built from the same source code as the regular Android, but it is much smaller; no system server, no HALs, no GUI, etc. It is intended to host headless & native workloads only.

Building

You need a VIM3L board. Instructions for building Android for the target, and flashing the image can be found here.

Then you install com.android.virt APEX. All files needed to run microdroid are included in the APEX, which is already in the yukawa (VIM3L) target. You can of course build and install the APEX manually.

$ source build/envsetup.sh
$ choosecombo 1 aosp_arm64 userdebug // actually, any arm64-based target is ok
$ m com.android.virt
$ adb install $ANDROID_PRODUCT_OUT/system/apex/com.android.virt.apex
$ adb reboot

Running

Copy the artifacts to the temp directory, create the composite image using mk_cdisk, and run it via crosvm. For now, some other files have to be manually created. In the future, you won't need these, and this shall be done via virtmanager.

$ adb shell 'cp /apex/com.android.virt/etc/microdroid_bootloader /data/local/tmp/bootloader'
$ adb shell 'cp /apex/com.android.virt/etc/fs/*.img /data/local/tmp'
$ adb shell 'cp /apex/com.android.virt/etc/uboot_env.img /data/local/tmp'
$ adb shell 'dd if=/dev/zero of=/data/local/tmp/misc.img bs=4k count=256'
$ adb shell 'cd /data/local/tmp; /apex/com.android.virt/bin/mk_cdisk /apex/com.android.virt/etc/microdroid_cdisk.json os_composite.img'
$ adb shell 'cd /data/local/tmp; /apex/com.android.virt/bin/crosvm run --cid=5 --disable-sandbox --bios=bootloader --serial=type=stdout --disk=os_composite.img'

The CID in --cid parameter can be anything greater than 2 (VMADDR_CID_HOST).

ADB

$ adb forward tcp:8000 vsock:5:5555
$ adb connect localhost:8000

5 in vsock:5 should match with the CID number that was given to crosvm. 5555 must be the value. 8000 however can be any port in the development machine.

Done. Now you can log into microdroid. Have fun!

$ adb -s localhost:8000 shell