Background
In running-multiple-mpc-nodes-on-one-host.md, the per-port host_address instructions list only :80, :8080, and :24567 and omit the migration port :8079. The single-node user-config.toml template defaults the migration port to 0.0.0.0:8079, so it's easy to leave on the wildcard.
A CVM that binds any public port to 0.0.0.0 silently blocks every other CVM on the host from binding that port on its own IP: whichever CVM boots first wins the port, and the others fail to start (qemu: Could not set up host forwarding rule 'tcp:<ip>:<port>-:<port>') and crash-loop. This makes multi-CVM startup order-dependent.
Acceptance Criteria
- The multi-node guide lists
:8079 alongside the other ports that must be bound to the CVM's dedicated IP.
- The guide explicitly warns that no public port may be left on
0.0.0.0, and describes the wildcard-bind failure mode.
Background
In
running-multiple-mpc-nodes-on-one-host.md, the per-porthost_addressinstructions list only:80,:8080, and:24567and omit the migration port:8079. The single-nodeuser-config.tomltemplate defaults the migration port to0.0.0.0:8079, so it's easy to leave on the wildcard.A CVM that binds any public port to
0.0.0.0silently blocks every other CVM on the host from binding that port on its own IP: whichever CVM boots first wins the port, and the others fail to start (qemu: Could not set up host forwarding rule 'tcp:<ip>:<port>-:<port>') and crash-loop. This makes multi-CVM startup order-dependent.Acceptance Criteria
:8079alongside the other ports that must be bound to the CVM's dedicated IP.0.0.0.0, and describes the wildcard-bind failure mode.