vLLM GPU access and drivers are painful
5 posts from 3 people4d activeFading, +0 this week
Posts per day
The posts behind it
[RFC]: Pluggable pipeline-parallel transport, and a path to out-of-process (elastic) PP stages
### Motivation. Pipeline parallelism in vLLM assumes a fixed group. All stages are ranks of one `torch.distributed` world, they start together, and `send`/`recv` between them never fail. Every stage also holds the KV of every request in flight. This fits a single node or a...
[Feature]: Support per-parameter meshes in NCCL M2N weight transfer
### 🚀 The feature, motivation and pitch NCCL M2N currently uses one source mesh and one destination mesh for the entire model update. Individual parameters may have different placements, but those placements must use the common meshes. This cannot directly represent models...
[Tracking Feature]: Support vLLM with Python 3.15
...module import in many places (first hit is `vllm/utils/deep_gemm.py`), so most of `vllm` fails to import. This also gates `torchvision` (0.29.1 has cp315 but needs torch 2.14) and `torchaudio` (cp315 only in nightly). * [ ] **Triton: kernel compilation fails on 3.15** with...
[Feature]: Support fused MoE weights with NCCL M2N weight transfer
### 🚀 The feature, motivation and pitch In current vLLM main, online weight updates use the regular model-loading path for fused MoE weights: This path is correct because the model loader understands expert ownership and the runtime-specific fused representation. However, every...
[Feature]: Support trainer-side pipeline parallelism with NCCL M2N weight transfer
### 🚀 The feature, motivation and pitch PR [[#51520] adds NCCL M2N weight transfer for resharing trainer weights directly into vLLM workers. The current M2N source contract requires every trainer rank to follow the same parameter manifest and participate in every parameter...
Companies and products named
About this problem
Evidence
5 posts from 3 people in 1 place, about 1 a week over 24 days. Mostly on vllm-project/vllm. Tools named alongside: GitHub, PyTorch, NVIDIA, PyPI.
Frustration Frustration 0 of 3· Seen on GitHub issues
How it was grouped
Posts that state a pain and match the "gpu-access" rule about vLLM. First post Oct 3, 2026, latest Oct 26, 2026. Corroborated: 3 or more posts from 2 or more people or places. Method
The same problem elsewhere
PyTorch GPU access and drivers are painful
17 posts from 17 people on GitHub issues, Reddit.
NVIDIA GPU access and drivers are painful
13 posts from 13 people on GitHub issues, Mastodon, Reddit.
GPU access, drivers and CUDA versions are painful
8 posts from 8 people on GitHub issues, Reddit.
DeepSeek GPU access and drivers are painful
7 posts from 6 people on GitHub issues.
Claude Code GPU access and drivers are painful
4 posts from 4 people on GitHub issues.
Ollama GPU access and drivers are painful
3 posts from 3 people on Hacker News, Reddit, GitHub issues.
OpenAI GPU access and drivers are painful
2 posts from 2 people on Reddit, GitHub issues. Unverified.
Chroma GPU access and drivers are painful
2 posts from 1 person on GitHub issues. Unverified.
Mistral GPU access and drivers are painful
2 posts from 2 people on GitHub issues. Unverified.
Other vLLM problems
vLLM users keep filing bugs
Top post: "Qwen3.8-flash-next 0% MTP acceptance rate in disaggregated PD serving", one of 37 posts from 34 people on GitHub issues, Reddit.
Running vLLM locally hits memory and speed limits
27 posts from 26 people on GitHub issues, Reddit.
vLLM upgrades break working setups
21 posts from 21 people on GitHub issues.
vLLM vulnerabilities are hard to triage and patch
9 posts from 9 people on Glyph Ibis.
vLLM runs out of context on real work
7 posts from 7 people on GitHub issues.
Trouble with vLLM cache
Top post: "AOT compile cache never loads for Qwen3.5 models: Kernel index 1 not found in id_to_kernel", one of 7 posts from 6 people on GitHub issues.
Fine-tuning vLLM is costly and unpredictable
7 posts from 7 people on GitHub issues.
vLLM fails to return valid structured output
5 posts from 5 people on GitHub issues.
Trouble with vLLM serve
Top post: "gpt-oss can't be served through `vllm serve` with any tool/reasoning-parser flags", one of 4 posts from 4 people on GitHub issues.
Trouble with vLLM performance
Top post: "Waiting requests re-walk their whole prefix-cache hit on every scheduling step", one of 3 posts from 3 people on GitHub issues, Reddit.
vLLM lock-in makes switching costly
3 posts from 3 people on GitHub issues.
RAG on vLLM returns irrelevant or missing context
3 posts from 3 people on GitHub issues.
History