Optimize identical configs

While writing a demo app I realized it makes sense to call
vm.setConfig immediately after vmm.getOrCreate - so if the VM already
existed but had a different config, we update it to what we want, or
find out it's incompatible.

And if in fact we just created the VM it would make sense for
setConfig to do minimal work, since old and new config will be the
same object.

Bug: 243512240
Test: atest MicrodroidTests
Change-Id: I0732eec3cd68ef9ad8d4e7b143ce49c46096f82b
2 files changed
tree: 896919e474653ff715a59e76deb724c635f4e2ec
  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. .clang-format
  25. .gitignore
  26. Android.bp
  27. OWNERS
  28. PREUPLOAD.cfg
  29. README.md
  30. 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.