commit | fa048be7c98183b2412afc2c0c0db51431121a9b | [log] [tgz] |
---|---|---|
author | Paul Kirth <[email protected]> | Tue Jul 14 03:51:38 2020 +0000 |
committer | Paul Kirth <[email protected]> | Tue Aug 04 23:14:01 2020 +0000 |
tree | cf0a5878dc4da6f2abc9776a9f1dc57791a67d17 | |
parent | ff59754a3935da7783d05c170a692d44c253cb2b [diff] |
Simplify resource management for allocd Some resources, such as network or mobile interfaces have complex multistage configuration. Having classes which can acquire and release static resources will make managing these resource lifetimes much more straightforward. The abstract base class StaticResource, is the common interface that clients can use to acquire and release resources. The client can configure the derived static resource class, and then ask for the list of resources to be acquired. Should any of these operations fail, then unwinding the operations is still straightforward, and may be achievable in the destructor. Thus far only mobile and wireless interface classes have been implemented, but any new resource types can be supported with minimal effort. This commit does not use these classes yet, but ResourceManager is expected to use them heavily. Bug: 148823285 Test: make -j Change-Id: I8c02ed371810e10c72dfe5f4ab88dee5d964f09c
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!