npx skills add ...
npx skills add nvidia/dgx-spark-playbooks --skill vllm-setup
Deploy a vLLM inference server on an NVIDIA DGX Station GB300 with validated container, GPU targeting, and tuning parameters. Use when the user asks to serve a model with vLLM, start a vLLM endpoint, or set up OpenAI-compatible inference on DGX Station.
npx skills add nvidia/dgx-spark-playbooks --skill vllm-setup
Deploy a vLLM inference server on DGX Station with validated configuration.
Find the GB300 GPU index. Run:
Identify the device index for the GB300 (typically device 1). Use this index for --gpus below. Do NOT use --gpus all — mixed coherency will cause CUDA failures.
Ask the user which model to serve. If they don't have a preference, suggest:
nvidia/Qwen3-235B-A22B-NVFP4 — large MoE model, fits in 279 GB HBMmeta-llama/Llama-3.1-70B-Instruct — solid general-purpose modelQwen/Qwen3-8B — small model for testingCheck if the user has an HF_TOKEN. Many models require HuggingFace authentication. The token must be passed inline with -e HF_TOKEN="..." — do not rely on shell export in background Docker tasks.
Deploy the container. Use this validated configuration:
Container version: Use nvcr.io/nvidia/vllm:26.01-py3. Do NOT use 25.10 — it has a FlashInfer buffer overflow on DGX Station.
Wait for the server to be ready. Monitor logs:
Wait for the line indicating the server is listening on port 8000.
Test the server:
Report the result to the user, including:
docker stop vllm-server && docker rm vllm-serverAdjust these based on the user's workload:
| Parameter | Default | Agent workloads | Throughput workloads |
|---|---|---|---|
--max-model-len | 32768 | 32768-65536 | 8192-16384 |
--gpu-memory-utilization | 0.9 | 0.85-0.90 | 0.90-0.92 |
--enable-prefix-caching | off | Enable (multi-turn reuse) | Enable |
--max-num-seqs | default | 4-16 (lower latency) | 32+ (higher throughput) |