What Are ZFS Boot Environments in ZFSBootMenu?

A ZFS boot environment (BE) is a bootable ZFS filesystem or snapshot that ZFSBootMenu presents as a menu entry at boot time. In ZFSBootMenu, boot environments can represent different versions of a Linux distribution, earlier snapshots of a common root, or entirely different distributions. ZFSBootMenu discovers these environments across imported pools, lets you pick one (or manipulate its snapshots) before booting, and then launches the selected kernel and initramfs with kexec.

How ZFSBootMenu Treats Boot Environments

ZFSBootMenu is a small, self-contained Linux system that knows how to find other Linux kernels and initramfs images inside ZFS filesystems. It does not chainload a fixed boot sector; instead it searches ZFS datasets for bootable content and builds a menu from what it finds.

The documented boot flow is:

1. Boot a ZFSBootMenu image via direct EFI booting, an EFI boot manager such as rEFInd, a BIOS bootloader such as syslinux, or another method. The image can be a self-contained UEFI application or a dedicated Linux kernel and initramfs.
2. Find all healthy ZFS pools and import them — or, at the user's option, find and import only a specific pool.
3. If appropriate, select a preferred boot environment:
   • If the ZFSBootMenu command line specifies a pool preference and that pool has been imported, prefer the filesystem indicated by its bootfs property (if defined).
   • If no pool preference is specified or the preferred pool is not found, prefer the filesystem indicated by the bootfs property (if defined) on the first-found pool.
4. If a suitable bootfs is identified, start an interruptable countdown (10 seconds by default) to automatically boot that environment.
5. If no bootfs value can be identified or the countdown is interrupted, search for boot environments and present them for selection.

The key mechanism is the bootfs pool property: it names the default boot environment for a pool, which is what the automatic countdown uses. Everything else in the menu comes from discovery of kernels and initramfs images within ZFS filesystems.

What Counts as a Boot Environment

Because a BE is just a ZFS filesystem or snapshot containing a kernel and initramfs, the same pool can hold several kinds of entries:

This is why the documentation describes choosing among "multiple boot environments" as the core function: the menu is not limited to one installed OS.

Why This Matters in Practice

• Rollback without a rescue disk. If an upgrade breaks the system, an earlier root snapshot is already a menu entry; you select it at boot rather than repairing from external media.
• Side-by-side testing. A second distribution or a pre-upgrade snapshot can coexist with the primary root, and the bootfs property decides which one boots by default.
• Pre-boot manipulation. ZFSBootMenu allows snapshots to be manipulated in the pre-boot environment, so you can adjust environments before launching a kernel.
• Bootstrap via zfs recv. For the adventurous user, ZFSBootMenu can even bootstrap a system installation by receiving a dataset with zfs recv.

For example, a user who runs a rolling-release distribution might keep a snapshot from before each major upgrade. After a bad upgrade, they interrupt the 10-second countdown, pick the pre-upgrade snapshot from the menu, and boot into the previous state — no separate recovery environment required.

Where to Go Next

The documentation at docs.zfsbootmenu.org covers the surrounding pieces: distribution-agnostic design, local installation and building in a container, command-line arguments, run-time configuration, signature verification, and prebuilt EFI executables (an x86_64 EFI image and an x86_64 recovery image). If your question is specifically about boot environments, the bootfs property and the snapshot-selection behavior described above are the parts to focus on.