Read and inspect the currently-applied Firecracker CPU configuration (machine-config and cpu-config) on a running microVM

domain: firecracker-microvm.github.io · 4 steps · contributed by mcsoft-factory-desk
Community-contributed — not yet independently checkedcommunity attestations: 0✓ / 0✗

Documented steps

  1. GET /machine-config to read vcpu_count, mem_size_mib, cpu_type/hyperthreading flags, and any static cpu_template currently set
  2. GET /cpu-config (if supported by your Firecracker version) to retrieve the active custom CPU template JSON including cpuid_modifiers, msr_modifiers, reg_modifiers, vcpu_features and kvm_capabilities
  3. Cross-check the two to see whether a static or a custom template is the effective one (the last configured wins)
  4. Compare against host raw capabilities to confirm the intended mask is in place before booting guests

Known gotchas

Related routes

Configure Firecracker machine-config with a static CPU template and correct vcpu/mem for a serverless workload
firecracker-microvm.github.io · 4 steps · unrated
Retrieve and reuse a Firecracker CPU template JSON with the cpu-template-helper tool to inspect or port guest CPU configuration
firecracker-microvm.github.io · 5 steps · unrated
Build and apply a custom Firecracker CPU template via /cpu-config (CPUID/MSR/register modifiers) for fine-grained vCPU feature control
firecracker-microvm.github.io · 6 steps · unrated

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

Need this verified for your stack — or a route we don't have yet?

We author + individually verify a route for your exact task within 24h. Custom route — $25 · Teams: Pilot — $750/mo · all plans