Google Git
Sign in
android / device / google / cuttlefish / bd76f6911
commitbd76f6911b0a8d88f72d507d8f69b55e6cac0003[log] [tgz]
authorDmitrii Merkurev <dimorinny@google.com>Fri Jan 13 00:40:34 2023 +0000
committerDmitrii Merkurev <dimorinny@google.com>Tue Jan 17 23:32:50 2023 +0000
treeb1341d7b5bc444dc899a574a98e5de5064df84f5
parenta6e270392a8c5ee91d5fbecbe6476f39f337d408 [diff]
Fix SIGPIPE handling in the socket_vsock_proxy tool

Was able to catch that with some of fastboot clients
(for example default fastboot in the acloud instances)
fastboot connection is unexpectively closed and
the whole proxy process is turned down because of that.

According to strace this problem is causeŠ² by SIGPIPE signal
default behaviour, which according to jemoreira comment on
Proxy must be disabled and handled as a regular write error.

So doing it to fix this particular problem and improve the
stability of adb / fastboot.

Test: checked fastboot proxy is not crashing with the different fastboot clients
Test: checked adb works with --adb_mode=vsock_tunnel
Bug: 265289715

Change-Id: Ic781bf26526393c24e52b72c5cafbe8a2f23e64f
Signed-off-by: Dmitrii Merkurev <dimorinny@google.com>
1 file changed
tree: b1341d7b5bc444dc899a574a98e5de5064df84f5
  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_arm_only/
  14. vsoc_x86/
  15. vsoc_x86_64/
  16. vsoc_x86_64_minidroid/
  17. vsoc_x86_64_only/
  18. vsoc_x86_only/
  19. rustfmt.toml ⇨ ../../../build/soong/scripts/rustfmt.toml
  20. .clang-format
  21. Android.bp
  22. Android.mk
  23. AndroidProducts.mk
  24. CleanSpec.mk
  25. default-permissions.xml
  26. dtb.img
  27. fetcher.mk
  28. host_package.mk
  29. iwyu.imp
  30. METADATA
  31. OWNERS
  32. PREUPLOAD.cfg
  33. README.md
  34. required_images
  35. 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