Skip to content

docs: reconcile DGX Station GB300 express setup with deferred support status #6951

New issue
New issue
Closed
Documentation
#7327
Closed
docs: reconcile DGX Station GB300 express setup with deferred support status#6951
Documentation
#7327
Assignees
miyoungc
Labels
area: docsDocumentation, examples, guides, or docs buildplatform: dgx-stationAffects DGX Station hardware or workflows

Description

@miyoungc
miyoungc
opened on Jul 15, 2026

Description

The v0.0.83 release history and current quickstart say that DGX Station GB300 systems enter or offer the express-install path, while the platform and managed-vLLM references still classify DGX Station as deferred pending end-to-end validation on physical hardware.

These statements can both be technically true, but the current wording does not distinguish path availability from product support clearly enough:

  • docs/changelog/2026-07-14.mdx says DGX Station GB300 systems enter the express-install path.
  • docs/get-started/quickstart.mdx presents DGX Station express install alongside DGX Spark and Windows WSL.
  • docs/inference/set-up-vllm.mdx, docs/inference/choose-inference-provider.mdx, and docs/reference/platform-support.mdx say DGX Station remains deferred until the managed-vLLM onboarding path is validated end to end on physical hardware.
  • PR fix(install): restore DGX Station GB300 express setup #6875 restored OEM firmware detection for product names containing Station and GB300; its regression tests prove classification and installer routing, not a complete physical-hardware validation run.

Maintainers need to decide whether DGX Station GB300 remains an available-but-deferred path or whether sufficient validation evidence exists to change its supported status.

Affected Page

docs/changelog/2026-07-14.mdx, docs/get-started/quickstart.mdx, docs/inference/set-up-vllm.mdx, docs/inference/choose-inference-provider.mdx, and docs/reference/platform-support.mdx.

Issue Type

Inaccurate information.

Suggested Fix

Choose one product-status contract and apply it consistently:

  1. If DGX Station remains deferred, qualify the changelog and quickstart so they say the installer detects Station GB300 hardware and offers the path, but end-to-end physical validation and support remain deferred.
  2. If validation is complete, record the accepted hardware evidence and ownership decision, then update the platform-support status and managed-vLLM caveats together.

Keep the distinction explicit between installer path availability, tested behavior, and supported platform status.

Activity

  1. miyoungc
    added
    needs: triageAwaiting maintainer classification
    on Jul 15, 2026

  2. senthilr-nv commented on Jul 16, 2026

    @senthilr-nv
    senthilr-nv
    on Jul 16, 2026
    Collaborator

    Accepted implementation boundary for #6991:

    • DGX Station GB300 remains an available-but-Deferred path; this decision does not promote the platform support status.
    • This PR may automate host preparation only for the qualified Ubuntu 24.04 ARM64 generic-Ubuntu stack with the reviewed NVIDIA driver, Docker, Buildx, and NVIDIA Container Toolkit pins, including the explicitly approved factory DKMS transition.
    • DGX OS / BaseOS Galaxy and other Station variants remain outside this PR until separately audited and validated.
    • Nonqualified platforms and mismatched prerequisite states must fail before host mutation with precise remediation.
    • The Docker-group root-equivalent grant remains limited to the disclosed trusted single-user development-machine flow; shared or managed hosts require an organization-approved access path.
    • NemoClaw installer maintainers own the package-pin and compatibility lifecycle.
    • Promotion requires physical clean-host validation covering package preparation, reboot/resume bound to one installer revision, post-reboot verification, idempotent rerun, managed vLLM, onboarding, inference, and a useful agent task.

    This records the conservative product boundary supported by the current evidence; broader Station image support requires a follow-up decision and qualification.

  3. ericksoa
    added a commit that references this issue on Jul 16, 2026

    feat(installer): prepare DGX Station host prerequisites (#6991)

    50d5e83
  4. wscurran
    added
    area: docsDocumentation, examples, guides, or docs build
    platform: dgx-stationAffects DGX Station hardware or workflows
    and removed
    needs: triageAwaiting maintainer classification
    on Jul 17, 2026
  5. wscurran
    added the
    Documentation
    issue type on Jul 17, 2026
  6. wscurran
    assigned
    miyoungc
    on Jul 17, 2026

  7. miyoungc commented on Jul 21, 2026

    @miyoungc
    miyoungc
    on Jul 21, 2026
    CollaboratorAuthor

    Updated maintainer scope decision for #6951:

    • Accept the single-Station validation recorded in PR fix(installer): enable stock DGX OS on Station GB300 #7108 as evidence for Tested with limitations on one physical DGX Station GB300 running stock DGX OS 7.5.0.
    • This decision supersedes the earlier available-but-Deferred status and promotion gate for that narrow single-Station configuration.
    • Dual-Station configurations remain unvalidated.
    • Dedicated CI coverage is not available, so documentation must state both limitations.
    • This decision does not extend validation to other Station generations, generic Ubuntu preparation, unqualified images, or shared and managed-host access models.

    Validation evidence: #7108 (comment)

  8. senthilr-nv commented on Jul 21, 2026

    @senthilr-nv
    senthilr-nv
    on Jul 21, 2026
    Collaborator

    @miyoungc Physical DGX Station GB300 validation now covers stock DGX OS 7.5, generic Ubuntu 24.04 ARM64, April 2026 BaseOS, and June 2026 NVIDIA AI Developer Tools. Clean-host E2E passed on generic Ubuntu and BaseOS; stock DGX OS and AI Developer Tools also completed physical Station Express validation. We recommend Tested with limitations for single-Station GB300, noting only that dual-Station and dedicated CI coverage remain pending.

  9. miyoungc commented on Jul 21, 2026

    @miyoungc
    miyoungc
    on Jul 21, 2026
    CollaboratorAuthor

    Updated maintainer decision for #6951, accepting the expanded physical-validation record in #6951 (comment):

    • Tested with limitations applies across these exact profiles on one physical DGX Station GB300: generic Ubuntu 24.04 ARM64, stock DGX OS 7.5.0, the April 2026 NVIDIA Colossus BaseOS profile, and the June 2026 NVIDIA AI Developer Tools profile.
    • Clean-host end-to-end validation passed on generic Ubuntu and Colossus BaseOS. Stock DGX OS and AI Developer Tools completed physical Station Express validation.
    • This decision supersedes the stock-DGX-OS-only scope in docs: reconcile DGX Station GB300 express setup with deferred support status #6951 (comment) for these exact profiles.
    • For the support status, the remaining validation limitations are dual-Station configurations and the absence of dedicated CI coverage.
    • This decision does not extend validation to other Station generations, unmatched image profiles, or shared and managed-host access models.
  10. apurvvkumaria
    closed this as completedin #7327on Jul 21, 2026
  11. apurvvkumaria
    added a commit that references this issue on Jul 21, 2026

    docs(platform): mark DGX Station tested with limitations (#7327)

    426af01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

area: docsDocumentation, examples, guides, or docs buildplatform: dgx-stationAffects DGX Station hardware or workflows

Type

Documentation

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions