vllm-project / vllm-project/production-stack

bug: lmCacheConfig with Blackwell 6000 pro and CUDA 13

Open
#893 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
Python
Stars
2.6k
Forks
503
Avg merge
4d 17h
Merged PRs (30d)
8

Description

Describe the bug

Hi,

Could you please release a vLLM Docker image with CUDA 13? The current images still use CUDA 12.8, and for compatibility with the latest Blackwell GPU we need CUDA 13.

Thanks,
Morgan

To Reproduce

Deploy gpt-oss-120b under 2 blackwell 6000 pro with lmcache/vllm-openai:v0.4.2 and lmCacheConfig to true :

(EngineCore_DP0 pid=100) ERROR 03-24 14:38:36 [core.py:1102] RuntimeError: Worker failed with error 'CUDA error: no kernel image is available for execution on the device
(EngineCore_DP0 pid=100) ERROR 03-24 14:38:36 [core.py:1102] Search for `cudaErrorNoKernelImageForDevice' in https://docs.nvidia.com/cuda/cuda-runtime-api/group__CUDART__TYPES.html for more information.
(EngineCore_DP0 pid=100) ERROR 03-24 14:38:36 [core.py:1102] CUDA kernel errors might be asynchronously reported at some other API call, so the stacktrace below might be incorrect.
Expected behavior

No response

Additional context

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the deployment using lmcache/vllm-openai:v0.4.2 on two Blackwell 6000 Pro GPUs and inspect how the production Docker image selects its CUDA base. Use the reported failure at core.py:1102 as the reproduction signal. Done means a released CUDA 13 image runs gpt-oss-120b with lmCacheConfig enabled without the no-kernel-image error.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker, python
Domain
devops, infrastructure
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
43/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.