virtmgr: migrate from vm_control to crosvm_control

`vm_control` is a crosvm internal API that is subject to arbitrary
refactoring. `crosvm_control` is the stable public API equivalent.

It is no longer possible to detect the `ENOTSUP` case when requesting
balloon stats. Contrary to what the comment said, that case only occurs
when the VM was configured without a virtio-balloon device (at least at
HEAD). For simplicity and consistency with `set_memory_balloon`,
`get_memory_balloon` has been changed to consider this case to be an
error. There are no users of that function yet, so it should be safe to
change.

(If the balloon device is present, but hasn't been initialized by the
guest yet, the call will simply block until it has been initialized,
which is possibly undesirable and needs rethinking. That is true both
before and after this change)

Test: m
Bug: 366271643
Change-Id: Ic58c3c9cf44cb06d517f8739d73f845d22832609
2 files changed
tree: 943aecd20b59f91e259b0521d3dda78db745729e
  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: