dcgmi set#

NAME#

dcgmi-set - change DCGM host-engine settings and driver attachment

SYNOPSIS#

dcgmi set --logging-severity <level> [--target-logger <logger>]
          [--json] [--host <address>]
dcgmi set --attach-driver [--host <address>]
dcgmi set --detach-driver [--host <address>]

DESCRIPTION#

dcgmi set changes a running host engine. It can change logger severity or ask DCGM to attach to and detach from the NVIDIA driver.

Driver attach and detach affect every GPU managed by that host engine. Detach stops diagnostics and removes watched data and group membership associated with detached GPUs. Coordinate these operations with other host users.

OPTIONS#

--logging-severity <level>: Set the selected logger to NONE, FATAL, ERROR, WARN, INFO, DEBUG, or VERB.
--target-logger <logger>: Select BASE or SYSLOG for --logging-severity. BASE, the default, handles most host-engine messages.
--attach-driver: Attach the NVIDIA driver to the host engine and discover currently available GPUs.
--detach-driver: Detach the NVIDIA driver from the host engine. Do not combine with --attach-driver.
-j, --json: Accepted with the logging operation for compatibility. The DCGM 4.6 setting call does not emit a structured result document.
--host <address>: Connect to the specified host engine.
-h, --help: Print generated usage information and exit.

SETTING SCOPE AND LIFETIME#

Each invocation should select exactly one of logging, attach, or detach. In DCGM 4.6 a logging request is processed first if it is combined with a driver flag, leaving the driver flag ignored; do not combine operation forms. Successful DCGM 4.6 setting calls are silent, so use the exit status to confirm completion.

Effects of settings operations#
Operation	Scope and lifetime
Logging severity	Changes one logger in the running host engine. It affects other clients’ subsequent host-engine log messages and returns to launch-time settings when that process restarts.
Detach driver	Globally detaches NVML from the host engine, stops running diagnostics, marks all GPUs detached, removes their cached values and watches, and removes detached GPUs and associated MIG entities from groups. Applied DCGM configuration is reset.
Attach driver	Globally reattaches NVML and discovers available GPUs. It does not reconstruct removed user-group membership or reapply the DCGM configuration that detach reset.

Attach and detach affect every user of the selected host engine and can require administrative privileges. Confirm the resulting inventory with dcgmi discovery --list --all and rebuild any user groups, configuration, or watches that the workflow requires. The complete per-feature behavior is in Detached GPUs.

EXAMPLES#

Set the base logger to informational severity:

$ dcgmi set --logging-severity INFO --target-logger BASE

Detach and later reattach the driver:

$ dcgmi set --detach-driver

$ dcgmi set --attach-driver