commit | 4fdf103ad9a3e0929bd4e60576b5fa15b37e2303 | [log] [tgz] |
---|---|---|
author | Nikita Ioffe <ioffe@google.com> | Tue Apr 16 15:03:02 2024 +0000 |
committer | Nikita Ioffe <ioffe@google.com> | Tue Apr 16 15:03:02 2024 +0000 |
tree | bea016f6143e0f4a50a2141e96aa4e21d8c7c8b0 | |
parent | e7df57a82a53a12070f3bed2318f4208156df6fb [diff] |
Hide android14-6.1-pkvm_experimental GKI behind separate product flag The new PRODUCT_AVF_MICRODROID_GUEST_GKI_VERSION flag is used to define which GKI image to include into the com.android.virt APEX. This flag will be used in our internal testing of device assignment feature. This product flag impacts the GSI image. I think this is fine, since the device assignment (and hence microdroid vendor modules) features are not mandated for Android V, so the GSI build won't have the GKI image inside com.android.virt APEX. Ideally, we would prefer to move the GKI image for Microdroid guest outside of the com.android.virt APEX to somewhere on /system_ext, however such change will be quite involved, as it will require significant changes to the signing scripts. Until we do such refactoring, this temporary approach (I think) should suffice. Bug: 329383978 Test: adb shell /apex/com.android.virt/bin/vm info Test: AVF presubmit Change-Id: I1016b90c5d9b17820726304d25f5cfdfb7f3bb25
Android Virtualization Framework (AVF) provides secure and private execution environments for executing code. AVF is ideal for security-oriented use cases that require stronger isolation assurances over those offered by Android’s app sandbox.
Visit our public doc site to learn more about what AVF is, what it is for, and how it is structured. This repository contains source code for userspace components of AVF.
If you want a quick start, see the getting started guideline and follow the steps there.
For in-depth explanations about individual topics and components, visit the following links.
AVF components:
AVF APIs:
How-Tos: