diff --git a/virt/release_notes/virt-4-19-release-notes.adoc b/virt/release_notes/virt-4-19-release-notes.adoc
index 24822e50efce..5180434c7405 100644
--- a/virt/release_notes/virt-4-19-release-notes.adoc
+++ b/virt/release_notes/virt-4-19-release-notes.adoc
@@ -318,6 +318,14 @@ You can also disable free page reporting of memory ballooning for all new VMs. T
 
 Release notes for asynchronous releases of Red Hat {VirtProductName}.
 
+[id="virt-4.19.3_{context}"]
+=== 4.19.3
+
+.New and changed features
+
+//CNV-65955 DOC: s390 Architecture TP to GA
+* Support for s390x architecture is now generally available. You can use {VirtProductName} on an {product-title} cluster that has been deployed in one or more logical partitions (LPARs) on {ibm-z-name} and {ibm-linuxone-name} (s390x architecture) systems. For more information, see xref:../../virt/install/preparing-cluster-for-virt.adoc#ibm-z-linuxone-compatibility_preparing-cluster-for-virt[{ibm-z-title} and {ibm-linuxone-title} compatibility].
+
 [id="virt-4.19.1_{context}"]
 === 4.19.1
 
@@ -332,7 +340,7 @@ See xref:../../virt/fusion_access_SAN/fusion-access-san-overview.adoc#about-fusi
 
 .Known issues
 
-//OCPNAS-56 Failed localdisk should have its status reflected 
+//OCPNAS-56 Failed localdisk should have its status reflected
 * When a file system in {FusionSAN} has two local disks and one local disk fails, both local disks move to the `Unknown` state, with no indication which of the local disks failed. (*OCPNAS-56*)
 //(link:https://issues.redhat.com/browse/OCPNAS-56[OCPNAS-56])