Module replay 

--config-file static-config replay path.

Per 20-firecracker-api.md § 6: a static-config file is parsed, validated, and replayed through the same RuntimeApiController::dispatch path as the HTTP server. There is no parallel codepath; the same validation, the same errors, the same logging.

The replay order is deterministic: machine-config → cpu-config → boot-source → drives → NICs → vsock → mmds-config → mmds → balloon → entropy → serial → pmem → hotplug-memory → logger → metrics → Action(InstanceStart) (only when start_microvm = true).

Enums

ReplayError

Errors produced while replaying a static configuration file.

Functions

parse_config_file

Read and parse a static-config file. The file is read fully into memory; the API body limit does not apply (the file is local and trusted to the operator).

replay_config

Replay a parsed ConfigFile through the controller. If start_microvm is true, a final Action(InstanceStart) is dispatched after all configuration actions succeed (matches the spec’s --no-api semantics).