commit | 329b8dee3a6c11b1039354e761778987025db399 | [log] [tgz] |
---|---|---|
author | Cody Schuffelen <schuffelen@google.com> | Mon Nov 04 15:11:06 2019 -0800 |
committer | Cody Schuffelen <schuffelen@google.com> | Fri Nov 08 15:28:37 2019 -0800 |
tree | 4521a576bcf1c117feed9d83f2eaa6dd226dbdc7 | |
parent | 46487c033c6ac52b83dae74bafd746f0e15c0b5d [diff] |
Retrofit vsoc_input_service to use vsock This allows using vsoc_input_service under qemu without the vsoc/ivshmem support that is missing in 4.19 gki. The alternative is to use virtio-input, but in qemu this requires forwarding a hardware device (by using root permissions) while in crosvm the same functionality is available through a file descriptor. Test: launch_cvd -vm_manager=qemu_cli, check adb and vnc Bug: 143713267 Change-Id: Ice9767b28d9011fba6389435c029bed2e80ba7b8
git clone https://github.com/google/android-cuttlefish cd android-cuttlefish debuild -i -us -uc -b sudo dpkg -i ../cuttlefish-common_*_amd64.deb sudo apt-get install -f
aosp-master
if you don't know what you're looking foraosp_cf_x86_phone
and click on userdebug
for the latest buildArtifacts
aosp_cf_x86_phone-img-xxxxxx.zip
-- it will always have img
in the name. Download this filecvd-host_package.tar.gz
. You should always download a host package from the same build as your images.mkdir cf cd cf tar xvf /path/to/cvd-host_package.tar.gz unzip /path/to/aosp_cf_x86_phone-img-xxxxxx.zip
Launch cuttlefish with:
$ HOME=$PWD ./bin/launch_cvd
Stop cuttlefish with:
$ HOME=$PWD ./bin/stop_cvd
You can use adb
to debug it, just like a physical device:
$ ./bin/adb -e shell
You can use the TightVNC JViewer. Once you have downloaded the TightVNC Java Viewer JAR in a ZIP archive, run it with
$ java -jar tightvnc-jviewer.jar -ScalingFactor=50 -Tunneling=no -host=localhost -port=6444
Click "Connect" and you should see a lock screen!