Skip to content

docs: Say what hvi 0.1.0-rc.3 changes for the gateway - #42

Merged
ananos merged 1 commit into
mainfrom
chore/hvi-rc3-readme
Nov 19, 2026
Merged

ananos merged 1 commit into
mainfrom
chore/hvi-rc3-readme

Conversation

@ananos

@ananos ananos commented Nov 18, 2026 •

Copy link
Copy Markdown
Contributor

Summary

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 (src/arch/{x86_64,aarch64}/kvm.rs at rc.1 and rc.2). A gateway hvi cannot reach is a warning on every release, with a fallback to the built-in stub stack (src/devices/virtio/net.rs, unreachable_gateway_falls_back_to_the_stub), 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 corrects the one place that is still editable. Spotted by papazof on brig-sh/hull#171, in two rounds.

Changes

  • README.md: the hvi row of the component table.

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 <ananos@nofire.ai>
@ananos
ananos force-pushed the chore/hvi-rc3-readme branch from 51a63bb to 5b8475d Compare November 18, 2026 04:54
@ananos
ananos marked this pull request as ready for review November 18, 2026 16:31
@ananos
ananos merged commit 02c11a6 into main Nov 19, 2026
5 checks passed
@ananos
ananos deleted the chore/hvi-rc3-readme branch November 19, 2026 12:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants