Google Git
Sign in
android / device / google / cuttlefish / 189bbc73e
commit189bbc73e05f88bdcafbbf9af05fb43fc0b16816[log] [tgz]
authorJeongik Cha <jeongik@google.com>Fri Sep 08 18:06:37 2023 +0900
committerJeongik Cha <jeongik@google.com>Mon Sep 11 03:42:35 2023 +0000
tree24241968d5cc79355dee039e702a5591d7c783d8
parent989f3dae17dc00454c17554ac368f76275af77ab [diff]
avb_keys=/avb for system_dlkm in cuttlefish

we can use vbmeta from end of the image in the case of
mixing different products' images

Bug: 298075407
Bug: 289368466
Test: booting
Change-Id: If2c2c3f58ef7f48024caa9441d69b89fc6fae28a
1 file changed
tree: 24241968d5cc79355dee039e702a5591d7c783d8
  1. apex/
  2. build/
  3. common/
  4. guest/
  5. host/
  6. recovery/
  7. shared/
  8. tests/
  9. tools/
  10. vsoc_arm64/
  11. vsoc_arm64_minidroid/
  12. vsoc_arm64_only/
  13. vsoc_arm64_pgagnostic/
  14. vsoc_arm_minidroid/
  15. vsoc_riscv64/
  16. vsoc_riscv64_minidroid/
  17. vsoc_x86/
  18. vsoc_x86_64/
  19. vsoc_x86_64_host/
  20. vsoc_x86_64_minidroid/
  21. vsoc_x86_64_only/
  22. vsoc_x86_only/
  23. rustfmt.toml ⇨ ../../../build/soong/scripts/rustfmt.toml
  24. .clang-format
  25. Android.bp
  26. Android.mk
  27. AndroidProducts.mk
  28. CleanSpec.mk
  29. default-permissions.xml
  30. dtb.img
  31. fetcher.mk
  32. host_package.mk
  33. iwyu.imp
  34. METADATA
  35. OWNERS
  36. PREUPLOAD.cfg
  37. README.md
  38. required_images
  39. TEST_MAPPING
README.md

Cuttlefish Getting Started

Try Cuttlefish

  1. Make sure virtualization with KVM is available.

    grep -c -w "vmx\|svm" /proc/cpuinfo

    This should return a non-zero value. If running on a cloud machine, this may take cloud-vendor-specific steps to enable. For Google Compute Engine specifically, see the GCE guide.

ARM specific steps:

  • When running on an ARM machine, the most direct way is to check for the existence of /dev/kvm. Note that this method can also be used to confirm support of KVM on any environment.

  1. Download, build, and install the host debian packages:

    sudo apt install -y git devscripts config-package-dev debhelper-compat golang curl
git clone https://github.com/google/android-cuttlefish
cd android-cuttlefish
for dir in base frontend; do
  cd $dir
  debuild -i -us -uc -b -d
  cd ..
done
sudo dpkg -i ./cuttlefish-base_*_*64.deb || sudo apt-get install -f
sudo dpkg -i ./cuttlefish-user_*_*64.deb || sudo apt-get install -f
sudo usermod -aG kvm,cvdnetwork,render $USER
sudo reboot

    The reboot will trigger installing additional kernel modules and applying udev rules.

  2. Go to http://ci.android.com/

  3. Enter a branch name. Start with aosp-master if you don‘t know what you’re looking for

  4. Navigate to aosp_cf_x86_64_phone and click on userdebug for the latest build

For ARM, use branch aosp-master-throttled-copped and device target aosp_cf_arm64_only_phone-userdebug

  1. Click on Artifacts

  2. Scroll down to the OTA images. These packages look like aosp_cf_x86_64_phone-img-xxxxxx.zip -- it will always have img in the name. Download this file

  3. Scroll down to cvd-host_package.tar.gz. You should always download a host package from the same build as your images.

  4. On your local system, combine the packages:

    mkdir cf
cd cf
tar xvf /path/to/cvd-host_package.tar.gz
unzip /path/to/aosp_cf_x86_64_phone-img-xxxxxx.zip

  5. Launch cuttlefish with:

$ HOME=$PWD ./bin/launch_cvd

Debug Cuttlefish

You can use adb to debug it, just like a physical device:

$ ./bin/adb -e shell

Launch Viewer (WebRTC)

When launching with ---start_webrtc (the default), you can see a list of all available devices at https://localhost:8443 . For more information, see the WebRTC on Cuttlefish documentation.

Stop Cuttlefish

You will need to stop the virtual device within the same directory as you used to launch the device.

$ HOME=$PWD ./bin/stop_cvd