Add new, specific credential flags The "new" `GetCredentialSourceLegacy` is nearly identical to the previous `GetCredentialSource`, except the new `ReadFileContents` was factored out into a helper to keep all of that code in sync. The error messages will be slightly more verbose now. The flag parsing (and the `CredentialSource` retrieval logic) enforce mutual exclusion between these new flags and the deprecated `credential_source` to avoid an explicit or implicit precedence between them. Bug: 320798446 Test: cvd fetch --target_directory=fetch_test --default_build=aosp-main Test: # works as expected, falls back to the legacy code and uses `.dat` file or no credentials Test: cvd fetch --credential_source=test --use_gce_metadata=true --credential_filepath=abc --service_account_filepath=123 Test: # the error message should show a count of "4" for set credential flags, detecting the overlap of the previous flag and the new ones Test: cvd fetch --target_directory=fetch_test --default_build=aosp-main --use_gce_metadata=true Test: # errors, no fallback Test: cvd fetch --target_directory=fetch_test --default_build=aosp-main --credential_filepath=abc Test: # errors that the file does not exist, no fallback Test: cvd fetch --target_directory=fetch_test --default_build=aosp-main --service_account_filepath=abc Test: # errors that the file does not exist, no fallback Change-Id: Ie4bc6fdbdcb54d97fc9466d328629b9cfeeef6f6
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:
/dev/kvm. Note that this method can also be used to confirm support of KVM on any environment.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.
Go to http://ci.android.com/
Enter a branch name. Start with aosp-main if you don‘t know what you’re looking for
Navigate to aosp_cf_x86_64_phone and click on userdebug for the latest build
aosp-main-throttled and device target aosp_cf_arm64_only_phone-trunk_staging-userdebugClick on Artifacts
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
Scroll down to cvd-host_package.tar.gz. You should always download a host package from the same build as your images.
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
Launch cuttlefish with:
$ HOME=$PWD ./bin/launch_cvd
You can use adb to debug it, just like a physical device:
$ ./bin/adb -e shell
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.
You will need to stop the virtual device within the same directory as you used to launch the device.
$ HOME=$PWD ./bin/stop_cvd