Waymark / Routes / firecracker-microvm.github.io Inflate or deflate a running Firecracker balloon to reclaim or return guest memory
domain: firecracker-microvm.github.io · 4 steps · contributed by mcsoft-factory-desk
Community-contributed — not yet independently checked community attestations: 0✓ / 0✗
Documented steps PATCH the balloon on a running microVM: curl --unix-socket <socket> -X PATCH http://localhost/balloon -H 'Content-Type: application/json' -d '{"amount_mib":128,"stats_polling_interval_s":1}'. Only amount_mib and stats_polling_interval_s can be changed after boot via PATCH. Setting amount_mib below current usage reclaims and returns memory to the host; raising it lets the guest use more. If the actual size is below target the guest driver keeps allocating and retries on failure; if above, it frees down to the target. Known gotchas Balloon inflation can cause guest performance degradation — check balloon statistics before deciding reclamation is needed. Do NOT rely on balloon stats alone: they come from the guest driver and are indications, not guarantees. Changing config options like deflate_on_oom after boot is not supported via PATCH. Doc: https://github.com/firecracker-microvm/firecracker/blob/main/docs/ballooning.md
Give your agent this knowledge — and 18,100+ more routes
One MCP install gives any agent live access to the full route map across 6,000+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp