Repository navigation
docs(inference): show how hardware profiles identify the GPU - #14760
Merged
Merged
Conversation
Collaborator
Author
Authoring session — opening
|
cv
enabled auto-merge (squash)
November 21, 2026 22:53
Contributor
|
v1 documentation preview: https://nvidia-preview-nemoclaw-v1-pr-14760.docs.buildwithfern.com/nemoclaw |
Contributor
Selected hardware E2EsCommit: Selected cases run automatically; results do not gate merging. Shared code or test infrastructure changed.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Documents that managed-service hardware profiles identify the GPU by the name
nvidia-smireports, shows how to check that name before applying, and lists DGX Spark systems whose driver reports a placeholder name as a current limit.Problem
On a DGX Spark whose driver reports
NVIDIA JMJWOA-Generic-GPU, the GTC DC Hermes example plans, then apply fails after creating the gateway and model container:The docs described the requirement as an ARM64 GB10 without saying that the runtime identifies the GPU by its
nvidia-sminame, so a reader couldn't check a host before applying.Part of #14698: these docs say that such a host can't use the profile. Whether v1 should accept another GPU identity source remains open there.
Change
docs/agents-inference/models.md: how each profile matches the GPU name, the failure for a placeholder name, and thenvidia-smicommand to run before applying.examples/gtc-dc/README.md: the same check in the host preparation steps.docs/resources/limits.md: a row for DGX Spark systems that report a placeholder GPU name.The runtime's check is unchanged. Accepting the placeholder would trust a name that the driver emits for a GPU it doesn't identify; NemoClaw's main line also sees the same placeholder from the Windows-on-Arm WSL shim on non-NVIDIA hardware. Identifying GB10 by PCI device ID or firmware product name needs data from an affected host first, requested on #14698.
Beyond CI
NVIDIA GB10, 12.1, 580.178.04on the host, and the same name appeared inside a--gpus allcontainer.nvidia-smidecoder and thedgx-sparkcheck produced the documented error; the same line withNVIDIA GB10passed.