You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit a84e095
Browse filesBrowse the repository at this point in the historyBrowse files
ateom-microvm: stage the rootfs upper inside the cold boot
The ROOTFS restore untarred the rootfs uppers before handing off to the
cold boot, which only later cleared stale sandbox state. A previous
activation's overlay mounts could therefore still sit on the upper dir
when the untar removed it, the ordering teardown documents as unsafe. The
untar also ran serially, so a large upper added its full extraction time
to the resume, where the MEMORY path overlaps the same work with bundle
preparation.
Make the cold boot own the upper dir. It clears sandbox state first, moved
ahead of bundle preparation, which touches only the atelet-owned bundle
dirs, then stages the upper in the background and joins it right before
the overlay mounts need it: pristine for a plain boot, re-materialized from
the snapshot's tars when the boot parameters name a snapshot dir. A retry
stages again from that dir, so nothing depends on what an earlier attempt
left behind, and the ROOTFS restore arm shrinks to naming the dir.
Spell the ladder out once: includesRootfs and includesMemory decide the
checkpoint's capture set and whether a restore resumes the guest, and
stageRootfsUpper is the one place a cold boot decides between a pristine
and a restored upper. Both have table tests, so a regression in what each
fidelity carries shows up without a KVM lane.
0 commit comments