Gitiles
Code Review Sign In
gerrit-public.fairphone.software / device / google / cuttlefish / 4e9e6d84d259f1f63879c1364c235090576e02c7
commit4e9e6d84d259f1f63879c1364c235090576e02c7[log] [tgz]
authorAlistair Delva <adelva@google.com>Fri Jul 17 16:17:38 2020 -0700
committerAlistair Delva <adelva@google.com>Wed Jul 22 20:27:47 2020 -0700
tree9885a7108c2f1c6c6d6972f1c5e9056428250928
parent116551307532d759b937d4d268251ec5e6949080 [diff]
Add ramoops pstore support to QEMU

Implement ramoops pstore using a fake 2MB NVDIMM. QEMU will assign the
NVDIMM to 0x100000000, next to any other pmem region. Currently, the x86
GKI kernel doesn't support NVDIMM detection via CONFIG_ACPI_NFIT, which
is actually a good thing because then the LIBNVDIMM driver would claim
the region, which we don't want (we want to be able to claim with the
legacy "ramoops pstore" driver).

In the longer term, we should add a pmem backend to the pstore driver,
then we can simply use virtio_pmem, which will also enable arm64
support.

Bug: 159242186
Change-Id: Ic434c62f458a7b0ddb47a985d23f4fa76e461734
Signed-off-by: Alistair Delva <adelva@google.com>
2 files changed
tree: 9885a7108c2f1c6c6d6972f1c5e9056428250928
  1. common/
  2. guest/
  3. host/
  4. recovery/
  5. shared/
  6. tests/
  7. tools/
  8. vsoc_arm64/
  9. vsoc_arm64_only/
  10. vsoc_x86/
  11. vsoc_x86_64/
  12. vsoc_x86_64_only/
  13. vsoc_x86_noapex/
  14. Android.bp
  15. Android.mk
  16. AndroidProducts.mk
  17. CleanSpec.mk
  18. dtb.img
  19. fetcher.mk
  20. host_package.mk
  21. METADATA
  22. OWNERS
  23. README.md
  24. required_images
  25. 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!