Repository navigation
ateom-microvm: snapshot durable-dir volumes as one tar per volume - #2283
Merged
Haven Xia (HavenXia) merged 1 commit intoOct 7, 2026
Merged
Haven Xia (HavenXia) merged 1 commit into
Haven Xia (HavenXia) merged 1 commit into
Conversation
Archive and restore each durable-dir volume in its own durable-dir-<volume>.tar file instead of a single durable-dir.tar covering the parent directory, matching ateom-gvisor. Because kata-agent bind-mounts /run/kata-containers/shared/containers/durable/<volume> by path inside the guest VM on cold boot (including DATA-scope restores), extracting a single tar into the parent directory allowed a snapshot entry to replace <volume> with a symlink that kata-agent would resolve in the guest root filesystem. Creating each volume directory first and extracting its archive inside it keeps the volume layout out of the snapshot's control.
Benjamin Elder (BenTheElder)
added
area/microVM
breaking-change
Haven Xia (HavenXia)
approved these changes
Oct 7, 2026
2 tasks done
This was referenced Oct 11, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Archive and restore each durable-dir volume in its own durable-dir-.tar file instead of a single durable-dir.tar covering the parent directory, matching ateom-gvisor.
Because kata-agent bind-mounts /run/kata-containers/shared/containers/durable/ by path inside the guest VM on cold boot (including DATA-scope restores), extracting a single tar into the parent directory allowed a snapshot entry to replace with a symlink that kata-agent would resolve in the guest root filesystem. Creating each volume directory first and extracting its archive inside it keeps the volume layout out of the snapshot's control.
Breaking change
See: #2110, applies the same change to microvm. Unlike gvisor this class was contained within the VM, but we'll do the same inside the VM for defense in depth.