diff --git a/virt/release_notes/virt-4-18-release-notes.adoc b/virt/release_notes/virt-4-18-release-notes.adoc
index ce4fef09c970..e67cc870ce54 100644
--- a/virt/release_notes/virt-4-18-release-notes.adoc
+++ b/virt/release_notes/virt-4-18-release-notes.adoc
@@ -204,6 +204,10 @@ include::snippets/technology-preview.adoc[]
 [id="virt-4-18-ki-virtualization"]
 ==== Virtualization
 
+//CNV-56998 is doc issue; CNV-56659 is original issue
+* Virtual machine instance migrations might fail during workload updates or when a large number of migrations are triggered. This is more likely to occur if there are at least 400 pending migrations, undefined migrations, or a combination of both. (link:https://issues.redhat.com/browse/CNV-56659[*CNV-56659*])
+** As a workaround, follow the procedure in the link:https://access.redhat.com/solutions/7108359[Red{nbsp}Hat Knowledgebase solution for this issue].
+
 //CNV-36448: 4.16 - Unresolved
 * When adding a virtual Trusted Platform Module (vTPM) device to a Windows VM, the BitLocker Drive Encryption system check passes even if the vTPM device is not persistent. This is because a vTPM device that is not persistent stores and recovers encryption keys using ephemeral storage for the lifetime of the `virt-launcher` pod. When the VM migrates or is shut down and restarts, the vTPM data is lost. (link:https://issues.redhat.com/browse/CNV-36448[*CNV-36448*])