commit | e46ae52441cb9235a2a17d0278f342a7dab62091 | [log] [tgz] |
---|---|---|
author | Cody Schuffelen <schuffelen@google.com> | Thu Dec 05 12:55:45 2019 -0800 |
committer | Cody Schuffelen <schuffelen@google.com> | Wed Dec 11 17:39:00 2019 -0800 |
tree | 57e9c922986b7f29aa3efbb42c9091287641d902 | |
parent | d3f27b966e209a2701b5be4799aa31ecd1577b46 [diff] |
Move the kernel argument generation to another file. While this doesn't include the kernel arguments produced by the VMM interface code, it does get a lot into one place. Moving this to another file helps shorten run_cvd.cc which is carrying a lot of other responsibilities, and establishes the API surface between the VMM executor and the kernel command line inputs through the kernel_args.h header file. Test: Build and run locally Bug: 145247175 Change-Id: I533ff9c1d306a4f223cea58e0dc26f08e87aafa5
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!