From 5b8475de7e07ec35ef1d50e8f0f7d3b49001d08b Mon Sep 17 00:00:00 2001 From: Anastassios Nanos Date: Wed, 18 Nov 2026 02:00:50 +0200 Subject: [PATCH] docs: Say what hvi 0.1.0-rc.3 changes for the gateway The component table said rc.3 is the first hvi whose Linux build takes --net-gateway. Every release takes it, rc.1 included: the KVM boot path connects the socket on both architectures. A gateway hvi cannot reach is a warning on every release, with a fallback to the built-in stub stack, so the guest boots with no egress. What rc.3 changes is one case: a connected socket that does not clone fails the boot (hvi-vmm 13324d9). The commit that moved the pin (4bb7c4e) states the wrong fact in its message; this is the correction. Signed-off-by: Anastassios Nanos --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 6bf54b3..9a408b8 100644 --- a/README.md +++ b/README.md @@ -319,7 +319,7 @@ urunc and hull, which have none for Linux: | brig, brigd, brig-broker | `brig-sh/brig` release | fetched, verified against its signed `checksums.txt` | | urunc, containerd-shim-urunc-v2 | built from `urunc-dev/urunc` at commit `5c6bc70` (branch `feat/linux-hvi-v050`) | CGO-static, built in a Go container | | hull | built from `brig-sh/hull` at commit `4bf76a6` (branch `main`), which publishes no Linux release | static (`CGO_ENABLED=0`), built in a Go container, with no telemetry endpoint | -| hvi | `brig-sh/hvi-vmm` release `v0.1.0-rc.3` (commit `bde7c58`), the first whose Linux build takes `--net-gateway`; hull pins its own hvi for macOS (`hvi.pin`) and does not check this one | fetched, musl-static; its `SHA256SUMS` cosign-verified against hvi-vmm's release workflow, the tarball pinned by sha256 | +| hvi | `brig-sh/hvi-vmm` release `v0.1.0-rc.3` (commit `bde7c58`); a gateway hvi cannot reach is a warning and a fallback to its stub stack on every release, and rc.3 makes a connected socket that does not clone fatal; hull pins its own hvi for macOS (`hvi.pin`) and does not check this one | fetched, musl-static; its `SHA256SUMS` cosign-verified against hvi-vmm's release workflow, the tarball pinned by sha256 | | guest kernel, container-initrd | `ghcr.io/nofireai/hull-assets` `0.1.12` | fetched by digest once its cosign signature checks out; the initrd is urunit. urunc's `packaging/container-initrd/urunit.pin` names `48a61bd`; hull-assets `0.1.12` does not record its urunit, so the bundle records that commit as `urunit_expected`. The build refuses a hull-assets bundle built from another urunc | | monitors, virtiofsd | `urunc-dev/monitors-build` | fetched, pinned by sha256 | | containerd, runc, nerdctl, CNI | upstream releases | fetched, upstream checksums |