Add rootfs/kernel overrides
This commit is contained in:
parent
f7e372d8db
commit
306412c995
3 changed files with 30 additions and 2 deletions
|
|
@ -24,6 +24,8 @@ Minimal Firecracker launcher.
|
|||
- `--name`: must be unique and match `[a-z0-9][a-z0-9_-]{0,63}`.
|
||||
- `--vcpu`: defaults to 2, max 16.
|
||||
- `--ram`: MiB, defaults to 1024, max 32768.
|
||||
- `--rootfs`: path to the base rootfs image (default: `./rootfs.ext4`).
|
||||
- `--kernel`: path to the kernel image (default: `./vmlinux`).
|
||||
- `--home-size`: M/G suffixes supported (default: 2G).
|
||||
|
||||
## Storage Layout
|
||||
|
|
@ -59,8 +61,11 @@ reboot
|
|||
## VM Info File
|
||||
Each VM writes a metadata file at `state/vms/<id>/info` with the following fields:
|
||||
- `id`: unique identifier for the VM instance.
|
||||
- `name`: VM name.
|
||||
- `pid`: Firecracker process ID.
|
||||
- `created_at`: timestamp when the VM was launched.
|
||||
- `rootfs`: root filesystem image path used to launch the VM.
|
||||
- `kernel`: kernel image path used to launch the VM.
|
||||
- `guest_ip`: IP address assigned to the guest.
|
||||
- `tap`: host TAP interface name attached to the bridge.
|
||||
- `api_sock`: path to the Firecracker API socket (stored under `$XDG_RUNTIME_DIR/banger/` when available).
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue