Gitiles
Code Review Sign In
gerrit.omnirom.org / android_packages_modules_Virtualization / 9bffc3b515a466fa83b4d4c22749902178f6253c
commit9bffc3b515a466fa83b4d4c22749902178f6253c[log] [tgz]
authorAlan Stokes <alanstokes@google.com>Wed Jan 25 09:45:54 2023 +0000
committerAlan Stokes <alanstokes@google.com>Wed Jan 25 13:52:28 2023 +0000
tree79b60f9f2aa9b5ee50f8e0995055f4c69c085bc5
parent630e0c3138c10693d84028fb47d8dab85fe3cd3e [diff]
Cache package name not APK path

The APK path for an app can change, e.g. if an update is
installed. Where the caller hasn't specified an explicit APK path we
should store the package name rather than the current APK path in the
config file, and map it to the APK path on run().

I modified the builder/config tests to cover the changes.

I've manually tested this using my demo app and it is now possible to
start a VM after the APK is updated; it then fails (as expected)
because the APK hash has changed. And it succeeds if I reinstall the
same APK (so the path changes, but the hash doesn't).

Bug: 266395810
Test: atest MicrodroidTests
Change-Id: Ifa0680d3e6bc805282674eb37c89190a996a7af4
4 files changed
tree: 79b60f9f2aa9b5ee50f8e0995055f4c69c085bc5
  1. apex/
  2. apkdmverity/
  3. authfs/
  4. avmd/
  5. compos/
  6. demo/
  7. docs/
  8. encryptedstore/
  9. javalib/
  10. launcher/
  11. libs/
  12. microdroid/
  13. microdroid_manager/
  14. pvmfw/
  15. rialto/
  16. tests/
  17. virtualizationmanager/
  18. virtualizationservice/
  19. vm/
  20. vm_payload/
  21. vmbase/
  22. vmclient/
  23. zipfuse/
  24. rustfmt.toml ⇨ ../../../build/soong/scripts/rustfmt.toml
  25. .clang-format
  26. .gitignore
  27. Android.bp
  28. OWNERS
  29. PREUPLOAD.cfg
  30. README.md
  31. TEST_MAPPING
README.md

Virtualization

This repository contains userspace services related to running virtual machines on Android, especially protected virtual machines. See the getting started documentation and Microdroid README for more information.