Merge pull request #38918 from sjhala-ccs/cnv-12277

CNV-12277: Removed mention of sriovLiveMigration feature gate

Author: sjhala-ccs

modules/virt-about-live-migration.adoc

@@ -16,4 +16,4 @@ You can use live migration if the following conditions are met:
 
 * Ports `49152` and `49153` must be available in the `virt-launcher` pod. If these ports are specified in the `masquerade` interface, live migration does not function.
 
-* Live migration is supported for virtual machines that are attached to an SR-IOV network interface only if the `sriovLiveMigration` feature gate is enabled in the `HyperConverged` custom resource (CR). When the `spec.featureGates.sriovLiveMigration` field is set to `true`, the `virt-launcher` pod runs with the `SYS_RESOURCE` capability. This might degrade its security.
+* Live migration is supported for virtual machines that are attached to an SR-IOV network interface.

modules/virt-about-upgrading-virt.adoc

@@ -24,8 +24,7 @@ connection. Most automatic updates complete within fifteen minutes.
 
 [IMPORTANT]
 ====
-If you have virtual machines running that cannot be live migrated, they might block an {product-title} cluster upgrade.
-This includes virtual machines that use hostpath provisioner storage or SR-IOV network interfaces that have the `sriovLiveMigration` feature gate disabled.
+If you have virtual machines running that use hostpath provisioner storage, they cannot be live migrated and might block an {product-title} cluster upgrade. 
 
 As a workaround, you can reconfigure the virtual machines so that they can be powered off automatically during a cluster upgrade. Remove the `evictionStrategy: LiveMigrate` field and set the `runStrategy` field to `Always`.
 ====

modules/virt-features-for-storage-matrix.adoc

@@ -51,7 +51,7 @@
 You cannot live migrate virtual machines that use:
 
 * A storage class with ReadWriteOnce (RWO) access mode
-* Passthrough features such as GPUs or SR-IOV network interfaces that have the `sriovLiveMigration` feature gate disabled
+* Passthrough features such as GPUs 
 
 Do not set the `evictionStrategy` field to `LiveMigrate` for these virtual machines.
 ====

virt/virtual_machines/vm_networking/virt-configuring-sriov-device-for-vms.adoc

@@ -8,11 +8,7 @@ toc::[]
 You can configure a Single Root I/O Virtualization (SR-IOV) device for virtual machines in your cluster.
 This process is similar but not identical to configuring an SR-IOV device for {product-title}.
 
-[NOTE]
-====
-Live migration is supported for virtual machines that are attached to an SR-IOV network interface only if the `sriovLiveMigration` feature gate is enabled in the HyperConverged Cluster custom resource (CR). When the `spec.featureGates.sriovLiveMigration` field is set to `true`, the `virt-launcher` pod runs with the `SYS_RESOURCE` capability. This might degrade its security.
-====
-
+[id="prerequisites_configuring-sriov-device-for-vms"]
 == Prerequisites
 * You must have xref:../../../networking/hardware_networks/installing-sriov-operator.adoc#installing-sriov-operator[installed the SR-IOV Operator.]
 
@@ -21,6 +17,7 @@ Live migration is supported for virtual machines that are attached to an SR-IOV
 include::modules/nw-sriov-device-discovery.adoc[leveloffset=+1]
 include::modules/nw-sriov-configuring-device.adoc[leveloffset=+1]
 
+[id="next-steps_configuring-sriov-device-for-vms"]
 == Next steps
 
 * xref:../../../virt/virtual_machines/vm_networking/virt-defining-an-sriov-network.adoc#virt-defining-an-sriov-network[Configuring an SR-IOV network attachment for virtual machines]