virtmgr: disable disk file locking in crosvm

crosvm calls `man 2 flock` on disk image files. It used to only call it
on the "root" image, but now it calls it on all the nested images, e.g.
the "component" files in a composite disk image.

That isn't necessarily a bad thing, but the SELinux policies don't allow
it. For example, some of the disk images used by Microdroid are labelled
with the very generic "system_file" context. We should consider changing
the policies, but, in meantime, disable locking isn't a big deal.
Generally the files are either read-only at the FS level (and so the
locking is mostly redundant) or are generated per VM images (and so no
conflict is likely).

Bug: 364645148, 330911976
Test: launch microdroid
Change-Id: I5d64ee343d56620df4389c57dbbb99a57e2c3c8c
1 file changed
tree: ee2788ae2a7fef930303e5bef4a83191e4095fc9
  1. android/
  2. build/
  3. docs/
  4. guest/
  5. libs/
  6. microfuchsia/
  7. tests/
  8. .clang-format
  9. .gitignore
  10. Android.bp
  11. dice_for_avf_guest.cddl
  12. OWNERS
  13. PREUPLOAD.cfg
  14. README.md
  15. rustfmt.toml
  16. 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: