tree: 6a417bfccf1665471e6a35902b36cdb852cade58 [path history] [tgz]
  1. data/
  2. kokoro/
  3. .gitignore
  4. build.py
  5. disk_config.tpl
  6. OWNERS
  7. README.md
  8. setup.sh
vm_tools/reference_vm/README.md

Reference VM

The Reference VM is a Debian-based VM image used for testing ChromeOS VM integrations.

Dependencies

Debian:

sudo apt install eatmydata fai-setup-storage lvm2 ovmf python3-jinja2 \
  python3-requests python3-yaml

For creating the UEFI variables image:

pip3 install --user virt-firmware

Build instructions

sudo ./build.py

sudo is required for loopback device use.

UEFI variables preparation

virt-fw-vars --input /usr/share/OVMF/OVMF_VARS_4M.fd \
  --output refvm_VARS.fd \
  --enroll-generate "reference VM PK/KEK" \
  --secure-boot \
  --add-mok "$(uuidgen -r)" ./data/var/lib/dkms/mok.pub

Secure Boot

The built image and firmware support UEFI Secure Boot. To load out-of-tree modules (currently virtio_wl and tpm_virtio), a signing key is included in the built image at /var/lib/dkms/mok.key. The variables image generated using the above command includes the public key in the MOK.

Booting in crosvm directly

A build of OVMF for crosvm (CROSVM_CODE.fd) is required. To run a basic VM with a serial console:

crosvm run --cpus 4 --mem 4096 --disable-sandbox --bios CROSVM_CODE.fd \
  --pflash refvm_VARS.fd --block path=/mnt/refvm.img \
  --serial type=stdout,console,stdin,earlycon

To enable networking, refer to the crosvm guide .

Booting on chromeOS

Place CROSVM_CODE.fd and refvm_VARS.fd in Downloads. Place refvm.img into /run/daemon-store/crosvm/<user ID>/cmVmdm0=.img.

vmc start refvm --bios /home/chronos/user/Downloads/CROSVM_CODE.fd \
  --pflash /home/chronos/user/Downloads/refvm_VARS.fd \
  --tools-dlc termina-dlc --no-start-lxd