[NVIDIA] fix: H100+H200 CoreWeave fix#308
Merged
Merged
Conversation
Oseltamivir
pushed a commit
that referenced
this pull request
Dec 9, 2025
* add shm path mount * add fix to h200 cw * change path * change path back
cquil11
changed the title
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
1 participant
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.
After upgrade to vLLM 0.11.2, it appears the container tries to access
/dev/shm/sagemaker_sessions(inside the container). For some reason, on CoreWeave cluster (H100 + H200), the same fs is being mounted each time, so between subsequent runs there are permission errors. Therefore, the workaround/solution is to just mountdev/shm/sagemaker_sessionsto a temp directory on/mnt/vast.