Add VM metadata and naming
This commit is contained in:
parent
5b1de19cf5
commit
e4039ca7e9
3 changed files with 435 additions and 2 deletions
15
README.md
15
README.md
|
|
@ -27,6 +27,21 @@ ssh -i "./id_ed25519" root@<guest_ip>
|
|||
reboot
|
||||
```
|
||||
|
||||
## VM Info File
|
||||
Each VM writes a metadata file at `state/vm-*/info` with the following fields:
|
||||
- `vm_id`: unique identifier for the VM instance.
|
||||
- `pid`: Firecracker process ID.
|
||||
- `created_at`: timestamp when the VM was launched.
|
||||
- `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.
|
||||
- `log`: path to the Firecracker log file.
|
||||
- `base_loop`: loop device backing the base rootfs (if present).
|
||||
- `cow_file`: copy-on-write image file (if present).
|
||||
- `cow_loop`: loop device for the COW image (if present).
|
||||
- `dm_name`: device-mapper name for the merged rootfs (if present).
|
||||
- `dm_dev`: device-mapper device path for the merged rootfs (if present).
|
||||
|
||||
## Log Notes
|
||||
- `PCI: Fatal: No config space access function found` and `MissingAddressRange` lines are expected with `pci=off` in `run.sh`.
|
||||
- `SELinux: Could not open policy file ...` is expected in the minimal rootfs.
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue