Merge pull request #94420 from ousleyp/cnv-61769-418

CNV#61769: fixing identical RN in 4.18

Author: ousleyp

virt/release_notes/virt-4-18-release-notes.adoc

@@ -241,9 +241,10 @@ include::snippets/technology-preview.adoc[]
 include::snippets/technology-preview.adoc[]
 --
 
-// ocpbugs-51113 - ballooning call traces
-* When you create a VM by using {op-system-base-full} container disk images for s390x architecture, call traces referencing `virtio_balloon` print to the VM console. (link:https://issues.redhat.com/browse/OCPBUGS-51113[OCPBUGS-51113])
-** As a workaround, add the following parameter to the VM YAML configuration: `spec.autoattachMemBalloon: false`.
+* When you create a VM by using {op-system-base-full} container disk images for s390x architecture, call traces referencing `virtio_balloon` free page reporting print to the VM console. This is due to a kernel bug. (link:https://issues.redhat.com/browse/OCPBUGS-51113[OCPBUGS-51113])
+** As a workaround, disable memory ballooning for the VM by adding the following parameter to the VM YAML configuration: `spec.domain.devices.autoattachMemBalloon: false`. 
++
+You can also disable free page reporting of memory ballooning for all new VMs. To do so, edit the `HyperConverged` CR and add the parameter `spec.virtualMachineOptions.disableFreePageReporting: true`.
 
 // cnv-56889 - boot mode
 * In the web console, the *Boot mode* list for an s390x VM incorrectly includes *BIOS*, *UEFI*, and *UEFI (secure)* boot modes. If you select one of these modes for an s390x-based VM, the operation fails. This is because VMs based on s390x architecture can only use the *IPL* boot mode. (link:https://issues.redhat.com/browse/CNV-56889[CNV-56889])