ChromeOS Flex VM #2242

Name of the Script

ChromeOS Flex

Script Type

VM (Virtual Machine)

Does this script support arm64?

arm64 not supported

📋 Script Details

vm/chromeos-flex-vm.sh — creates a ChromeOS Flex VM from Google's official recovery image. Built on the new core (pve/vm-core.func).

Where the image comes from. Flex is not in recovery.json; that file lists Chromebooks. Flex uses the board name reven and lives in the old CloudReady index at dl.google.com/dl/edgedl/chromeos/recovery/cloudready_recovery.json, currently a single stable-channel entry (16733.48.0, Chrome 151.0.7922.141).

This is the first image script here that can actually verify its download. Google publishes zipfilesize, filesize and a sha1 in that index, so the zip is checked against the expected size, and the extracted image against both size and sha1. Everywhere else we rely on a size floor heuristic.

The zip is 1.3 GB and expands to 9.5 GB, with both present at once, so the script checks free space before starting rather than failing forty minutes into a download.

Two deliberate departures from the other VM scripts:

• SATA, not virtio-scsi, and e1000, not virtio-net. The reven build carries the generic PC driver set Google ships for old laptops. AHCI and e1000 are certainly covered; virtio may work and is worth testing, but it should not be the default someone has to debug on first boot.
• UEFI with pre-enrolled-keys=0. Flex will not boot with the Microsoft keys enrolled.

Defaults: 4 cores, 4 GB RAM, 32 GB disk.

What to test

• Whether virtio-scsi and virtio-net actually work — if they do, the conservative defaults can go
• Whether the installer completes and the VM boots from disk afterwards
• Behaviour on ZFS and Btrfs storage (the raw/qcow2 branch differs)
• That the space check triggers correctly on a small root filesystem

Known and expected: Google does not support Flex in a VM, and Flex has no Play Store or Android apps. Both are stated in the script output and in the catalog entry.