Repository navigation
GPU Sandboxes in gVisor: What's Missing and What's Next #119
klueska
started this conversation in
Maintainer Summit NA 2026
Replies: 2 comments 4 replies
|
Hi @klueska, it seems that no gVisor maintainers are invited to the CNCF maintainer summit, but this session might benefit from having at least one gVisor maintainer at the table. Would it be possible to let either @milantracy or I (we are both in SLC this week) in? |
4 replies
|
This session has been selected and added to the schedule for 2:20 PM: https://events.linuxfoundation.org/kubecon-cloudnativecon-north-america/features-add-ons/maintainer-summit/?id=1318476#schedule Thank you for leading this discussion! |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Topic
GPU Sandboxes in gVisor: What's Missing and What's Next
What projects are involved?
gVisor
Description
Agents are starting to write and run their own CUDA code, and people want to sandbox it in environments where running a VM is not feasible. gVisor is a logical choice when virtualization isn't possible, but its GPU support lags behind. Each driver release has to be tracked by hand, only a few driver versions are qualified, MIG and multi-node NVLink aren't supported yet, and checkpoint/restore with a GPU doesn't work for every workload. This session is for comparing what issues people have run into when running workloads with GPUs on gVisor and working out what is worth fixing first. Anyone who maintains gVisor or runs sandboxes using it is welcome.
Questions to discuss
Session lead contact information
Kevin Klues - @klueska
All reactions