commit | 4e54d0be6092fc4a51a31a948fbaced96fb53c9f | [log] [tgz] |
---|---|---|
author | JaeMan Park <[email protected]> | Mon May 22 08:06:53 2023 +0900 |
committer | Android Build Coastguard Worker <[email protected]> | Thu Jun 15 18:45:49 2023 +0000 |
tree | ae727530491c411a088eeee76a3f68fb171638ca | |
parent | 1be61cff9eee3524ccfc79c3e3ebc750a656cd2e [diff] |
Re-land: Move unix sockets to /tmp/cf_avd Bug: 279085447 Test: launch_cvd Check unix sockets are under /tmp/cf_avd/cvd-1/... Not ~/cuttlefush_runtime.1/... (cherry picked from https://googleplex-android-review.googlesource.com/q/commit:136b95e7004ce622789531084de669f4fd3bce29) Merged-In: Ia264affc58ade2a8261977dbaa0c05cd7dc50d8c Change-Id: Ia264affc58ade2a8261977dbaa0c05cd7dc50d8c
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-master
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-master-throttled-copped
and device target aosp_cf_arm64_only_phone-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