Menü Schließen

oVirt Bugfix Release und Async Release veröffentlicht

oVirt Logo

Die Open-Source Virtualisierungslösung oVirt, wurde vor kurzem in der Version freigegeben. oVirt selbst ist eine Alternative für VMWare und vSphere und ermöglicht das Managment von KVM Virtualisierung in Multi-Node-Umgebungen. 

oVirt Release Notes

Please note that in RHEL 8 / CentOS 8 several devices that worked on EL7 are no longer supported.

For example, the megaraid_sas driver is removed. If you use Enterprise Linux 8 hosts you can try to provide the necessary drivers for the deprecated hardware using the DUD method

Known issues

How to prevent hosts entering emergency mode after upgrade from oVirt 4.4.1

Due to [Bug 1837864] – Host enter emergency mode after upgrading to latest build,

If you have your root file system on a multipath device on your hosts you should be aware that after upgrading from 4.4.1 to 4.4.10 you may get your host entering emergency mode.

In order to prevent this be sure to upgrade oVirt Engine first, then on your hosts:

  1. Remove the current lvm filter while still on 4.4.1, or in emergency mode (if rebooted).
  2. Reboot.
  3. Upgrade to 4.4.10 (redeploy in case of already being on 4.4.10).
  4. Run vdsm-tool config-lvm-filter to confirm there is a new filter in place.
  5. Only if not using oVirt Node:
    • run “dracut –force –add multipath” to rebuild initramfs with the correct filter configuration
  6. Reboot.

What’s New in 4.4.10?

Release Note

oVirt Engine

  • BZ 2007286 Host is never fenced after a soft fence attemptPreviously, a non responsive host was first soft-fenced by the engine, but it didn’t fix the connectivity issue. The engine didn’t initiate a hard fence and the host was left in non responsive status.

In this release, Soft fencing has been fixed, and if the soft fencing does’t make the host responsive again, then the non-responding host treatment process continues correctly with the additional steps.


oVirt Engine

  • BZ 1897114 Add additional logging information to be able to understand why host is stuck in Unassigned stateIn this release, monitoring of host refresh capabilities functionality was improved to help debug very rare production issues that sometimes caused the Red Hat Virtualization Manager to lose connectivity with the Red Hat Virtualization hosts.

Bug Fixes


  • BZ 2023344 vdsmd fails to shut down cleanly when it tries to deactivate a used LV
  • BZ 2012832 Snapshot recovery reports false result

oVirt Engine

  • BZ 2013430 RHV 4.4. FIPS install leaves UUID blank in grub after setting kernel option
  • BZ 2032919 Unable to add RHEL 7 host into RHV Manager in clusters 4.2/4.3
  • BZ 2027424 Consume video device from virt-v2v
  • BZ 2022660 Removing a iSCSI storage connection removes all newly added connections
  • BZ 2025872 VM with a PCI host device and max vCPUs >= 256 fails to start

oVirt Engine Data Warehouse

  • BZ 2014882 Memory and CPU overcommit panels are incorrect in ‘Ovirt executive dashboard/cluster dashboard’ in Grafana

oVirt Hosted Engine HA

  • BZ 2026625 _getHaInfo from vdsm can still get stuck if broker socket is not repsonding



  • BZ 2026809 VM remains locked after importing from vmware/external-ova, we see “‘str’ object has no attribute ‘decode’” in the log

oVirt Engine

  • BZ 2037216 VM imported from configuration is stuck in WaitForLaunch once removed quickly after power-off
  • BZ 1854038 Download or upload disk (SDK) fails due to ‘Timed out waiting for transfer XXX to finalize’
  • BZ 1985746 [CBT][Veeam] Full backup is stuck on ‘FINALIZING’ status when an error occurs during the image transfer flow
  • BZ 2027260 Cold backup fail in various ways – backup is reported ready before add_bitmap jobs complete
  • BZ 2018971 [CBT][Veeam] Scratch disks on block-based storage domain created with the wrong initial size.
  • BZ 2018986 [CBT][Veeam] Allow configurable block-based scratch disk initial size
  • BZ 2015470 [CBT] It’s possible to remove a disk immediately after starting a backup
  • BZ 2013932 [CBT] VM backup scratch disks remains if the VM destroyed during the backup

No Doc Update


  • BZ 2022354 Network gateway stays out-of-sync after upgrade

oVirt Engine Data Warehouse

  • BZ 2014883 None of the grafana dashboard shows ethernet statistics for VMs

oVirt Hosted Engine HA

  • BZ 2025381 VDSM logs are spammed due to multiple connection attempts and drops from ha-agent client

Quelle: oVirt 4.4.10 Release Notes | oVirt

oVirt Async Release Notes

Fixing the following bugs:
 – [BZ 1854038] – Download or upload disk (SDK) fails due to ‘Timed out waiting for transfer XXX to finalize’
 – [BZ 2013430] – oVirt 4.4. FIPS install leaves UUID blank in grub after setting kernel option
 – [BZ 2037216] – VM imported from configuration is stuck in WaitForLaunch once removed quickly after power-off

Schreibe einen Kommentar

Deine E-Mail-Adresse wird nicht veröffentlicht. Erforderliche Felder sind mit * markiert