Google Git
Sign in
android / device / google / cuttlefish / ca15fe231
commitca15fe231a11d454d1f3d6b0a0147d5ac0d4ba26[log] [tgz]
authorEthan Lee <ethanalee@google.com>Wed Oct 23 07:58:42 2024 +0000
committerEthan Lee <ethanalee@google.com>Wed Oct 23 07:58:42 2024 +0000
tree2737ac37f7c7fa1be78b4e989fa8bc5a4f55a266
parentce99eafd13bce8809764dbe95efe792d5759892d [diff]
Add support for multiple custom partition paths

Multiple custom partition paths can be specified now, resulting in the
following disk partitions in the case of multiple custom partitions:
- /dev/block/by-name/custom
- /dev/block/by-name/custom_1
- /dev/block/by-name/custom_2
Thus, any older versions of cuttlefish will still support the "custom"
name.

Test: m && m custom_images && cvd create
--custom_partition_path="$OUT/oem.img;$OUT/oem2.img"
Test: adb shell && df | grep oem
Fixes: 374932703
Change-Id: I4381fbe1e17bf0131905e88889b24330c1cd6bb5
1 file changed
tree: 2737ac37f7c7fa1be78b4e989fa8bc5a4f55a266
  1. .vscode/
  2. apex/
  3. build/
  4. common/
  5. guest/
  6. host/
  7. recovery/
  8. shared/
  9. tests/
  10. tools/
  11. vsoc_arm/
  12. vsoc_arm64/
  13. vsoc_arm64_minidroid/
  14. vsoc_arm64_only/
  15. vsoc_arm64_pgagnostic/
  16. vsoc_arm_minidroid/
  17. vsoc_riscv64/
  18. vsoc_riscv64_minidroid/
  19. vsoc_x86/
  20. vsoc_x86_64/
  21. vsoc_x86_64_host/
  22. vsoc_x86_64_minidroid/
  23. vsoc_x86_64_only/
  24. vsoc_x86_64_pgagnostic/
  25. vsoc_x86_only/
  26. rustfmt.toml ⇨ ../../../build/soong/scripts/rustfmt.toml
  27. .clang-format
  28. Android.bp
  29. AndroidProducts.mk
  30. CleanSpec.mk
  31. default-permissions.xml
  32. dtb.img
  33. iwyu.imp
  34. METADATA
  35. OWNERS
  36. OWNERS_techleads
  37. PREUPLOAD.cfg
  38. README.md
  39. required_images
  40. 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
sudo apt install devscripts equivs
for dir in base frontend; do
  pushd $dir
  sudo mk-build-deps -i
  dpkg-buildpackage -uc -us
  popd
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-main 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-main-throttled and device target aosp_cf_arm64_only_phone-trunk_staging-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