Set access-kregistry to 2MiB. For pmem files not aligned to 2MiB, CrosVM currently sets up an alignment up to 2MiB using read-only pages. When the pmem file is being mapped for read-write access, this creates a problem, as KVM on ARM will regest a pmem region spanning multiple VMAs that uses a mixture of read-only and read-write mappings. Bump up the pmem file to 2MiB while the CrosVM issue gets fixed. Test: boot test on x86 and rockpi Bug: 148706939 Signed-off-by: Iliyan Malchev <malchev@google.com> Change-Id: Iaf750d0ca52b920f64db24cbda0ce33070c47e80 Merged-In: Iaf750d0ca52b920f64db24cbda0ce33070c47e80
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 buildArtifactsaosp_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!