Gitiles
Code Review Sign In
gerrit-public.fairphone.software / device / google / cuttlefish / 829ad255b2887ec68b709b343d829d37d214c8a3
commit829ad255b2887ec68b709b343d829d37d214c8a3[log] [tgz]
authorAlistair Delva <adelva@google.com>Wed May 13 16:47:55 2020 -0700
committerAlistair Delva <adelva@google.com>Thu May 14 03:08:59 2020 +0000
tree731a0770cf50981edc6d929d63f8d628ca490ab0
parent3aac3e1f7a151b7dec16956eb32889b23b359f9a [diff]
Fix networking on aarch64

Due to limitations in the Android build system, we currently build all
of the host tools as x86_64, and then use qemu-user to translate them to
aarch64 on the target device. However, qemu-user can't translate TUN
ioctls, so the tap devices are not correctly configured for crosvm and
networking is broken. This works around the problem by pushing the
critical configuration out of process.

The correct longer term fix for this problem is to modify crosvm to
accept tap devices by name; as we provide crosvm natively for aarch64,
no translation occurs, and crosvm can freely use the TUN ioctls.

Bug: 156322936
Change-Id: I9fba825324b037e907394064724e6adfab93c3ed
Merged-In: I9fba825324b037e907394064724e6adfab93c3ed
4 files changed
tree: 731a0770cf50981edc6d929d63f8d628ca490ab0
  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. default-permissions.xml
  16. dtb.img
  17. fetcher.mk
  18. host_package.mk
  19. OWNERS
  20. README.md
  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!