commit | 84135dc09f93ab1cf0d98ca03c21ef9b95511e45 | [log] [tgz] |
---|---|---|
author | Dmitrii Merkurev <dimorinny@google.com> | Sun Jan 08 16:18:19 2023 +0000 |
committer | Dmitrii Merkurev <dimorinny@google.com> | Sun Jan 08 16:18:19 2023 +0000 |
tree | 58d94841ccb5741a0cf605bc19f33957116b5144 | |
parent | 30a7fbaed89e72d135617a2182d7f2d3c5b8fda7 [diff] |
Start migrating to grub-mkimage for grub efi binary generation Use grub-mkimage to generate grub monolith. Leaving fallback logic in grub-mkimage isn't presented everywhere As a next step will introduce grub flow realted metrics and after making sure monolith binaries are not used anywhere will fully migrate to grub-mkimage Test: launch_cvd for Android and Linux flow make sure grub-mkimage is working Test: checked it's possible to generate grub image inside mtt container Bug: 260338443 Change-Id: I5e120f1bf29cbfc9c3eeb43302f839300086ec1a Signed-off-by: Dmitrii Merkurev <dimorinny@google.com>
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