Repository navigation
Update the gVisor release to 20261102.0 - #3574
Merged
Dmitry Berkovich (dberkov) merged 1 commit intoNov 3, 2026
Merged
Dmitry Berkovich (dberkov) merged 1 commit into
Dmitry Berkovich (dberkov) merged 1 commit into
Conversation
Signed-off-by: Nayana Bidari <[email protected]>
nybidari
requested review from
Dmitry Berkovich (dberkov) and
Fabricio Voznika (fvoznika)
November 2, 2026 23:54
Zoe Zhao (zoez7)
left a comment
Collaborator
There was a problem hiding this comment.
This makes sense to me. It adds a new version to the gvisor sbx config and keeps existing versions restorable.
Zoe Zhao (zoez7)
approved these changes
Nov 3, 2026
Dmitry Berkovich (dberkov)
approved these changes
Nov 3, 2026
Fabricio Voznika (fvoznika)
approved these changes
Nov 3, 2026
Dmitry Berkovich (dberkov)
approved these changes
Nov 3, 2026
Eitan Yarmush (EItanya)
pushed a commit
to kagent-dev/substrate
that referenced
this pull request
Nov 3, 2026
gvisor-default gains v7, release 20261102.0, as its default version. v6 stays enabled, so actors with memory snapshots taken on v6 still restore with their memory. The new gVisor release includes some reliability fixes such as: - Systrap no longer crashes sandboxes at high density. It now recognizes host stalls, such as a cgroup freeze, and stops killing stub threads that only look stuck (google/gvisor@a5b7936e84dd). - Resumed actors no longer fire all their pending timers at once, because CLOCK_MONOTONIC stops counting checkpointed time. Clock reads are fast right after a restore (google/gvisor@25172e526f45). - Apps no longer freeze while a large memory region loads during a background restore, which lowers resume latency for big actors (google/gvisor@ffc048011e1b, google/gvisor@ae286a28ef26). - Checkpoint no longer stats every cached file. For actors with many files, such as node_modules, the pause drops from seconds to milliseconds (google/gvisor@8229bcb7a7b6). - Disk-backed overlay pages no longer count as memory after a restore, and long-lived sandboxes no longer grow memory for each file they touch (google/gvisor@aa767e4c43d0, google/gvisor@b24cc9724102). AI use: AI-assisted, I reviewed and tested it. - [x] Tests pass - [x] Docs updated Signed-off-by: Nayana Bidari <[email protected]> (cherry picked from commit fc931c4) Signed-off-by: Eitan Yarmush <[email protected]>
1 of 2 tasks
Dmitry Berkovich (dberkov)
pushed a commit
that referenced
this pull request
Nov 3, 2026
gvisor-default gains v7, release 20261102.0, as its default version. v6 stays enabled, so actors with memory snapshots taken on v6 still restore with their memory. The new gVisor release includes some reliability fixes such as: - Systrap no longer crashes sandboxes at high density. It now recognizes host stalls, such as a cgroup freeze, and stops killing stub threads that only look stuck (google/gvisor@a5b7936e84dd). - Resumed actors no longer fire all their pending timers at once, because CLOCK_MONOTONIC stops counting checkpointed time. Clock reads are fast right after a restore (google/gvisor@25172e526f45). - Apps no longer freeze while a large memory region loads during a background restore, which lowers resume latency for big actors (google/gvisor@ffc048011e1b, google/gvisor@ae286a28ef26). - Checkpoint no longer stats every cached file. For actors with many files, such as node_modules, the pause drops from seconds to milliseconds (google/gvisor@8229bcb7a7b6). - Disk-backed overlay pages no longer count as memory after a restore, and long-lived sandboxes no longer grow memory for each file they touch (google/gvisor@aa767e4c43d0, google/gvisor@b24cc9724102). AI use: AI-assisted, I reviewed and tested it. - [x] Tests pass - [x] Docs updated Signed-off-by: Nayana Bidari <[email protected]> (cherry picked from commit fc931c4) Signed-off-by: Eitan Yarmush <[email protected]>
2 tasks done
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.
gvisor-default gains v7, release 20261102.0, as its default version. v6 stays enabled, so actors with memory snapshots taken on v6 still restore with their memory.
The new gVisor release includes some reliability fixes such as:
AI use: AI-assisted, I reviewed and tested it.