commit | 584da616165b42cf61de845eeea2951b379b0c6b | [log] [tgz] |
---|---|---|
author | Dennis Song <[email protected]> | Thu Dec 14 07:05:30 2023 +0000 |
committer | Automerger Merge Worker <[email protected]> | Thu Dec 14 07:05:30 2023 +0000 |
tree | a97bb99961b1d66def1b2e2fd64208443beb2cdb | |
parent | 39c004d41e553b298dcf44b5887956e6d64b67ba [diff] | |
parent | 294a79132e404f5b0c57908b58c67eed30a7dbb1 [diff] |
Merge "Print the launcher.log while establishing the ssh tunnel" into main am: 551811ad31 am: e050389ccb am: 294a79132e Original change: https://android-review.googlesource.com/c/device/google/cuttlefish/+/2854383 Change-Id: I49675f6d1c76b68f4b9281c6cb7b61c46968412b Signed-off-by: Automerger Merge Worker <[email protected]>
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-userdebug
Click 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