CNV-47442: Updated mediated devices example

Author: abrennan89

modules/virt-options-configuring-mdevs.adoc

@@ -40,7 +40,7 @@ spec:
     enabled: true
     defaultWorkload: vm-vgpu
   driver:
-    enabled: false <1>
+    enabled: false
   dcgmExporter: {}
   dcgm:
     enabled: true
@@ -61,23 +61,22 @@ spec:
         - name: WITH_WORKLOAD
           value: "true"
   vgpuManager:
-    enabled: true <2>
-    repository: <vgpu_container_registry> <3>
+    enabled: true
+    repository: <vgpu_container_registry>
     image: <vgpu_image_name>
-    version: nvidia-vgpu-manager
+    version: <nvidia_vgpu_manager_version>
   vgpuDeviceManager:
-    enabled: false <4>
-    config:
-      name: vgpu-devices-config
-      default: default
+    enabled: false
   sandboxDevicePlugin:
-    enabled: false <5>
+    enabled: false
   vfioManager:
-    enabled: false <6>
+    enabled: false
 ----
-<1> Set this value to `false`. Not required for VMs.
-<2> Set this value to `true`. Required for using vGPUs with VMs.
-<3> Substitute `<vgpu_container_registry>` with your registry value.
-<4> Set this value to `false` to allow {VirtProductName} to configure mediated devices instead of the NVIDIA GPU Operator.
-<5> Set this value to `false` to prevent discovery and advertising of the vGPU devices to the kubelet.
-<6> Set this value to `false` to prevent loading the `vfio-pci` driver. Instead, follow the {VirtProductName} documentation to configure PCI passthrough.
++
+** `spec.drive.enabled` is set to `false`. This is not required for VMs.
+** `spec.vgpuManager.enabled` is set to `true`. This is required if you want to use vGPUs with VMs.
+** `spec.vgpuManager.repository` is set to your registry value.
+** `spec.vgpuManager.version` is set to the version of the vGPU driver you have downloaded from the NVIDIA website and used to build the image.
+** `spec.vgpuDeviceManager.enabled` is set to `false` to allow {VirtProductName} to configure mediated devices instead of the NVIDIA GPU Operator.
+** `spec.sandboxDevicePlugin.enabled` is set to `false` to prevent discovery and advertising of the vGPU devices to the kubelet.
+** `spec.vfioManager.enabled` is set to `false` to prevent loading the `vfio-pci` driver. Instead, follow the {VirtProductName} documentation to configure PCI passthrough.

virt/managing_vms/advanced_vm_management/virt-configuring-virtual-gpus.adoc

@@ -1,11 +1,12 @@
 :_mod-docs-content-type: ASSEMBLY
+include::_attributes/common-attributes.adoc[]
 [id="virt-configuring-virtual-gpus"]
 = Configuring virtual GPUs
-include::_attributes/common-attributes.adoc[]
 :context: virt-configuring-virtual-gpus
 
 toc::[]
 
+[role="_abstract"]
 If you have graphics processing unit (GPU) cards, {VirtProductName} can automatically create virtual GPUs (vGPUs) that you can assign to virtual machines (VMs).
 
 include::modules/virt-about-using-virtual-gpus.adoc[leveloffset=+1]
@@ -60,4 +61,4 @@ include::modules/virt-assigning-vgpu-vm-web.adoc[leveloffset=+2]
 [role="_additional-resources"]
 [id="additional-resources_{context}"]
 == Additional resources
-* link:https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/virtualization_deployment_and_administration_guide/sect-troubleshooting-enabling_intel_vt_x_and_amd_v_virtualization_hardware_extensions_in_bios[Enabling Intel VT-X and AMD-V Virtualization Hardware Extensions in BIOS]
+* link:https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/virtualization_deployment_and_administration_guide/sect-troubleshooting-enabling_intel_vt_x_and_amd_v_virtualization_hardware_extensions_in_bios[Enabling Intel VT-X and AMD-V Virtualization Hardware Extensions in BIOS]