Add AMD GPU support for Nemotron-3-Nano-30B-A3B#207
Add AMD GPU support for Nemotron-3-Nano-30B-A3B#207GoldenGrapeGentleman wants to merge 1 commit intovllm-project:mainfrom
Conversation
GoldenGrapeGentleman
commented
Jan 27, 2026
- Add AMD MI300X/MI325X/MI355X support section
- Tested on ROCm 7.0.2 with rocm/vllm-dev:nightly
- Requires VLLM_ROCM_USE_AITER=0 for compatibility
- Document known limitations
Tested and verified on AMD MI300X: - Docker image: rocm/vllm-dev:nightly - AITER disabled for compatibility - Benchmark passed: 4/4 requests successful (1024/1024 input/output) Co-authored-by: billishyahao <bill.he@amd.com> Signed-off-by: Yuan Yue <yueyuan@amd.com>
Summary of ChangesHello @GoldenGrapeGentleman, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This pull request significantly enhances the accessibility of the Nemotron-3-Nano-30B-A3B models by introducing detailed documentation for AMD MI300X GPU support. It provides users with a clear, step-by-step guide to set up their environment, configure the vLLM server, and run benchmarks, thereby broadening the hardware platforms capable of utilizing these models. Highlights
🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console. Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here. You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension. Footnotes
|
There was a problem hiding this comment.
Code Review
This pull request adds valuable documentation for running Nemotron-3-Nano-30B-A3B on AMD GPUs. The instructions are clear and easy to follow. I've added a few suggestions to improve the documentation's completeness and readability. Specifically, I've recommended listing all supported AMD GPUs, improving the formatting of a long command, clarifying support for the FP8 model variant, and adding the 'Known Limitations' section mentioned in the pull request description. These changes will help ensure users have all the necessary information to run the model successfully on AMD hardware.
| --num-prompts 4 \ | ||
| --ignore-eos \ | ||
| --trust-remote-code | ||
| ``` |
There was a problem hiding this comment.
The pull request description mentions 'Document known limitations', but this section is missing. It's important to include this for users. For example, the PR description states Requires VLLM_ROCM_USE_AITER=0 for compatibility, and while this is set in the server launch command, there is no explanation for why it's needed. Please add a 'Known Limitations' section to explain this and any other caveats for running on AMD hardware.
|
|
||
| ### AMD GPU Support | ||
|
|
||
| Please follow the steps here to install and run Nemotron-3-Nano-30B-A3B models on AMD MI300X GPU. |
There was a problem hiding this comment.
The PR description mentions support for MI300X/MI325X/MI355X, but the documentation only lists MI300X. To provide complete information to users, please list all supported AMD GPU models.
| Please follow the steps here to install and run Nemotron-3-Nano-30B-A3B models on AMD MI300X GPU. | |
| Please follow the steps here to install and run Nemotron-3-Nano-30B-A3B models on AMD MI300X/MI325X/MI355X GPUs. |
| ``` | ||
| Launch the ROCm vLLM docker: | ||
| ```shell | ||
| docker run -it --ipc=host --network=host --privileged --cap-add=CAP_SYS_ADMIN --device=/dev/kfd --device=/dev/dri --device=/dev/mem --group-add video --cap-add=SYS_PTRACE --security-opt seccomp=unconfined -v $(pwd):/work -e SHELL=/bin/bash --name Nemotron-Nano rocm/vllm-dev:nightly |
There was a problem hiding this comment.
This docker run command is very long and horizontally scrolls, which harms readability. Consider breaking it into multiple lines using backslashes (\) for better clarity and ease of use.
| docker run -it --ipc=host --network=host --privileged --cap-add=CAP_SYS_ADMIN --device=/dev/kfd --device=/dev/dri --device=/dev/mem --group-add video --cap-add=SYS_PTRACE --security-opt seccomp=unconfined -v $(pwd):/work -e SHELL=/bin/bash --name Nemotron-Nano rocm/vllm-dev:nightly | |
| docker run -it \ | |
| --ipc=host \ | |
| --network=host \ | |
| --privileged \ | |
| --cap-add=CAP_SYS_ADMIN \ | |
| --device=/dev/kfd \ | |
| --device=/dev/dri \ | |
| --device=/dev/mem \ | |
| --group-add video \ | |
| --cap-add=SYS_PTRACE \ | |
| --security-opt seccomp=unconfined \ | |
| -v $(pwd):/work \ | |
| -e SHELL=/bin/bash \ | |
| --name Nemotron-Nano \ | |
| rocm/vllm-dev:nightly |
| SAFETENSORS_FAST_GPU=1 \ | ||
| VLLM_USE_TRITON_FLASH_ATTN=0 \ | ||
| VLLM_ROCM_USE_AITER=0 \ | ||
| vllm serve nvidia/NVIDIA-Nemotron-3-Nano-30B-A3B-BF16 \ | ||
| --tensor-parallel-size 1 \ | ||
| --max-model-len 32768 \ | ||
| --max-num-seqs 256 \ | ||
| --trust-remote-code \ | ||
| --disable-log-requests |
There was a problem hiding this comment.
The documentation for AMD GPU support only provides instructions for the BF16 model variant. The model also has an FP8 variant. Please clarify if FP8 is supported on AMD GPUs. If it is, please provide instructions for running it. If not, it would be helpful to state this explicitly as a known limitation. The NVIDIA section provides a good example of how to handle different data types using a DTYPE environment variable.