Skip to content

Update the gVisor release to 20261102.0 - #3574

Merged
Dmitry Berkovich (dberkov) merged 1 commit into
agent-substrate:mainfrom
nybidari:gvisor-release-20261102
Nov 3, 2026
Merged

Dmitry Berkovich (dberkov) merged 1 commit into
agent-substrate:mainfrom
nybidari:gvisor-release-20261102

Conversation

@nybidari

@nybidari nybidari commented Nov 2, 2026 •

Copy link
Copy Markdown
Collaborator

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.

  • Tests pass
  • Docs updated

@zoez7 Zoe Zhao (zoez7) left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This makes sense to me. It adds a new version to the gvisor sbx config and keeps existing versions restorable.

@dberkov
Dmitry Berkovich (dberkov) added this pull request to the merge queue Nov 3, 2026
Merged via the queue into agent-substrate:main with commit fc931c4 Nov 3, 2026
7 checks passed
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]>
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]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants