From 16caf208f14b3fb30af06362afeaf1dfd41e7aa6 Mon Sep 17 00:00:00 2001 From: danielclowers Date: Thu, 23 Oct 2025 10:51:49 -0400 Subject: [PATCH] OCPBUGS-51113: Remove known issue from 4.20 RN --- virt/release_notes/virt-4-20-release-notes.adoc | 8 +------- 1 file changed, 1 insertion(+), 7 deletions(-) diff --git a/virt/release_notes/virt-4-20-release-notes.adoc b/virt/release_notes/virt-4-20-release-notes.adoc index 4061bc387d22..5d94a6e0dc70 100644 --- a/virt/release_notes/virt-4-20-release-notes.adoc +++ b/virt/release_notes/virt-4-20-release-notes.adoc @@ -62,7 +62,7 @@ This release adds new features and enhancements related to the following compone === Installation and update //CNV-62403 direct z-stream updates -* You can now directly update {VirtProductName} to a later z-stream (x.y.z) release without applying each intermediate z-stream version. +* You can now directly update {VirtProductName} to a later z-stream (x.y.z) release without applying each intermediate z-stream version. + [NOTE] ==== @@ -252,11 +252,5 @@ include::snippets/technology-preview.adoc[] :!FeatureName: endif::[] -// 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` 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: Matan indicated this will remain in 4.20 but is targeted for 4.21 * VMs based on s390x architecture can only use the *IPL* boot mode. However, in the {product-title} web console, the *Boot mode* list for s390x VMs incorrectly includes *BIOS*, *UEFI*, and *UEFI (secure)* boot modes. If you select one of these modes for an s390x-based VM, the operation fails. (link:https://issues.redhat.com/browse/CNV-56889[CNV-56889])