Merge pull request #94672 from SNiemann15/ocpvirt_back_to_tp

[CNV-52363] IBM Z readd tech preview

Author: ousleyp

virt/install/preparing-cluster-for-virt.adoc

@@ -59,6 +59,14 @@ endif::[]
 --
 
 * {ibm-z-name} or {ibm-linuxone-name} (s390x architecture) systems where an {product-title} cluster is installed in logical partitions (LPARs). See xref:../../installing/installing_ibm_z/preparing-to-install-on-ibm-z.adoc#preparing-to-install-on-ibm-z_preparing-to-install-on-ibm-z[Preparing to install on {ibm-z-title} and {ibm-linuxone-title}].
++
+--
+ifdef::openshift-enterprise[]
+:FeatureName: Using {VirtProductName} in a cluster deployed on s390x architecture
+include::snippets/technology-preview.adoc[]
+:!FeatureName:
+endif::[]
+--
 
 endif::openshift-rosa,openshift-dedicated,openshift-rosa-hcp[]
 
@@ -85,13 +93,19 @@ ifndef::openshift-rosa,openshift-dedicated,openshift-rosa-hcp[]
 
 You can use {VirtProductName} in an {product-title} cluster that is installed in logical partitions (LPARs) on an {ibm-z-name} or {ibm-linuxone-name} (`s390x` architecture) system.
 
+ifdef::openshift-enterprise[]
+:FeatureName: Using {VirtProductName} in a cluster deployed on s390x architecture
+include::snippets/technology-preview.adoc[]
+:!FeatureName:
+endif::[]
+
 Some features are not currently available on `s390x` architecture, while others require workarounds or procedural changes. These lists are subject to change.
 
 [discrete]
 [id="currently-unavailable-ibm-z_{context}"]
 ==== Currently unavailable features
 
-The following features are currently not supported on `s390x` architecture:
+The following features are currently not available on `s390x` architecture:
 
 * Memory hot plugging and hot unplugging
 * Node Health Check Operator
@@ -102,6 +116,7 @@ The following features are currently not supported on `s390x` architecture:
 * IPv6
 * {ibm-name} Storage scale
 * {hcp-capital} for {VirtProductName}
+* VM pages using HugePages
 
 The following features are not applicable on `s390x` architecture:
 
@@ -110,6 +125,8 @@ The following features are not applicable on `s390x` architecture:
 * USB host passthrough
 * Configuring virtual GPUs
 * Creating and managing Windows VMs
+* Hyper-V
+
 
 [discrete]
 [id="functionality-differences_{context}"]
@@ -123,6 +140,10 @@ The following features are available for use on s390x architecture but function
 
 * When xref:../../virt/monitoring/virt-exposing-downward-metrics.adoc#virt-configuring-downward-metrics_virt-exposing-downward-metrics[configuring a downward metrics device], if you use a VM preference, the `spec.preference.name` value must be set to `rhel.9.s390x` or another available preference with the format `*.s390x`.
 
+* When xref:../../virt/creating_vm/virt-creating-vms-from-instance-types.adoc#virt-creating-vms-from-instance-types[creating virtual machines from instance types], you are not allowed to set `spec.domain.memory.maxGuest` because memory hot plugging is not supported on {ibm-z-name}.
+
+* Prometheus queries for VM guests could have inconsistent outcome in comparison to `x86`.
+
 endif::openshift-rosa,openshift-dedicated,openshift-rosa-hcp[]
 
 // Section is in assembly so that we can use xrefs
@@ -247,7 +268,7 @@ Currently, IPI is not supported on {ibm-z-name}.
 
 [NOTE]
 ====
-Fence Agents Remediation uses supported fencing agents to reset failed nodes faster than the Self Node Remediation Operator. This improves overall virtual machine high availability. For more information, see the link:https://access.redhat.com/articles/7057929[OpenShift Virtualization - Fencing and VM High Availability Guide] knowledgebase article. 
+Fence Agents Remediation uses supported fencing agents to reset failed nodes faster than the Self Node Remediation Operator. This improves overall virtual machine high availability. For more information, see the link:https://access.redhat.com/articles/7057929[OpenShift Virtualization - Fencing and VM High Availability Guide] knowledgebase article.
 ====
 
 * High availability for any platform is available by using either a monitoring system or a qualified human to monitor node availability. When a node is lost, shut it down and run `oc delete node <lost_node>`.