Google Git
Sign in
chromium / chromiumos / platform / initramfs / 8cadb08062d991dac9d288f26cfc79d3d29de0d3
commit8cadb08062d991dac9d288f26cfc79d3d29de0d3[log] [tgz]
authorTomasz Jeznach <tjeznach@chromium.org>Thu Apr 08 05:03:16 2021
committerCommit Bot <commit-bot@chromium.org>Thu Apr 08 22:18:30 2021
treed52bc207399ed20621d0739501d7e22e9a11a973
parenteeade2fe30bc8de9d6b88cf13ecb1cf992b8196c [diff]
hypervisor: use crosvm-direct

Switch to crosvm-direct, a slim version of crosvm.
Remove unused serial console fail-over path.

BUG=b:173824333
TEST=build factory_install target.

Change-Id: I207d99307d0f09f1c2aef23bf39ee066d8371d20
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/initramfs/+/2815604
Tested-by: Tomasz Jeznach <tjeznach@chromium.org>
Reviewed-by: Allen Webb <allenwebb@google.com>
Commit-Queue: Tomasz Jeznach <tjeznach@chromium.org>
2 files changed
tree: d52bc207399ed20621d0739501d7e22e9a11a973
  1. common/
  2. factory_netboot/
  3. factory_shim/
  4. hypervisor/
  5. minios/
  6. recovery/
  7. test/
  8. .gitignore
  9. LICENSE
  10. Makefile
  11. OWNERS
  12. README.md
README.md

Chromium OS initramfs

Build logic for creating standalone initramfs environments.

See the README files in the respective subdirs for more details.

To Use

Normally you wouldn't build in this directory directly. Instead, you would build the chromeos-initramfs package with the right USE flags. e.g.:

$ USE=recovery_ramfs emerge-$BOARD chromeos-initramfs

That will install the cpio initramfs files into the sysroot for you to build into a kernel directly. The various build scripts would then be used to make the right kernel/image using those (e.g. mod_image_for_recovery.sh).

To Make

You could build these by hand for quick testing. Inside the chroot:

$ make SYSROOT=/build/$BOARD BOARD=$BOARD <target>

That will create the cpio archives for you.

To Debug

It is possible to debug few of the initramfs targets in QEMU. Read test/README.md for more information.

Also, here is a shortcut for developing/debugging graphical bits in initramfs, without having to create a full image for every iteration.

After emerge-$BOARD, find your initramfs package from chroot /build/$BOARD/var/lib/initramfs and copy to a running DUT, for example /tmp/recovery_ramfs.cpio.xz, then do followings on DUT over SSH:

  1. mkdir /usr/local/test/; cd /usr/local/test
  2. xzcat /tmp/XXXXXX_ramfs.cpio.xz | toybox cpio -iv
  3. stop ui; kill $(pidof frecon)
  4. bind mount /dev, /proc, /sys and /tmp in /usr/local/test:
for d in dev proc sys tmp; do
   mount --bind /${d} /usr/local/test/${d}
done
  1. chroot /usr/local/test /init
  2. Iterate.