Update run_cvd to handle non-vsock frontend

Adds a bool to specify whether vnc frontend was launched.

aosp/1186883 changed the behavior of checking whether or not to
enable the frontend flags in the vmm from whether or not all of
the shared fds were created successfully to checking whether or
not any server vsock ports were set. This was equivilent to the
original check because one vsock port was always set for sending
frames. But aosp/1186879 updates run_cvd to not set any vsock
ports in the case of crosvm with GPU acceleration.

Bug: b/128842306
Test: locally built and ran cuttlefish with crosvm<-wayland->vnc
Change-Id: Ib104a075a643a50098b84a697f7c1a46b9098f2b
5 files changed
tree: d943c354ee332b3d80a7370af9f5e3ab70239cf9
  1. common/
  2. guest/
  3. host/
  4. shared/
  5. tests/
  6. tools/
  7. vsoc_arm64/
  8. vsoc_x86/
  9. vsoc_x86_64/
  10. vsoc_x86_noapex/
  11. Android.bp
  12. Android.mk
  13. AndroidProducts.mk
  14. CleanSpec.mk
  15. dtb.img
  16. fetcher.mk
  17. host_package.mk
  18. OWNERS
  19. README.md
  20. task_profiles.json
  21. TEST_MAPPING
README.md

So you want to try cuttlefish?

  1. Download, build, and install the host debian package:
git clone https://github.com/google/android-cuttlefish
cd android-cuttlefish
debuild -i -us -uc -b
sudo dpkg -i ../cuttlefish-common_*_amd64.deb
sudo apt-get install -f
  1. Go to http://ci.android.com/
  2. Enter a branch name. Start with aosp-master if you don't know what you're looking for
  3. Navigate to aosp_cf_x86_phone and click on userdebug for the latest build
  4. Click on Artifacts
  5. Scroll down to the OTA images. These packages look like aosp_cf_x86_phone-img-xxxxxx.zip -- it will always have img in the name. Download this file
  6. Scroll down to cvd-host_package.tar.gz. You should always download a host package from the same build as your images.
  7. 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_phone-img-xxxxxx.zip
  1. Launch cuttlefish with:

    $ HOME=$PWD ./bin/launch_cvd

  2. Stop cuttlefish with:

    $ HOME=$PWD ./bin/stop_cvd

So you want to debug cuttlefish?

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

$ ./bin/adb -e shell

So you want to see cuttlefish?

You can use the TightVNC JViewer. Once you have downloaded the TightVNC Java Viewer JAR in a ZIP archive, run it with

$ java -jar tightvnc-jviewer.jar -ScalingFactor=50 -Tunneling=no -host=localhost -port=6444

Click "Connect" and you should see a lock screen!