Multi-vGPU#
Multi-vGPU attaches several vGPU devices to one VM. Devices may be time-sliced or MIG-backed and can sit on different physical GPUs - you are not limited to slicing one physical GPU across many VMs.
That layout suits training and inference that need multiple GPUs inside one guest: each vGPU is dedicated to that VM, so workloads in the VM do not compete with other VMs on the same physical GPU for those devices (for example, a VM with two A100-class vGPUs versus one).
Compatibility Rules#
You can assign multiple vGPUs with differing amounts of frame buffer to a single VM, provided the board type and the series of all the vGPUs are the same. For example, you can assign an A40-48C vGPU and an A40-16C time-sliced vGPU to the same VM. You can also assign an A100-4-20C vGPU and one A100-2-10C vGPU to a VM, both on MIG instances from an A100 board. However, you cannot assign an A30-8C vGPU and an A16-8C vGPU to the same VM.
For architecture-specific board and vGPU combinations, refer to Multi-vGPU Board Support.
See also
Multi-vGPU and P2P - shared hypervisor support for Multi-vGPU and P2P
Peer-To-Peer (P2P) CUDA Transfers - NVLink P2P CUDA transfers between vGPUs in the same VM
Device Groups - topology-aware multi-GPU provisioning
NVIDIA NVSwitch - NVLink fabric for multi-GPU bandwidth
NVIDIA vGPU Types by Hardware - full per-board vGPU profile listings