You will use NVIDIA Sync to connect to a DGX Spark or Station, then download a vLLM container and a model for your device. Then, you will add a supplied launch script ...
Software 1.0 profile blocks MIG mutation and platform fixes Expected behavior: the Software 1.0 profile is capability-scoped to guidance, diagnostics, read-only MIG inspection, and explicitly ...
You will choose a recipe for your device, run its commands, and test the model's API and tool calling. Along the way, you will see how the recipe uses memory, batches requests, and selects the code ...
If you want to run a workload or a model that won't fit on a single DGX Spark, you can connect two or more Sparks into a cluster and distribute the workload or model across the devices. However, this ...
Build a local AI assistant in an OpenShell sandbox with vLLM inference and optional Telegram Use the matrix below to confirm your hardware platform, OS, memory, and multi-node workflow. The ...
Previously ran the NemoClaw playbook? NemoClaw installs openclaw-gateway.service as a systemd user service that binds port 18789. If it is still running, make setup fails with "Port 18789 is already ...
The playbook now pins the OpenFold3 1.6.0 multi-architecture image by digest. Its bundled manifest uses a generic OpenFold3 profile rather than a PCI-ID allowlist. On a DGX Station GB300 (31c2:10de), ...
You will use NVIDIA Sync to set up a two-Spark cluster, then use a supplied recipe to run one model across both devices. The recipe launcher starts a container on each Spark and runs vLLM across the ...
Cluster Assistant cannot finish its checks One or both Sparks or their ConnectX-7 link needs attention Return to Connect Multiple DGX Sparks and complete its checks before running the recipe. The API ...
Some results have been hidden because they may be inaccessible to you
Show inaccessible results