Gitiles
Code Review Sign In
gerrit-public.fairphone.software / device / google / cuttlefish / fc226195f27ad3b4ae2004b364dc6f0607701a21
commitfc226195f27ad3b4ae2004b364dc6f0607701a21[log] [tgz]
authorIliyan Malchev <malchev@google.com>Mon Apr 20 09:51:35 2020 -0700
committerEnrico Granata <egranata@google.com>Tue May 12 15:37:07 2020 +0000
tree3cd990ea574a431c6bba4d7f241e3a9361a186e1
parentc75f71066543b7fa04bbf87e90a414ccb3b0129d [diff]
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
1 file changed
tree: 3cd990ea574a431c6bba4d7f241e3a9361a186e1
  1. common/
  2. guest/
  3. host/
  4. shared/
  5. tests/
  6. tools/
  7. vsoc_arm64/
  8. vsoc_x86/
  9. vsoc_x86_64/
  10. vsoc_x86_noapex/
  11. Android.bp
  12. Android.mk
  13. AndroidProducts.mk
  14. CleanSpec.mk
  15. default-permissions.xml
  16. dtb.img
  17. fetcher.mk
  18. host_package.mk
  19. OWNERS
  20. README.md
  21. TEST_MAPPING
README.md

So you want to try cuttlefish?

  1. Download, build, and install the host debian package:
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
  1. Go to http://ci.android.com/
  2. Enter a branch name. Start with aosp-master if you don't know what you're looking for
  3. Navigate to aosp_cf_x86_phone and click on userdebug for the latest build
  4. Click on Artifacts
  5. Scroll down to the OTA images. These packages look like aosp_cf_x86_phone-img-xxxxxx.zip -- it will always have img in the name. Download this file
  6. Scroll down to cvd-host_package.tar.gz. You should always download a host package from the same build as your images.
  7. On your local system, combine the packages:
mkdir cf
cd cf
tar xvf /path/to/cvd-host_package.tar.gz
unzip /path/to/aosp_cf_x86_phone-img-xxxxxx.zip

  1. Launch cuttlefish with:

    $ HOME=$PWD ./bin/launch_cvd

  2. Stop cuttlefish with:

    $ HOME=$PWD ./bin/stop_cvd

So you want to debug cuttlefish?

You can use adb to debug it, just like a physical device:

$ ./bin/adb -e shell

So you want to see cuttlefish?

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!