pa-fazil
/
android_packages_modules_Virtualization
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
android_packages_modules_Vi.../microdroid/bootconfig.normal

12 lines
232 B
Plaintext
Raw Normal View History

Don't start adb if debugging is off * Debug level None: adb is not supported * Debug level app_only: adb is supported, but rooting is prohibited * Debug level full: adb is supported and can be rooted Bug: 201362865 Test: start a VM with `--debug none` and try to connect to the VM via adb. It doesn't work as expected. Change-Id: I95fe01e722d974ff1eb29469ac96abe7d785288d
2021-10-18 06:51:59 +00:00
# ro.debuggable is off
androidboot.microdroid.debuggable=0
# Console output is not redirect to the host-side.
Define debug levels Previously, a VM can be configured as running in debug mode or not. However, the debug mode was not defined clearly and debugging features like logging and adb-shell were actually left enabled even when the debug mode is off. This CL re-defines the debuggability of a VM. A VM has a debug level which can be either of these three: 1. None: In this level, VM is not debuggable at all. No log is exported from the VM, and debugger can't be attached to any process in the VM. adb-shell of course is not supported. 2. App-only: In this level, only the app payload is debuggable. Logs from the app process is exported to the host and the process can be attached to debugger. adb-shell is not supported. 3. Full: In this level, the VM is fully debuggable. All logs including kernel logs are exported to the VM and developers can adb-shell into the VM. Note that this CL doesn't fully implement all the levels yet, but implements the framework around supporting multiple debug levels. Specifically, each debug level is associated with a bootconfig image. Each image has config values each of which enables or disables a debugging feature. For example, bootconfig images for the none and app-only levels have "kernel.console = none" to not show kernel console output. The `vm` tool and the Java APIs are also amended accordingly. The debug level can be set via `--debug <level>` flag and the `DebugLevel(...)` method. Future work: * Implement each debug level * Each level uses different vm-instance image. Debug level is stored in the instance image and is compared against the given level when microdroid boots. * Sign bootconfig images with avb and let uboot verify them (b/203031847) Bug: 201362865 Test: atest MicrodroidHostTestCases Test: adb shell /apex/com.android.virt/bin/vm run-app /data/local/tmp/virt/MicrodroidDemoApp.apk /data/local/tmp/virt/MicrodroidDemoApp.apk.idsig /data/local/tmp/virt/instance.img assets/vm_config.json shows ... Created VM from "/data/local/tmp/virt/MicrodroidDemoApp.apk"!"assets/vm_config.json" with CID 13, state is NOT_STARTED. Started VM, state now STARTING. Hello Microdroid /mnt/apk/lib/arm64-v8a/MicrodroidTestNativeLib.so hello microdroid , which is without logs from the bootloader and the kernel Change-Id: I897dcd88723f014524d2cd2b6ffaa6f9fb5696d6
2021-10-14 15:02:12 +00:00
kernel.console = null
Don't start adb if debugging is off * Debug level None: adb is not supported * Debug level app_only: adb is supported, but rooting is prohibited * Debug level full: adb is supported and can be rooted Bug: 201362865 Test: start a VM with `--debug none` and try to connect to the VM via adb. It doesn't work as expected. Change-Id: I95fe01e722d974ff1eb29469ac96abe7d785288d
2021-10-18 06:51:59 +00:00
# ADB is not enabled.
androidboot.adb.enabled=0
Run logd only when debug_level is set When debug_level is set to none, logd is not started at all. Bug: 200914564 Test: run a VM with and without --debug full Change-Id: Idb1ea3753067242eb0dcd53d3ae783e9e947ca32
2021-10-18 09:33:28 +00:00
# logd is not enabled
androidboot.logd.enabled=0