4.2. Red Hat Virtualization 4.3 Batch Update 1 (ovirt-4.3.4)

4.2.1. Bug Fix

The items listed in this section are bugs that were addressed in this release:


The self-hosted engine was not detecting exceptions or failures when the ‘--vm-start’ command was initiated. As a result, the retry count was not incremented and therefore the score of the host was not reduced for rescheduling.

In this release, the self-hosted engine setup fails when the create VM functionality fails. As a result, the self-hosted engine High Availability agent can adjust its retry count and reduce the score of the host, giving other hosts a higher priority.


Previously, the Conversion playbook failed while creating an .ssh directory. The current release fixes this bug.


Previously, when upgrading the Open Virtual Network (OVN), the status of the ovn-controller service was not saved, and consequently, the service did not start after the upgrade. The ovn-controller service is now included in the list of tracked services, and starts after the upgrade.


Previously, when converting virtual machines to Red Hat Virtualization using the SSH method, the SSH wrapper used the root SSH key instead of the VDSM user’s SSH key. This bug is now fixed.


Updating the Data Center level while the virtual machine was suspended, resulted in the virtual machine not resuming activity following the update. In this release, the suspended virtual machine must be resumed before the Data Center level update. Otherwise, the operation fails.


When a virtual machine migration entered post-copy mode and remained in that mode for a long time, the migration sometimes failed and the migrated virtual machine was powered off. In this release, post-copy migrations are maintained to completion.


Converting a storage domain to the V5 format failed when there were partly deleted volumes with cleared metadata remaining in the storage domain following an unsuccessful delete volume operation. In this release, storage domain conversion succeeds even when partly deleted volumes with cleared metadata remain in the storage domain.


In some scenarios, the PCI address of a hotplugged SR-IOV vNIC was overwritten by an empty value, and as a result, the NIC name in the virtual machine was changed following a reboot. In this release, the vNIC PCI address is stored in the database and the NIC name persists following a virtual machine reboot.

4.2.2. Enhancements

This release of Red Hat Virtualization features the following enhancements:


A new generic Linux x86 operating system selection named ‘Other Linux (kernel 4.x)’ has been added to the drop down list of operating systems available when creating a new virtual machine in Red Hat Virtualization.


This release adds support for virtual machines to use Windows 2019 x64 in the Administration Portal.


A new configuration variable 'EventPurgeTimeoutInHours' has been added to set the number of hours an event can stay in the queue before being cleaned up. The variable can be modified using engine-config. The initial default value is 3 hours.


When a host is running in FIPS mode, VNC must use SASL authorization instead of regular passwords because of the weak algorithm inherent in the VNC protocol.

In order to facilitate that process, the Ansible role 'ovirt-host-setup-vnc-sasl' is provided. It must be run manually on all FIPS hosts. The role does the following: * Creates an (empty) SASL password database * Prepares an SASL configuration file for qemu * Changes the libvirt configuration file for qemu


Previously, you could only test a host’s network connectivity with ICMP (ping). Sometimes the gateway does not reply to a ping request, such as when ping is blocked at the network level. When such a failure occurred during the installation of a self-hosted engine, the installation failed. Now you can test network connectivity by checking if the DNS resolution is working, by pinging the gateway, by testing a TCP connection to a configurable port on a configurable host, or you can proceed with installation without running any test.

4.2.3. Release Notes

This section outlines important details about the release, including recommended practices and notable changes to Red Hat Virtualization. You must take this information into account to ensure the best possible outcomes for your deployment.


Red Hat Virtualization 4.3 supports host machines with AMD EPYC processors.