|
1 | | -# NVIDIA vGPU profiles commonly exposed by nvidia-vgpu-manager in vGPU |
2 | | -# mode. Used by bundles/iaas.yaml when bundles.iaas.gpuOperatorVariant=vgpu |
3 | | -# and cozystack.gpu-operator is in bundles.enabledPackages. Auto-injected |
4 | | -# into the KubeVirt CR at spec.configuration.permittedHostDevices.mediatedDevices |
5 | | -# and spec.configuration.mediatedDevicesConfiguration. |
| 1 | +# NVIDIA vGPU profiles to EXPOSE to VMs in vGPU mode. Used by |
| 2 | +# bundles/iaas.yaml when bundles.iaas.gpuOperatorVariant=vgpu and |
| 3 | +# cozystack.gpu-operator is in bundles.enabledPackages. Auto-injected |
| 4 | +# into the KubeVirt CR at spec.configuration.permittedHostDevices.mediatedDevices. |
6 | 5 | # |
7 | | -# The profiles below cover the 24Q (3D-optimised) and 48Q (datacenter |
8 | | -# whole-card) splits on the GPU families cozystack supports for vGPU |
9 | | -# (Ampere and earlier — Ada Lovelace and Blackwell use per-VF NVIDIA |
10 | | -# sysfs and are out of scope for the chart's vGPU defaults; see |
11 | | -# system/gpu-operator/values-vgpu.yaml). |
| 6 | +# Division of labour: the GPU Operator's vGPU Device Manager CREATES the |
| 7 | +# mdev devices on each node from a name-based profile config; KubeVirt |
| 8 | +# only EXPOSES the already-created mdevs to VMs, matched by profile name |
| 9 | +# via mdevNameSelector. This file therefore carries only the name-based |
| 10 | +# exposure list — it does NOT ship a mediatedDevicesConfiguration block. |
| 11 | +# That block's mediatedDeviceTypes are numeric nvidia-NNN ids that make |
| 12 | +# KubeVirt itself create mdevs, but those ids are per-(SKU, driver) sysfs |
| 13 | +# indices with no portable value, and would duplicate the Device |
| 14 | +# Manager. Operators who deliberately want KubeVirt to drive creation set |
| 15 | +# host-verified ids via .Values.gpu.mediatedDevicesConfiguration instead. |
| 16 | +# |
| 17 | +# mdevNameSelector must match the on-host profile name the driver exposes |
| 18 | +# under /sys/bus/pci/devices/<BDF>/mdev_supported_types/*/name — which is |
| 19 | +# driver-branch-dependent ("NVIDIA A100-40C" on the vGPU 13+/AIE branch, |
| 20 | +# "GRID A100-40C" on older GRID drivers). The profiles below cover the |
| 21 | +# 24Q/48Q and whole-card C splits on the families cozystack supports for |
| 22 | +# vGPU (Ampere and earlier — Ada Lovelace and Blackwell use per-VF NVIDIA |
| 23 | +# sysfs and are out of scope; see system/gpu-operator/values-vgpu.yaml). |
| 24 | +# Verify against the live node and override via |
| 25 | +# .Values.gpu.permittedHostDevices / .Values.gpu.replaceDefaults if your |
| 26 | +# driver exposes different names: |
| 27 | +# |
| 28 | +# for t in /sys/bus/pci/devices/<BDF>/mdev_supported_types/*; do \ |
| 29 | +# echo "$(basename "$t") -> $(cat "$t"/name)"; done |
12 | 30 | # |
13 | 31 | # externalResourceProvider: true is mandatory — the mediated devices are |
14 | 32 | # published by the vGPU Manager DaemonSet, not by KubeVirt itself. |
@@ -38,18 +56,3 @@ permittedHostDevices: |
38 | 56 | - mdevNameSelector: NVIDIA T4-16Q |
39 | 57 | resourceName: nvidia.com/T4-16Q |
40 | 58 | externalResourceProvider: true |
41 | | -mediatedDevicesConfiguration: |
42 | | - # mediatedDeviceTypes lists the vGPU profile IDs the operator may |
43 | | - # auto-create per-node from the underlying physical GPUs. Numeric IDs |
44 | | - # are the NVIDIA-published vGPU type numbers (see GRID/vGPU release |
45 | | - # notes for the full mapping); listing one whole-card type per GPU |
46 | | - # family keeps the default deterministic. |
47 | | - mediatedDeviceTypes: |
48 | | - - nvidia-559 # A100-40C |
49 | | - - nvidia-560 # A100-80C |
50 | | - - nvidia-558 # A40-48Q |
51 | | - - nvidia-555 # A40-24Q |
52 | | - - nvidia-453 # A30-24C |
53 | | - - nvidia-471 # A10-24Q |
54 | | - - nvidia-413 # V100D-32C |
55 | | - - nvidia-232 # T4-16Q |
|
0 commit comments