Este conteúdo não está disponível no idioma selecionado.

Chapter 2. Release notes


2.1. OpenShift Virtualization release notes

2.1.1. Providing documentation feedback

To report an error or to improve our documentation, log in to your Red Hat Jira account and submit a Jira issue.

2.1.2. About Red Hat OpenShift Virtualization

With Red Hat OpenShift Virtualization, you can bring traditional virtual machines (VMs) into OpenShift Container Platform and run them alongside containers. In OpenShift Virtualization, VMs are native Kubernetes objects that you can manage by using the OpenShift Container Platform web console or the command line.

OpenShift Virtualization is represented by the OpenShift Virtualization icon.

You can use OpenShift Virtualization the OVN-Kubernetes Container Network Interface (CNI) network provider.

Learn more about what you can do with OpenShift Virtualization.

Learn more about OpenShift Virtualization architecture and deployments.

Prepare your cluster for OpenShift Virtualization.

2.1.2.1. Supported cluster versions for OpenShift Virtualization

The latest stable release of OpenShift Virtualization 4.20 is 4.20.0.

OpenShift Virtualization 4.20 is supported for use on OpenShift Container Platform 4.20 clusters. To use the latest z-stream release of OpenShift Virtualization, you must first upgrade to the latest version of OpenShift Container Platform.

2.1.2.2. Supported guest operating systems

To view the supported guest operating systems for OpenShift Virtualization, see Certified Guest Operating Systems in Red Hat OpenStack Platform, Red Hat Virtualization, OpenShift Virtualization and Red Hat Enterprise Linux with KVM.

2.1.2.3. Microsoft Windows SVVP certification

OpenShift Virtualization is certified in Microsoft’s Windows Server Virtualization Validation Program (SVVP) to run Windows Server workloads.

The SVVP certification applies to:

  • Red Hat Enterprise Linux CoreOS workers. In the Microsoft SVVP Catalog, they are named Red Hat OpenShift Container Platform 4.20.
  • Intel and AMD CPUs.

2.1.3. Quick starts

Quick start tours are available for several OpenShift Virtualization features. To view the tours, click the Help icon ? in the menu bar on the header of the OpenShift Container Platform web console and then select Quick Starts. You can filter the available tours by entering the keyword virtualization in the Filter field.

2.1.4. New and changed features

This release adds new features and enhancements related to the following components and concepts:

2.1.4.1. Installation and update

  • You can now directly update OpenShift Virtualization to a later z-stream (x.y.z) release without applying each intermediate z-stream version.

    Note

    Ensure that you update to the latest z-stream release of your current minor (x.y) version before updating to the next minor version.

  • Using OpenShift Virtualization on a bare-metal cluster installed on an ARM64 (AARCH64) system is now generally available. For more information, see ARM64 compatibility.

2.1.4.2. Virtualization

  • The descheduler profile DevKubeVirtRelieveAndMigrate has been renamed to KubeVirtRelieveAndMigrate and is now generally available. The updated profile improves VM eviction stability during live migrations by enabling background evictions and reducing oscillatory behavior. For more information, see Configuring descheduler evictions for virtual machines.
  • You can now use the kube_application_aware_resourcequota and kube_application_aware_resourcequota_creation_timestamp metrics to query the current usage and creation times of the Application-Aware Quota (AAQ) Operator resources. For more information, see AAQ Operator metrics.

2.1.4.3. Networking

  • You can now hot plug and hot unplug a secondary network interface to a VM without manually triggering live migration. You do not need permission to create and list VirtualMachineInstanceMigration objects. For more information, see Hot plugging secondary network interfaces.
  • You can now use the Border Gateway Protocol (BGP) to configure dynamic ingress and egress routing for VMs that are connected to primary user-defined networks. Importing routes from provider networks into OVN-Kubernetes eliminates the need to manually configure routes on hosts. With dynamic egress, you can export VM IP addresses to provider networks, making the VMs directly reachable from outside the cluster. For more information, see Advertise cluster network routes with Border Gateway Protocol.

2.1.4.4. Web console

  • In the OpenShift Container Platform web console, the Migrations tab of the Virtualization page now displays a progress bar for each migrating virtual machine.
  • When performing live migration of a VM, you can now specify the particular node for the VM to migrate to.
  • The procedure for hot plugging disks now includes an optional step for selecting a bus type. You can select the virtio-blk or the virtio-scsi bus type. The virtio-blk type is the default. For more information, see Hot plugging VM disks.
  • The InstanceTypes tab on the Create new VirtualMachine page now includes options for selecting huge pages. These options appear in the M and CX series of instance types. They are accessible both through the Select InstanceType tiles and in the Default InstanceType menu of the Add volume dialog box.

    For more information about selecting huge pages for an instance type, see "Creating a VM from an instance type by using the web console".

2.1.4.5. Monitoring

  • Added documentation for the kubevirt_vmi_vcpu_delay_seconds_total Prometheus metric. This metric reports the time a virtual CPU (vCPU) was queued by the host scheduler but was not running. The updated documentation helps users better understand vCPU queue delays in OpenShift Virtualization environments.
  • The following alerts for the OpenShift Virtualization Operator are now included in the OpenShift Virtualization runbooks:

    • HighNodeCPUFrequency
    • VirtualMachineStuckInUnhealthyState
    • VirtualMachineStuckOnNode
    • PersistentVolumeFillingUp
    • DeprecatedMachineType
    • HCOGoldenImageWithNoSupportedArchitecture
    • HCOGoldenImageWithNoArchitectureAnnotation
    • HCOMultiArchGoldenImagesDisabled

    For a complete list of virtualization metrics, see the openshift/runbooks Git repository.

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.

2.1.4.6. Notable technical changes

  • Before this update, only the virtio-scsi bus type could be used for hot plugging disks. With this update, the virtio-blk bus type is supported as well.

2.1.5. Deprecated and removed features

2.1.5.1. Deprecated features

Deprecated features are included in the current release and supported. However, they will be removed in a future release and are not recommended for new deployments.

  • The OperatorConditionsUnhealthy alert is deprecated. You can safely silence it.
  • All hot plugged disks are persistent by default. The use of non-persistent hot plugged disks is deprecated. They will not be supported in future releases.

2.1.5.2. Removed features

Removed features are no longer supported in OpenShift Virtualization.

  • With this release, support for the Data Plane Development Kit (DPDK) checkup has been removed. You can no longer run a predefined checkup to verify if your OpenShift Container Platform cluster node can run a VM with a DPDK workload with zero packet loss.

2.1.6. Technology Preview features

Some features in this release are currently in Technology Preview. These experimental features are not intended for production use. Note the following scope of support on the Red Hat Customer Portal for these features:

Technology Preview Features Support Scope

  • OpenShift Virtualization is now supported on Azure Boost.
  • Golden image support for heterogeneous clusters is now available.

2.1.7. Bug fixes

  • Restoring a snapshot of a VM after a storage migration no longer fails because of unreferenced dataVolumeTemplate objects. The snapshot process now refreshes the data volume templates in the controller revision to match the volumes list, ensuring consistent data recovery. (CNV-61279)
  • The migration controller in the virt-handler pod was redesigned to separate source, target, and VM responsibilities, ensure deterministic completion, and use a unified VirtualMachineInstance (VMI) cache. (CNV-48348)
  • Virtual Trusted Platform Module (vTPM) persistence is now enabled by default in VM templates. BitLocker system checks in Windows VMs no longer pass with non-persistent vTPM devices. (CNV-36448)
  • On s390x systems, VMs created from a template with the Boot from CD option now boot correctly. CD-ROM devices are attached as SCSI instead of SATA, which is not supported on s390x architecture. (CNV-61740)

2.1.8. Known issues

2.1.8.1. Networking

  • When you update from OpenShift Container Platform 4.12 to a newer minor version, VMs that use the cnv-bridge Container Network Interface (CNI) fail to live migrate. (https://access.redhat.com/solutions/7069807)

    • As a workaround, change the spec.config.type field in your NetworkAttachmentDefinition manifest from cnv-bridge to bridge before performing the update.
  • Red Hat OpenShift Service Mesh 3.1.1 and Istio versions 1.25 and later are incompatible with OpenShift Virtualization 4.20 because the annotation traffic.sidecar.istio.io/kubevirtInterfaces is deprecated. (OSSM-10883)

    • As a workaround, when installing Service Mesh for integration with OpenShift Virtualization, select version 3.0.4 and Istio 1.24.4 instead of the default versions that are displayed in the web console.
2.1.8.1.1. Nodes
  • Uninstalling OpenShift Virtualization does not remove the feature.node.kubevirt.io node labels created by OpenShift Virtualization. You must remove the labels manually. (CNV-38543)

2.1.8.2. Virtualization

  • Live migration fails if the VM name exceeds 47 characters. (CNV-61066)
  • OpenShift Virtualization links a service account token in use by a pod to that specific pod. OpenShift Virtualization 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. (CNV-33835)

    • As a workaround, use user accounts rather than service accounts because user account tokens are not bound to a specific pod.

2.1.8.3. IBM Z and IBM LinuxONE

Important

Using OpenShift Virtualization in a cluster deployed on s390x architecture is a Technology Preview feature only. Technology Preview features are not supported with Red Hat production service level agreements (SLAs) and might not be functionally complete. Red Hat does not recommend using them in production. These features provide early access to upcoming product features, enabling customers to test functionality and provide feedback during the development process.

For more information about the support scope of Red Hat Technology Preview features, see Technology Preview Features Support Scope.

  • VMs based on s390x architecture can only use the IPL boot mode. However, in the OpenShift Container Platform 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. (CNV-56889)
Voltar ao topo
Red Hat logoGithubredditYoutubeTwitter

Aprender

Experimente, compre e venda

Comunidades

Sobre a documentação da Red Hat

Ajudamos os usuários da Red Hat a inovar e atingir seus objetivos com nossos produtos e serviços com conteúdo em que podem confiar. Explore nossas atualizações recentes.

Tornando o open source mais inclusivo

A Red Hat está comprometida em substituir a linguagem problemática em nosso código, documentação e propriedades da web. Para mais detalhes veja o Blog da Red Hat.

Sobre a Red Hat

Fornecemos soluções robustas que facilitam o trabalho das empresas em plataformas e ambientes, desde o data center principal até a borda da rede.

Theme

© 2025 Red Hat