Google Git
Sign in
android / device / google / cuttlefish / f7b0bf505a3c777def40ab5643ad04e65a16af11
commitf7b0bf505a3c777def40ab5643ad04e65a16af11[log] [tgz]
authorA. Cody Schuffelen <[email protected]>Wed Jun 12 15:32:58 2024 -0700
committerA. Cody Schuffelen <[email protected]>Fri Jun 14 17:56:06 2024 -0700
treea59428b7cdbad155298495f6e9283b53f8c0e447
parent11b934644c3f12f0277a7673d83686ffa495d23d [diff]
Add a prototype setting to separate out the block device with vhost-user

Only currently works for the sdcard device in crosvm

Heavily based on the crosvm vhost-user gpu code in crosvm_manager.cpp by
natsu@.

On fully enabling it with crosvm, u-boot no longer seems able to inspect
the partition table and the partition entries are gone.
```
Driver                    uid uclass               Devices
----------------------------------------------------------
blk_partition             083 partition            <none>
```
versus a successful run:
```
Driver                    uid uclass               Devices
----------------------------------------------------------
blk_partition             083 partition            virtio-blk#22:1
                                                   virtio-blk#22:2
...
```

On fully enabling with QEMU there's some conflict with using it on any
devices.
```
2024-06-12T22:35:11.479077Z qemu-system-x86_64: Failed to read msg header. Read -1 instead of 12. Original request 1.
2024-06-12T22:35:11.479123Z qemu-system-x86_64: Failed to write msg. Wrote -1 instead of 20.
2024-06-12T22:35:11.479136Z qemu-system-x86_64: vhost VQ 0 ring restore failed: -22: Invalid argument (22)
2024-06-12T22:35:11.479151Z qemu-system-x86_64: Failed to set msg fds.
2024-06-12T22:35:11.479162Z qemu-system-x86_64: vhost_set_vring_call failed 22
2024-06-12T22:35:11.479195Z qemu-system-x86_64: Failed to set msg fds.
2024-06-12T22:35:11.479208Z qemu-system-x86_64: vhost_set_vring_call failed 22
2024-06-12T22:35:11.479305Z qemu-system-x86_64: vhost-user-blk: vhost start failed: Error starting vhost: Protocol error
[2024-06-12T22:35:11.479867813+00:00 ERROR crosvm::crosvm::sys::linux] error while running device block-0: invalid message
[2024-06-12T22:35:11.482253282+00:00 INFO  crosvm::crosvm::sys::linux] process for device block-0 (PID 42777) exited with code 1
[2024-06-12T22:35:11.482381564+00:00 INFO  crosvm::crosvm::sys::linux] all device processes have exited
[2024-06-12T22:35:11.482432972+00:00 INFO  crosvm] exiting with success
```

The only working mode I see now is enabling it for the sdcard disk,
which has minimal interaction with the bootloader.
```
$ cvd start --resume=false --vhost_user_block --daemon
$ adb shell
$ su
$ mkdir /data/local/mnt
$ mount /dev/vdc1 /data/local/mnt
$ echo "b" > /data/local/mnt/b
$ cat /data/local/mnt/b
```

Bug: b/346855591
Change-Id: I2d4b83d515d091bae5e8bae1bf50976de8798778
Test: cvd start --resume=false --vhost_user_block
11 files changed
tree: a59428b7cdbad155298495f6e9283b53f8c0e447
  1. .vscode/
  2. apex/
  3. build/
  4. common/
  5. guest/
  6. host/
  7. recovery/
  8. shared/
  9. system_image/
  10. tests/
  11. tools/
  12. vsoc_arm64/
  13. vsoc_arm64_minidroid/
  14. vsoc_arm64_only/
  15. vsoc_arm64_pgagnostic/
  16. vsoc_arm_minidroid/
  17. vsoc_riscv64/
  18. vsoc_riscv64_minidroid/
  19. vsoc_x86/
  20. vsoc_x86_64/
  21. vsoc_x86_64_host/
  22. vsoc_x86_64_minidroid/
  23. vsoc_x86_64_only/
  24. vsoc_x86_64_pgagnostic/
  25. vsoc_x86_only/
  26. rustfmt.toml ⇨ ../../../build/soong/scripts/rustfmt.toml
  27. .clang-format
  28. Android.bp
  29. Android.mk
  30. AndroidProducts.mk
  31. CleanSpec.mk
  32. default-permissions.xml
  33. dtb.img
  34. host_package.mk
  35. iwyu.imp
  36. METADATA
  37. OWNERS
  38. OWNERS_techleads
  39. PREUPLOAD.cfg
  40. README.md
  41. required_images
  42. TEST_MAPPING
README.md

Cuttlefish Getting Started

Try Cuttlefish

  1. 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:

  • When running on an ARM machine, the most direct way is to check for the existence of /dev/kvm. Note that this method can also be used to confirm support of KVM on any environment.

  1. 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.

  2. Go to http://ci.android.com/

  3. Enter a branch name. Start with aosp-main if you don‘t know what you’re looking for

  4. Navigate to aosp_cf_x86_64_phone and click on userdebug for the latest build

For ARM, use branch aosp-main-throttled and device target aosp_cf_arm64_only_phone-trunk_staging-userdebug

  1. Click on Artifacts

  2. 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

  3. Scroll down to cvd-host_package.tar.gz. You should always download a host package from the same build as your images.

  4. 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

  5. Launch cuttlefish with:

$ HOME=$PWD ./bin/launch_cvd

Debug Cuttlefish

You can use adb to debug it, just like a physical device:

$ ./bin/adb -e shell

Launch Viewer (WebRTC)

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.

Stop Cuttlefish

You will need to stop the virtual device within the same directory as you used to launch the device.

$ HOME=$PWD ./bin/stop_cvd