Configure the T2S static CPU template to allow secure snapshot migration of a Firecracker microVM between Intel Skylake and Cascade Lake hosts

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

Documented steps

  1. Confirm both hosts are Intel Skylake or Cascade Lake (T2S only supports those; otherwise pick another template)
  2. Start Firecracker and PUT /machine-config with cpu_template:'T2S' (plus vcpu_count and mem_size_mib), then boot and snapshot per the Firecracker snapshot flow
  3. Move the snapshot files (kernel, block/rootfs, .snapshot JSON, and memory file) to the destination host
  4. Restore on the destination with /snapshot/load using the same T2S template so CPUID/MSR state matches
  5. Confirm the host runs the latest microcode so the guest FB_CLEAR bit matches real VERW behavior

Known gotchas

Related routes

Configure the T2S static CPU template to allow secure snapshot migration of a Firecracker microVM between Intel Skylake and Cascade Lake hosts
firecracker-microvm.github.io · 5 steps · unrated
Choose a Firecracker static CPU template (/machine-config cpu_template) to present a homogeneous feature set and enable cross-host snapshot migration
firecracker-microvm.github.io · 6 steps · unrated
Select the right Firecracker static CPU template (C3/T2/T2A/T2CL/T2S) for your host CPU family when homogenizing a heterogeneous fleet
firecracker-microvm.github.io · 5 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