Repository navigation
Closed
Copy link
Labels
area: networkingInitial title-keyword triage suggestionInitial title-keyword triage suggestionarea: openvmmInitial title-keyword triage suggestionInitial title-keyword triage suggestion
Description
Objective. The microVM's network enforces the egress and ingress policy that NVX passes to OpenVMM, under a contract that NVX's consumers can rely on, and the VM worker refuses a network identity that the guest's command line cannot express.
Children.
| Issue | Scope | Blocked by |
|---|---|---|
| #1250 | Enforce ICMP egress rules end to end, and make ICMP usable in the guest. A downstream consumer asks whether consomme relays ICMP and enforces its rules, and which guest configuration, such as ping_group_range, NVX intends. |
— |
| #1252 | Confirm that general ingress allow publishes listeners on every host interface, admitting only private-network peers, while host-loopback access stays independent; and decide whether to publish IPv6 loopback, and whether to refuse --network-ingress allow --host-loopback deny. |
— |
| #1372 | The VM worker accepts a decoded network prefix outside the CLI's 1 to 30, and a debug build panics on 0 or above 32 while it derives the netmask. | — |
Order. No child blocks another.
Notes.
- ICMP: enforce ICMP egress rules end to end and make ICMP usable in the guest (NVX 6b485c82 / OpenVMM c32c57d1, Windows WHP) #1250 and Ingress: confirm that general ingress allow binds all host interfaces while host-loopback access stays independent #1252 are a downstream consumer's questions, observed at NVX
6b485c82and OpenVMMc32c57d1on WHP. Each spans the consumer's own policy layer, nvx-rs's lowering, the guest, and OpenVMM's consomme, and says which layer it observed. Answer them first, then fix here what the answers need. - openvmm: a microVM network prefix of 0 or over 32 panics config validation #1372 and openvmm: an unaligned or reversed decoded snapshot RAM range panics microVM load #1373 (in OpenVMM/microVM umbrella: snapshot publication, the manifest, block identity, and restore claims #1180) both add checks to
validate_machine_config(openvmm/openvmm_defs/src/microvm.rs); land them one at a time. Only a launch message that OpenVMM's controller did not build reaches either. - microVM: keep guests from reaching loopback-TCP console listeners through host loopback #551 (in OpenVMM/microVM umbrella: consoles, the management RPC, activation delivery, and stable error codes #1179) keeps guests from reaching loopback-TCP console listeners through the host-loopback mapping, the egress side of the host-loopback access whose ingress side Ingress: confirm that general ingress allow binds all host interfaces while host-loopback access stays independent #1252 asks about.
Metadata
Metadata
Assignees
Labels
area: networkingInitial title-keyword triage suggestionInitial title-keyword triage suggestionarea: openvmmInitial title-keyword triage suggestionInitial title-keyword triage suggestion
Activity
openvmm: pin the processor state that snapshots lost