| commit | f0b59a8ad8b9370680e9cdea309df032a56d3608 | [log] [tgz] |
|---|---|---|
| author | retroinspect <sangachoi@google.com> | Thu Aug 31 09:05:23 2023 +0000 |
| committer | retroinspect <sangachoi@google.com> | Sat Sep 02 02:15:00 2023 +0000 |
| tree | b0a7f60739003cfb9b41f943a8431d7ab0b21de3 | |
| parent | a119dc299c094f244d3e1c36f957a1541d43b527 [diff] |
Add group_name flag to cvd load config
`group_name` is needed to distinguish different groups easily, for local & cloud based management of cvd environments.
`cvd load` is now able to accept group_name as a parameter of json configuration file.
An example of config.json is as follows:
```
{
"instances": [{
"@import": "phone",
"vm": {
"memory_mb": 8192,
"setupwizard_mode": "OPTIONAL",
"cpus": 4
},
"disk": {
"default_build": "@ab/10741043/aosp_cf_x86_64_phone-trunk_staging-userdebug"
}
}],
"common": {
"group_name": "baz"
}
}
```
Bug: 298332322
Test: Make config.json file and enter `cvd load config.json`
Change-Id: I738fc3bca1c890cf373162cbcd2a9b2597243b86
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-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