Ferrochrome: Re-enable tests with more safe guards

This CL includes following changes
  - Ensure whether adb root success
  - Find and launch VM launcher based on intent action
  - Ensure that both host and DUT have enough space
  - Ensure arm64 arch
  - Ensure non-virtual device
  - Remove pushed image when test is finished (kill vmlauncher for it)
  - Enable verbose log by 'set -x'

Bug: 346742552
Change-Id: I74eb02821d3979f7548e15551a3e1c51938d9f71
Test: Locally on aosp_shiba, \
  tangorpro with go/abtd/run/L12000030004706790
5 files changed
tree: 02c17199c443b87537d805bfaf76fa652dc94503
  1. apex/
  2. apkdmverity/
  3. authfs/
  4. compos/
  5. demo/
  6. demo_native/
  7. docs/
  8. encryptedstore/
  9. ferrochrome_app/
  10. flags/
  11. java/
  12. launcher/
  13. libs/
  14. microdroid/
  15. microdroid_manager/
  16. pvmfw/
  17. rialto/
  18. service_vm/
  19. tests/
  20. virtualizationmanager/
  21. virtualizationservice/
  22. vm/
  23. vm_payload/
  24. vmbase/
  25. vmclient/
  26. vmlauncher_app/
  27. zipfuse/
  28. .clang-format
  29. .gitignore
  30. Android.bp
  31. avf_flags.aconfig
  32. OWNERS
  33. PREUPLOAD.cfg
  34. README.md
  35. rustfmt.toml
  36. TEST_MAPPING
README.md

Android Virtualization Framework (AVF)

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: