commit | 971842d8b547f34b1b35737c2d547f28fa456aec | [log] [tgz] |
---|---|---|
author | Cody Schuffelen <[email protected]> | Tue Dec 10 16:33:11 2019 -0800 |
committer | Cody Schuffelen <[email protected]> | Fri Dec 20 16:19:27 2019 -0800 |
tree | d6013aa91b60ae5c3d8e1cd6be6e0fc77e6b150f | |
parent | fb87708c6026e57e566fe7811fd0fc5770c73a97 [diff] |
Check that TAP devices aren't in use. This is just a sanity check at the moment to avoid multiple VMMs using the same TAP device. Looking at the list of tap devices in use will in the future help with selecting available instance numbers / indexes to run a device in. Prior to this change, if the TAP device was already being used, run_cvd would run without that tap device and print "Unable to connect to ..tap interface: Device or resource busy". This makes run_cvd fail outright if the tap device is already being used by another process. Test: Build and run when TAP device is in use (through vde_plug2tap) Change-Id: If233470bbae6fdbcb2956f618f350ca2dec7f4ff
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!