## Problem All children resume with parent's TSC value. Identical wall-clock across children opens timing attacks and breaks log correlation. ## Approach Firecracker exposes TSC config on snapshot/restore. Surface via `forkd-vmm::ForkOpts`. ## Acceptance - [ ] `ForkOpts { randomize_tsc: true }` produces children with distinct TSC offsets - [ ] Default = true
Problem
All children resume with parent's TSC value. Identical wall-clock across children opens timing attacks and breaks log correlation.
Approach
Firecracker exposes TSC config on snapshot/restore. Surface via
forkd-vmm::ForkOpts.Acceptance
ForkOpts { randomize_tsc: true }produces children with distinct TSC offsets