openshift · abrennan89 · May 27, 2026
diff --git a/modules/virt-binding-devices-vfio-driver.adoc b/modules/virt-binding-devices-vfio-driver.adoc
@@ -19,6 +19,7 @@ The `MachineConfig` Operator generates the `/etc/modprobe.d/vfio.conf` on the no
 ====
 Enabling IOMMU is not required on `s390x` architecture.
 ====
+
 * You have installed the {oc-first}.
 
 .Procedure
@@ -34,6 +35,7 @@ NVIDIA GPU is supported on `x86` and `aarch64` architectures, Intel QAT is suppo
 ----
 $ lspci -nnv | grep -i <gpu_accelerator>
 ----
++
 Valid values for `<gpu_accelerator>` are `nvidia`, `qat`, and `spyre`.
 +
 Example output:
@@ -122,6 +124,7 @@ NAME                             GENERATEDBYCONTROLLER                      IGNI
 ----
 $ lspci -nnk -d <vendor_id>:
 ----
++
 The output confirms that the VFIO driver is being used.
 +
 Example output:

diff --git a/modules/virt-enabling-dynamic-key-injection-cli.adoc b/modules/virt-enabling-dynamic-key-injection-cli.adoc
@@ -29,7 +29,56 @@ Example manifest:
 +
 [source,yaml]
 ----
-include::snippets/virt-dynamic-key.yaml[]
+apiVersion: kubevirt.io/v1
+kind: VirtualMachine
+metadata:
+  name: example-vm
+  namespace: example-namespace
+spec:
+  dataVolumeTemplates:
+    - metadata:
+        name: example-vm-volume
+      spec:
+        sourceRef:
+          kind: DataSource
+          name: rhel9
+          namespace: openshift-virtualization-os-images
+        storage:
+          resources: {}
+  instancetype:
+    name: u1.medium
+  preference:
+    name: rhel.9
+  runStrategy: Always
+  template:
+    spec:
+      domain:
+        devices: {}
+      volumes:
+        - dataVolume:
+            name: example-vm-volume
+          name: rootdisk
+        - cloudInitNoCloud:
+            userData: |-
+              #cloud-config
+              runcmd:
+              - [ setsebool, -P, virt_qemu_ga_manage_ssh, on ]
+          name: cloudinitdisk
+      accessCredentials:
+        - sshPublicKey:
+            propagationMethod:
+              qemuGuestAgent:
+                users: ["cloud-user"]
+            source:
+              secret:
+                secretName: authorized-keys
+---
+apiVersion: v1
+kind: Secret
+metadata:
+  name: authorized-keys
+data:
+  key: c3NoLXJzYSB...
 ----
 * `spec.template.spec.volumes.cloudInitNoCloud` defines the data source, for example `userData`.
 * `spec.template.spec.accessCredentials.sshPublicKey.source.secret.secretName` defines the `secret` object name.
@@ -47,10 +96,11 @@ $ oc create -f <manifest_file>.yaml
 [source,terminal]
 ----
 $ virtctl start vm example-vm -n example-namespace
----- 
+----
 
 .Verification
-* Get the VM configuration:
+
+* Get the VM configuration by running the following command:
 +
 [source,terminal]
 ----

diff --git a/modules/virt-enabling-persistentreservation-feature-gate.adoc b/modules/virt-enabling-persistentreservation-feature-gate.adoc
@@ -1,8 +1,8 @@
 // Module included in the following assemblies:
 //
-// * * virt/virtual_machines/virtual_disks/virt-configuring-shared-volumes-for-vms.adoc
+// * virt/virtual_machines/virtual_disks/virt-configuring-shared-volumes-for-vms.adoc
 
-:_mod-docs-content-type: PROCEDURE
+:_mod-docs-content-type: CONCEPT
 [id="virt-enabling-persistentreservation-feature-gate_{context}"]
 = Enabling the PersistentReservation feature gate
 
@@ -11,7 +11,8 @@ You can enable the SCSI `persistentReservation` feature gate and allow a LUN-bac
 
 The `persistentReservation` feature gate is disabled by default. You can enable the `persistentReservation` feature gate by using the web console or the command line.
 
-.Prerequisites
+[id="virt-enabling-persistentreservation-feature-gate-prereqs_{context}"]
+== Prerequisites
 
 * Cluster administrator privileges are required.
 * The volume access mode `ReadWriteMany` (RWX) is required if the VMs that are sharing disks are running on different nodes. If the VMs that are sharing disks are running on the same node, the `ReadWriteOnce` (RWO) volume access mode is sufficient.

diff --git a/modules/virt-update-node-network-config-form.adoc b/modules/virt-update-node-network-config-form.adoc
@@ -1,20 +1,25 @@
+// Module included in the following assemblies:
+//
+// * networking/k8s_nmstate/k8s-nmstate-updating-node-network-config.adoc
+
 :_mod-docs-content-type: PROCEDURE
 [id="virt-update-node-network-config-form_{context}"]
 = Updating the policy by using form
 
 [role="_abstract"]
 You can update a `NodeNetworkConfigurationPolicy` object by using the form view in the web console.
 
+[NOTE]
+====
+Addition of a VLAN interface using the form is not supported. To add a VLAN interface, you must use YAML to create the policy. Once added, you cannot edit the policy using form.
+====
+
 .Procedure
+
 . Navigate to *Networking* → *NodeNetworkConfigurationPolicy*.
 
 . In the *NodeNetworkConfigurationPolicy* page, click the {kebab} icon placed next to the policy you want to edit, and click *Edit*.
 
 . Edit the fields that you want to update.
 
 . Click *Save*.
-
-[NOTE]
-====
-Addition of a VLAN interface using the form is not supported. To add a VLAN interface, you must use YAML to create the policy. Once added, you cannot edit the policy using form.
-====
diff --git a/snippets/virt-dynamic-key.yaml b/snippets/virt-dynamic-key.yaml
diff --git a/virt/managing_vms/virtual_disks/virt-configuring-shared-volumes-for-vms.adoc b/virt/managing_vms/virtual_disks/virt-configuring-shared-volumes-for-vms.adoc
@@ -31,6 +31,7 @@ include::modules/virt-enabling-persistentreservation-feature-gate-web.adoc[level
 include::modules/virt-enabling-persistentreservation-feature-gate-cli.adoc[leveloffset=+2]
 
 [role="_additional-resources"]
-.Additional resources
+[id="additional-resources_{context}"]
+== Additional resources
 * link:https://www.qemu.org/docs/master/interop/pr-helper.html[Persistent reservation helper protocol]
 * link:https://learn.microsoft.com/en-us/windows-server/failover-clustering/failover-clustering-overview[Failover Clustering in Windows Server and Azure Stack HCI]