vGPU#
The vGPU module is module ID 2. On a supported NVIDIA vGPU host, it exposes inventory and telemetry for the physical GPUs that can host vGPUs, the vGPU types available on those GPUs, and active vGPU instances.
When vGPU monitoring is useful#
This module is intended for host-side visibility in a virtualized GPU environment. It is useful when an administrator needs to correlate a virtual machine with its vGPU, confirm the guest driver or license state, measure the framebuffer assigned to an instance, or investigate encoder and framebuffer- capture activity.
DCGM complements the virtualization platform in this workflow:
The hypervisor or vGPU management stack creates and assigns a vGPU.
That management inventory supplies the active vGPU instance ID and its owning VM.
DCGM watches the physical GPU and vGPU-instance fields while the VM runs.
An operator correlates DCGM telemetry with the VM, guest, and physical GPU when investigating capacity, licensing, or performance.
DCGM does not create VMs, provision vGPU instances, or replace the vGPU management interfaces. The information is available on the host; a DCGM instance inside a guest sees the GPU interface presented to that guest rather than the host’s complete vGPU inventory.
Entities and fields#
An active vGPU instance is a DCGM_FE_VGPU entity and uses the command-line
selector vgpu:<id>. Useful instance fields include:
Field ID |
Field name |
What it answers |
|---|---|---|
520 |
|
Which VM identifier owns the vGPU? |
521 |
|
What VM name is reported by the virtualization stack? |
522 |
|
Which vGPU type ID is assigned? |
523 |
|
What UUID identifies the vGPU instance? |
524 |
|
Which guest vGPU driver version is reported? |
525 |
|
How much framebuffer is the instance using? |
526 |
|
Is the instance licensed ( |
527 |
|
What frame-rate limit applies to the instance? |
Physical-GPU vGPU inventory uses GPU-scoped fields 500 through 513, including virtualization mode, active instance IDs, and supported or creatable vGPU types. Fields 520 through 534 are scoped to an individual vGPU instance. Always confirm the definitions and scope in the field reference for the installed release.
Example: inspect an active vGPU#
DCGM does not currently provide a dedicated dcgmi command that enumerates
vGPU entity IDs. Obtain the active ID from the hypervisor or vGPU management
inventory. Suppose that inventory reports instance ID 17. Stream identifying
and operational fields for that instance as follows:
$ dcgmi dmon --entity-id vgpu:17 \
--field-id 521,524,525,526,527 --count 5
This sample can establish whether the expected VM is attached, whether the
guest driver and license are visible, and whether framebuffer consumption is
changing. A license status of 0 is an actionable vGPU licensing signal;
N/A is different and can mean that the field is unsupported, unavailable,
not yet sampled, or paired with the wrong entity.
For several instances, either list them directly or create a reusable group:
$ dcgmi group --create tenant-a --add vgpu:17,vgpu:23
$ dcgmi dmon --group-id <group-id> --field-id 525,526 --count 10
Replace <group-id> with the ID printed by the create command. Groups are
selectors in the running host engine; they do not establish VM isolation or
vGPU ownership.
Limits of the command-line view#
Some vGPU data, including per-process utilization and encoder or framebuffer-
capture session structures, is represented by binary fields. dcgmi dmon
does not render binary field payloads and displays them as N/A. Use the
C/C++ field APIs or the vGPU management interfaces when the workflow needs
those structured records.
Field availability also depends on the NVIDIA vGPU software release, physical GPU, active instance, and privileges. A numeric field ID existing in the DCGM catalogue does not guarantee that every vGPU environment can supply it.
Further reading#
dcgmi dmon documents monitoring syntax, field output, and unavailable values.
dcgmi group documents reusable entity groups and the
vgpuselector.dcgmi discovery documents what
dcgmican and cannot enumerate.Field Identifiers, Field Scope, and Field APIs are the exhaustive field and programmatic references.