Skip to content

fix(vllm): pin L4T arm64 backend to vllm==0.24.0 for GB10 stability #10725

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
mudler merged 1 commit into from
Jul 7, 2026
+9 −1
Merged

fix(vllm): pin L4T arm64 backend to vllm==0.24.0 for GB10 stability #10725

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 9 additions & 1 deletion backend/python/vllm/requirements-l4t13-after.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,4 +1,12 @@
# vLLM 0.20+ ships an aarch64 manylinux wheel on PyPI whose Requires-Dist pins
# torch==2.11.0 / torchvision==0.26.0 / torchaudio==2.11.0, locking an ABI-
# consistent set with the cu130 torch wheel installed above.
vllm
#
# Pinned to match the cublas13 build (requirements-cublas13-after.txt) and to
# stay deterministic on GB10 / DGX Spark: 0.24.0 carries vllm-project/vllm#45179
# ("release cached device memory under pressure on UMA GPUs during weight
# loading"), without which cold model loads on the Grace Blackwell unified-
# memory architecture crash deterministically with an empty "Engine core init
# failed" set (mudler/LocalAI#10722). Leaving this unpinned let the L4T image
# drift onto whatever wheel was latest at build time.
vllm==0.24.0
Loading