kubev2v · anarnold97 · Mar 17, 2026 · Mar 16, 2026 · Mar 16, 2026 · Mar 16, 2026
diff --git a/documentation/doc-Release_notes/master.adoc b/documentation/doc-Release_notes/master.adoc
@@ -30,7 +30,7 @@ include::modules/rn-resolved-issues.adoc[leveloffset=+2]
 
 //include::modules/rn-2-10-2-resolved-issues.adoc[leveloffset=+3]
 
-//include::modules/rn-2-10-1-resolved-issues.adoc[leveloffset=+3]
+include::modules/rn-2-11-1-resolved-issues.adoc[leveloffset=+3]
 
 include::modules/rn-2-11-0-resolved-issues.adoc[leveloffset=+3]
 

diff --git a/documentation/modules/common-attributes.adoc b/documentation/modules/common-attributes.adoc
@@ -22,7 +22,7 @@
 :project-version: 2.11
 :mtv-plan: https://docs.redhat.com/en/documentation/migration_toolkit_for_virtualization/{project-version}/html/planning_your_migration_to_red_hat_openshift_virtualization/
 :mtv-mig: https://docs.redhat.com/en/documentation/migration_toolkit_for_virtualization/{project-version}/html/migrating_your_virtual_machines_to_red_hat_openshift_virtualization/
-:project-z-version: 2.11.0
+:project-z-version: 2.11.1
 :rhel-first: Red Hat Enterprise Linux (RHEL)
 :virt: OpenShift Virtualization
 :must-gather: registry.redhat.io/migration-toolkit-virtualization/mtv-must-gather-rhel8:{project-z-version}

diff --git a/documentation/modules/known-issues-2-11.adoc b/documentation/modules/known-issues-2-11.adoc
@@ -2,13 +2,29 @@
 //
 // * documentation/doc-Release_notes/master.adoc
 
-:_mod-docs-content-type: CONCEPT
+:_mod-docs-content-type: REFERENCE
 [id="known-issues-2-11_{context}"]
 = Known issues
 
 [role="_abstract"]
 {project-first} 2.11 has the following known issues.
 
+VM migration failures when disks exceed LUN ID limit on ESXi host::
+
+During VM migrations with a large number of disks, the ESXi host's limit on discoverable SCSI LUN IDs can lead to migration failures when the disk count surpasses the host's LUN ID limit.
++
+*Workaround:* Increase the `Disk.MaxLUN` value on each ESXi host to support discovery of a higher number of LUN IDs during migrations.
++
+link:https://issues.redhat.com/browse/MTV-4719[MTV-4719]
+
+Live migration support limit in custom namespaces with host providers:: 
+
+Host providers in custom namespaces operate with restricted permissions that prevent {project-short} from accessing resources for live migration support, for example, verifying a feature gate is enabled or synchronizing certificates between namespaces. As a result, live migration currently has limited supported in custom namespaces with host providers. 
++
+*Workaround:* Use the default host provider or create a provider with an appropriate access token. 
++
+link:https://issues.redhat.com/browse/MTV-3347[MTV-3347]
+
 Forklift console plugin fails to load on IPv6-only {ocp-short} clusters::
 
 When {project-short} 2.9.1 is deployed on an IPv6-only {ocp-short} cluster, an incorrect API endpoint prevents the forklift-console-plugin from serving a valid plugin manifest, displaying the error `Failed to get a valid plugin manifest from /api/plugins/forklift-console-plugins/`. While the forklift-ui-plugin pod runs successfully, the console plugin cannot load, preventing access to the {project-short} user interface in the {ocp-short} web console. This issue affects all IPv6-only cluster deployments with {ocp-short} 4.19.7 and CNV 4.19.1.
@@ -55,12 +71,6 @@ When you upload a {vmw} Virtual Disk Development Kit (VDDK) init image, the imag
 +
 link:https://issues.redhat.com/browse/MTV-3673[MTV-3673]
 
-Inaccurate `ConnectionTestFailed` error messages when creating an OVA provider::
-
-When you create an Open Virtual Appliance (OVA) provider in the {project-short} UI, `ConnectionTestFailed` error messages are displayed before the provider status changes to `Ready`. The error messages are misleading and do not accurately reflect the in-progress status of the connection.
-+
-link:https://issues.redhat.com/browse/MTV-3613[MTV-3613]
-
 Fibre Channel (FC) protocol VM migration fails to identify existing FC host objects in Infinibox::
 
 Fibre Channel (FC) protocol VM migration fails to identify existing FC host objects in Infinibox due to incorrect adapter ID comparison. As a consequence, FC protocol VM migration fails to identify existing FC hosts, causing volume creation failure due to incorrect `port_name`.
@@ -69,27 +79,5 @@ Fibre Channel (FC) protocol VM migration fails to identify existing FC host obje
 +
 link:https://issues.redhat.com/browse/MTV-4338[MTV-4338]
 
-Migration stalls during VM migration to OCP with FC::
-
-During the migration of VMs to an OpenShift Container Platform (OCP) cluster with Fibre Channel (FC), the migration stalls when attempting to add a transfer network to a target namespace that does not have permissions to the transfer network.
-+
-*Workaround:* Currently, there is no workaround for this issue.  
-+
-link:https://issues.redhat.com/browse/MTV-4547[MTV-4547]
-
-Unexpected shutdown of forklift-controller due to network or storage map deletion::
-
-Deleting network or storage maps causes the `forklift-controller` to shut down unexpectedly, leaving the migration plan state as `Ready` and causing pods to continue running. 
-+
-*Workaround:* Delete and restart the pods manually.
-+
-link:https://issues.redhat.com/browse/MTV-4413[MTV-4413]
-
-{vmw} warm migration with SATA CD-ROM and SATA disks fails due to source guest OS not being detected::
-
-{vmw} only: Warm migration with SATA CD-ROM and SATA disks fails because of incorrect disk assignment.
-+
-link:https://issues.redhat.com/browse/MTV-4592[MTV-4592]
-
 //For a complete list of all known issues in this release, see the list of link:https://issues.redhat.com/issues/?filter=12472621[Known Issues] in Jira.
 
diff --git a/documentation/modules/new-features-and-enhancements-2-11.adoc b/documentation/modules/new-features-and-enhancements-2-11.adoc
@@ -2,13 +2,19 @@
 //
 // * documentation/doc-Release_notes/master.adoc
 
-:_mod-docs-content-type: CONCEPT
+:_mod-docs-content-type: REFERENCE
 [id="new-features-and-enhancements-2-11_{context}"]
 = New features and enhancements
 
 [role="_abstract"]
 {project-first} 2.11 introduces the following features and enhancements.
 
+Direct OVA import from local machines to {virt} in {project-short} UI::
+
+Previously, this feature was available as Technology Preview. In {project-short} 2.11.1, you can import Open Virtual Appliances (OVAs) directly from local machines to {virt} by uploading the OVAs to NFS through the web browser in the {project-short} UI.
++
+link:https://issues.redhat.com/browse/MTV-3698[MTV-3698]
+
 Customizable service account for pre-plan and post-plan hooks in Create migration plan pages::
 
 In {project-short} 2.11.0, users can set a service account name for pre-plan and post-plan hooks in the Create migration plan pages. This UI setting allows for greater flexibility and control over the service accounts used in these hooks, ensuring they have the necessary permissions to manage cluster resources. The `Service account` field is a free text field as the service account information is not stored in the inventory for a remote cluster. This enhancement improves the overall security and customization of the user's deployment.

diff --git a/documentation/modules/rn-2-10-1-resolved-issues.adoc b/documentation/modules/rn-2-10-1-resolved-issues.adoc
diff --git a/documentation/modules/rn-2-11-0-resolved-issues.adoc b/documentation/modules/rn-2-11-0-resolved-issues.adoc
@@ -2,7 +2,7 @@
 //
 // * documentation/doc-Release_notes/master.adoc
 
-:_mod-docs-content-type: CONCEPT
+:_mod-docs-content-type: REFERENCE
 [id="resolved-issues-2-11-0_{context}"]
 = Resolved issues 2.11.0
 

diff --git a/documentation/modules/rn-2-11-1-resolved-issues.adoc b/documentation/modules/rn-2-11-1-resolved-issues.adoc
@@ -0,0 +1,104 @@
+// Module included in the following assemblies:
+//
+// * documentation/doc-Release_notes/master.adoc
+
+:_content-type: REFERENCE
+[id="resolved-issues-2-11-1_{context}"]
+= Resolved issues 2.11.1
+
+[role="_abstract"]
+Review the resolved issues in this release of {project-short}.
+
+VM migration prevented with duplicate NAD mappings::
++
+--
+Before this update, VM migration succeeded when two Network Interface Controllers (NICs) were connected to the same Network Attachment Definition (NAD). As a consequence, users could not boot the VM after successful migration because both NICs were connected to the same target NAD. This update prevents the assignment of multiple NICs to the same NAD during VM migration, avoiding potential boot failures and failed migrations.
+
+link:https://issues.redhat.com/browse/MTV-3075[MTV-3075]
+--
+
+Misleading `ConnectionTestFailed` errors for OVA providers now hidden::
++
+--
+Before this update, misleading `ConnectionTestFailed` error messages were displayed for Open Virtual Appliance (OVA) providers during creation, due to an issue with the readiness probe in the OVA provider's pod specification. This update hides misleading `ConnectionTestFailed` error messages, allowing for accurate progress visualization during provider creation.
+
+link:https://issues.redhat.com/browse/MTV-3613[MTV-3613]
+--
+
+Forklift-controller no longer unexpectedly shuts down due to map deletion::
++
+--
+Before this update, the deletion of network or storage maps in the `forklift-controller` could cause unexpected shutdowns. With this update, deletion of these maps now results in migration plans moving to a `NotReady` state, as opposed to actively terminating associated pods. 
+
+link:https://issues.redhat.com/browse/MTV-4413[MTV-4413]
+--
+
+Increased memory limits for `forklift-cli-download` pod to prevent `OOMKilled` errors::
++
+--
+Before this update, insufficient memory limits in the `forklift-cli-download` pod caused Kubernetes `OOMKilled` memory errors after an update of the {project-short} Operator. As a result, the pod entered `CrashLoopBackOff` state. This update increases memory limits for the `forklift-cli-download` pod to prevent `OOMKilled` errors, improving deployment stability.
+
+link:https://redhat.atlassian.net/browse/MTV-4482[MTV-4482]
+--
+
+NetApp ONTAP initiator group filtering for XCOPY consistency::
++
+--
+Before this update, VM migrations on ESXi hosts with both FC and iSCSI adapters could experience issues with XCOPY usage because NetApp ONTAP initiator groups contained both FC and iSCSI initiators. With this update, you can filter initiators in ONTAP initiator groups by protocol for XCOPY consistency.
+
+link:https://redhat.atlassian.net/browse/MTV-4515[MTV-4515]
+--
+
+Correct LUN path detection during copy offload for PVCs with economy storage class::
++
+--
+Before this update, copy offload for Persistent Volume Claims (PVCs) that use the `ontap-san-economy` storage class assumed all PVCs used dedicated FlexVols with a specific LUN path. With this update, {project-short} detects the economy storage class and extracts the correct LUN path from the PV attributes, ensuring copy offload functionality.
+
+link:https://redhat.atlassian.net/browse/MTV-4556[MTV-4556]
+--
+
+Shared PVCs now labeled `Shareable: true` in storage offload migrations::
++
+--
+Before this update, shared PersistentVolumeClaims (PVCs) were not labeled `Shareable: true` during migration with storage offload. As a consequence, shareable disks were not automatically attached to VMs. With this release, shared PVCs have the `Shareable: true` label, and shared disks are correctly attached to VMs.
+
+link:https://redhat.atlassian.net/browse/MTV-4580[MTV-4580]
+--
+
+SATA CD-ROM disks skipped during warm migration::
++
+--
+Before this update, warm migration with SATA CD-ROM and SATA disks failed because of incorrect disk assignment. With this release, the SATA CD-ROM disks are intentionally skipped during warm migration because these disks are not migrated, resulting in successful conversion.
+
+link:https://redhat.atlassian.net/browse/MTV-4592[MTV-4592]
+--
+
+Consistent disk order in multi-boot VMs::
++
+--
+Before this update, there were disk order inconsistencies in the `virt-v2v-inspector` because of a conflict in how `libvirt` and {vmw} order the disks. As a consequence, users experienced unpredictable boot failures during VM conversion. With this release, the `virt-v2v-inspector` presents disks in a consistent order, reducing conversion failures in multi-boot VMs.
+
+link:https://redhat.atlassian.net/browse/MTV-4718[MTV-4718]
+--
+
+XFSv4 migrations failed::
++
+--
+{project-short} 2.11.0 was rebased to {rhel-first} 10, which does not support XFS version 4 (XFSv4). As a result, a new `spec.xfsCompatibility` option is available on the migration plan. When set to `false`, the default setting, the plan uses the standard conversion image. When set to `true`, the plan uses the XFS-compatible conversion image instead of the standard conversion image.
+[WARNING]
+====
+If you enable XFS support for a migration plan, then the plan cannot support Btrfs migration.
+====
+link:https://redhat.atlassian.net/browse/MTV-4685[MTV-4685] and link:https://issues.redhat.com/browse/MTV-4709[MTV-4709]
+
+--
+
+Active blocking of migration when target namespaces lack transfer network permissions::
++
+--
+Before this update, during VM migration to Red Hat OpenShift Container Platform (OCP) with Fibre Channel, migration could stall when target namespaces lacked permission to transfer networks. This update enhances error handling with active blocking of migration when target namespaces lack transfer network permissions.
+
+link:https://issues.redhat.com/browse/MTV-4547[MTV-4547]
+--
+
+
diff --git a/documentation/modules/rn-2-11.adoc b/documentation/modules/rn-2-11.adoc
@@ -2,7 +2,7 @@
 //
 // * documentation/doc-Release_notes/master.adoc
 
-:_mod-docs-content-type: CONCEPT
+:_mod-docs-content-type: REFERENCE
 [id="rn-2-11_{context}"]
 = {project-full} 2.11