CNV#57754_04: Misc 4.20 RN Fixes

Author: danielclowers

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

@@ -64,8 +64,8 @@ This release adds new features and enhancements related to the following compone
 //CNV-43322 Release notes:TP to GA OCI
 * Installing {VirtProductName} on {oci-first-no-rt} is now generally available. For more information, see link:https://access.redhat.com/articles/7118050[{VirtProductName} and Oracle Cloud Infrastructure known issues and limitations] in the Red{nbsp}Hat Knowledgebase, and link:https://github.com/oracle-quickstart/oci-openshift/blob/main/docs/openshift-virtualization.md[Installing {VirtProductName} on OCI] on GitHub.
 
-[id="virt-4-20-infrastructure_{context}"]
-=== Infrastructure
+//[id="virt-4-20-infrastructure_{context}"]
+//=== Infrastructure
 
 [id="virt-4-20-virtualization_{context}"]
 === Virtualization
@@ -82,8 +82,8 @@ This release adds new features and enhancements related to the following compone
 //CNV-52857 and CNV-56324
 * xref:../../virt/vm_networking/virt-setting-interface-link-state.adoc#virt-setting-interface-link-state[Managing the link state of a virtual machine interface] is now generally available. In previous releases this was a Technology Preview feature.
 
-[id="virt-4-20-storage_{context}"]
-=== Storage
+//[id="virt-4-20-storage_{context}"]
+//=== Storage
 
 [id="virt-4-20-web_{context}"]
 === Web console
@@ -101,11 +101,11 @@ Added documentation for the `kubevirt_vmi_vcpu_delay_seconds_total` Prometheus m
 //CNV-67575
 The guest agent ping probe is now generally available (GA). Previously, this feature was provided as a Technology Preview. It has been fully tested and is now supported for production use.
 
-[id="virt-4-20-documentation_{context}"]
-=== Documentation improvements
+//[id="virt-4-20-documentation_{context}"]
+//=== Documentation improvements
 
-[id="virt-4-20-notable-technical-changes_{context}"]
-=== Notable technical changes
+//[id="virt-4-20-notable-technical-changes_{context}"]
+//=== Notable technical changes
 
 
 [id="virt-4-20-deprecated-removed_{context}"]
@@ -160,11 +160,9 @@ link:https://access.redhat.com/support/offerings/techpreview[Technology Preview
 [id="virt-4-20-known-issues_{context}"]
 == Known issues
 
-[discrete]
-[id="virt-4-20-ki-monitoring_{context}"]
-=== Monitoring
+//[id="virt-4-20-ki-monitoring_{context}"]
+//=== Monitoring
 
-[discrete]
 [id="virt-4-20-ki-networking_{context}"]
 === Networking
 
@@ -177,18 +175,15 @@ link:https://access.redhat.com/support/offerings/techpreview[Technology Preview
 ** As a workaround, when installing {SMProductShortName} for integration with {VirtProductName}, select version 3.0.4 and Istio 1.24.4 instead of the default versions that are displayed in the web console.
 
 
-[discrete]
 [id="virt-4-20-ki-nodes_{context}"]
 ==== Nodes
 
 //CNV-38543: According to Stu, this remains an issue in 4.20
 * Uninstalling {VirtProductName} does not remove the `feature.node.kubevirt.io` node labels created by {VirtProductName}. You must remove the labels manually. (link:https://issues.redhat.com/browse/CNV-38543[*CNV-38543*])
 
-[discrete]
-[id="virt-4-20-ki-storage_{context}"]
-==== Storage
+//[id="virt-4-20-ki-storage_{context}"]
+//==== Storage
 
-[discrete]
 [id="virt-4-20-ki-virtualization_{context}"]
 === Virtualization
 
@@ -199,11 +194,9 @@ link:https://access.redhat.com/support/offerings/techpreview[Technology Preview
 * {VirtProductName} links a service account token in use by a pod to that specific pod. {VirtProductName} implements a service account volume by creating a disk image that contains a token. If you migrate a VM, then the service account volume becomes invalid. (link:https://issues.redhat.com/browse/CNV-33835[*CNV-33835*])
 ** As a workaround, use user accounts rather than service accounts because user account tokens are not bound to a specific pod.
 
-[discrete]
-[id="virt-4-20-ki-webconsole_{context}"]
-=== Web console
+//[id="virt-4-20-ki-webconsole_{context}"]
+//=== Web console
 
-[discrete]
 [id="virt-4-20-ki-ibm-z_{context}"]
 === {ibm-z-title} and {ibm-linuxone-title}
 
@@ -213,17 +206,11 @@ include::snippets/technology-preview.adoc[]
 :!FeatureName:
 endif::[]
 
-// cnv-61957 - GPU devices should not be shown in UI
-* GPU devices appear in the *Hardware Devices* list for s390x VMs, but GPU support is not available for s390x architecture. You can disregard these list entries. (link:https://issues.redhat.com/browse/CNV-61957[CNV-61957])
-
 // 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 - boot mode
+// 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])
-
-// cnv-56890 - threads
-* In the {product-title} web console, it is erroneously possible to define multiple CPU threads for a VM based on s390x architecture. If you define multiple CPU threads, the VM enters a `CrashLoopBackOff` state with the `qemu-kvm: S390 does not support more than 1 threads` error. (link:https://issues.redhat.com/browse/CNV-56890[CNV-56890])