commit | 5622eff4a53f514909b20339cc5e88376809ef5e | [log] [tgz] |
---|---|---|
author | A. Cody Schuffelen <[email protected]> | Mon Jun 24 16:30:44 2024 -0700 |
committer | A. Cody Schuffelen <[email protected]> | Mon Jun 24 16:30:44 2024 -0700 |
tree | 939251b2fba74e583791bcd4a9a8860e19fa29a7 | |
parent | 1826477c0b6aebaf06cb4bb6eb11842d3e396057 [diff] |
Unset default sandbox2 timeout in process_sandboxer By default sandbox2 will time out a sandboxed process after 2 minutes of wall time or 1024 seconds of cpu time. Lift these requirements since Cuttlefish includes long-running service host processes. https://cs.android.com/android/platform/superproject/main/+/main:external/sandboxed-api/sandboxed_api/sandbox2/limits.h;l=116;drc=d451478e26c0352ecd6912461e867a1ae64b17f5 Bug: b/349193629 Test: `cvd start --enable_host_sandbox=true`, wait 2 minutes Change-Id: If7927fdfecddabbdd17c572acbbec2413a5ae915
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 sudo apt install devscripts equivs for dir in base frontend; do pushd $dir sudo mk-build-deps -i dpkg-buildpackage -uc -us popd 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