January 2026 - Users - oVirt List Archives

oVirt Administration Portal will not load after upgrade to 4.5.7
by scottwilkins＠cicsnc.org 20 Jan '26

20 Jan '26

I'm running oVirt in standalone on a Centos Stream 9 box. The VM Portal will load fine, but the Admin Portal fails with a 500 error. When I dig down in the server log, the error message is: Caused by: java.lang.IllegalArgumentException: MigrationPolicies has no value for version: 4.8 When I run engine-config -g MigrationPolicies I get results for version 4.2 up to 4.7, but nothing for 4.8. Is this something I need to manually add? One other piece of confusing info is that the console still lists the version as 4.5.6-1.el9. I didn't see any errors during either the yum update or the engine-setup processes, but I may have missed something. Any help you all can give me would be great.

1 0

Upgrading self-hosted engine from 4.5.6 on Stream 8
by Devin A. Bougie 20 Jan '26

20 Jan '26

Hi, All. If possible, I’d greatly appreciate an overview of the recommended procedure for upgrading a self-hosted engine setup from 4.5.6 on CentOS Stream release 8 to 4.5.7. All of our hosts are running fully-updated AlmaLinux 9. When we initially setup our cluster, this gave us a self-hosted engine running CentOS Stream release 8. As 8 is no-longer supported, it seems the first step for upgrading our cluster from 4.5.6 to 4.5.7 is to update the engine to Stream 9 (or 10)? Has anyone else completed this upgrade, and does this look like the right approach? 1. Put the cluster in global maintenance: hosted-engine --set-maintenance --mode=global 2. Stop ovirt-engine on the engine VM: systemctl stop ovirt-engine.service 3. Backup the engine: /usr/bin/engine-backup --mode=backup --scope=all --file="/var/lib/ovirt-engine-backup/backup.tar.bz2" --log=/var/log/ovirt-engine-backups.log 4. From an existing host, deploy a new engine: hosted-engine --deploy --restore-from-file=backup.tar.bz2 5. From the new engine, re-install each existing host. If that looks correct, is there anything we need to do for the existing hosts that are running many VMs in addition to the hosted engine? Should we expect to be able to deploy a new engine and update each host to 4.5.7 without downtime for any running VMs? Many thanks, Devin

1 0

oVirt 4.5.7 is now generally available
by Jean-Louis Dupond 20 Jan '26

20 Jan '26

*oVirt 4.5.7 is now generally available* The oVirt Project is pleased to announce the availability of the 4.5.7 release as of January 13 2026. oVirt is a free open-source distributed virtualization solution, designed to manage your entire enterprise infrastructure. oVirt uses the trusted KVM hypervisor and is built upon several other community projects, including libvirt, Gluster, PatternFly, and Ansible. This release is now available on x86_64 architecture for: oVirt Node NG (based on CentOS Stream 9) CentOS Stream 9 CentOS Stream 10 RHEL 9 and derivatives RHEL 10 and derivatives To everyone using the oVirt Node NG we urge you to switch over to another way of using the product for ensured stability and security due to the way of how that product is structured. To find out how to interact with oVirt developers and users and ask questions, visit our community page. All issues or bugs should be reported via oVirt GitHub. If you’d like to try oVirt as quickly as possible, follow the instructions on the Download page. For complete installation, administration, and usage instructions, see the oVirt Documentation. For a general overview of oVirt, read the About oVirt page. To learn about features introduced before 4.5.7, see the release notes for previous versions. IMPORTANT If you are going to install on RHEL or derivatives please follow Installing on RHEL first. NOTE It is important that for installs on RHEL 10 and derivates that version 10.0-4 (or newer) of centos-release-ovirt45 is used. What’s New in 4.5.7? New releases in 4.5.7 Contributors New cpu’s What’s New in 4.5.7? CentOS 10 and AlmaLinux 10 support. Fixed CVE-2024-7259 Introduced new CPU’s Bumped external dependencies. Implemented new way of deploying to maven central. All Java code is now built on Java 21 and compatible with Java 11. Reconnect faster to host after reboot, instead of static 10 minutes adapted to connect when host is back online. On boot of VM have a spare of NumOfPciExpressPorts PCIe ports available instead of a fixed number. Add the optional attach_wgt flag to the vm start endpoint. This will auto attach the virtio-win iso to the vm. Ability to add tags to templates via UI in the administration panel. Add operating system description to host api object. Added option for user to decide preference of vnc console invocation. Added Windows 2025 and RHEL 10 to OS list. Improve isLiveDelete check on VM. Dropped deprecated packages. Dropped Ceph, Cinderlib and collectd in Centos 10 due to not available. Added new DC/Cluster level (4.8). Cluster level 4.8 now uses pc-q35-rhel9.6.0 machine type and enables discard-no-unref by default. Added ability to alter video device through API. Set audio value to ich9 starting from rhel7 on Q35. When a VDS network error occurs during VM start, set the VM status to “Unknown” instead of letting it fall through to “Down”. This to prevent duplicate VM deployments. Ability to update QoS on running VM’s when a QoS profile has been modified or when QoS was changed on a vNIC profile Many more changes were implemented in the newest releases of the oVirt packages and can be read about in detail down below. New releases in 4.5.7 ovirt-engine-4.5.7 cockpit-ovirt-0.16.3 ovirt-hosted-engine-setup-2.7.2 ovirt-node-ng-4.4.3 ovirt-engine-extension-aaa-ldap-1.5.0 otopi-1.10.5 ovirt-engine-ui-extensions-1.3.8-1 imgbased-1.2.26 ovirt-engine-metrics-1.6.3 ovirt-engine-extension-aaa-jdbc-1.3.1 ovirt-engine-keycloak-15.0.2-7 engine-db-query-1.6.5 ovirt-host-4.5.1-1 ovirt-engine-extensions-api-1.0.2 ovirt-log-collector-4.5.1 ovirt-engine-extension-aaa-misc-1.1.2 ovirt-dependencies-4.5.7 ovirt-setup-lib-1.3.4 ovirt-engine-build-dependencies-4.5.7 ovirt-web-ui 1.9.4 vdsm v4.50.6.1 vdsm-jsonrpc-java v1.7.4 python-ovirt-engine-sdk4 4.6.3 ovirt-engine-api-metamodel 1.3.11 ovirt-engine-api-model 4.6.1 ovirt-ansible-collection 3.2.1 ovirt-dwh 4.5.10 ovirt-hosted-engine-ha v2.5.2 mom 0.6.5 ovirt-engine-sdk-ruby 4.6.1 ovirt-engine-sdk-java 4.6.0 ovirt-provider-ovn 1.2.36 ovirt-engine-nodejs-modules 2.3.21 ovirt-vmconsole 10.0.10 terraform-provider-ovirt v2.2.0 ovirt-engine-sdk 4.5.1 ioprocess v1.4.3 userstorage 0.5.3 ovirt-tinycore-linux v13.13 ovirt-engine-wildfly 24.0.1-3 ovirt-jboss-modules-maven-plugin 2.0.4 Contributors 33 people contributed to this release: Arthur Verschaeve (Contributed to: ovirt-site) Artur Socha (Contributed to: vdsm-jsonrpc-java) Brian King (Contributed to: mom) Brooklyn Dewolf (Contributed to: vdsm) Eli Marcus (Contributed to: ovirt-site) Frank Wall (Contributed to: ovirt-site) Geoff O’Callaghan (Contributed to: ovirt-site, ovirt-node-ng-image, ovirt-appliance) Jasper Berton (Contributed to: ovirt-engine, vdsm, ovirt-web-ui, ovirt-engine-sdk, ovirt-site, cockpit-ovirt, ovirt-engine-sdk-java, mom, ovirt-engine-sdk-ruby, ovirt-provider-ovn, ovirt-engine-api-model, ovirt-hosted-engine-setup, python-ovirt-engine-sdk4, ovirt-engine-sdk-go, java-client-kubevirt, ovirt-engine-extension-aaa-ldap, ovirt-engine-api-metamodel, ovirt-engine-ui-extensions, imgbased, ovirt-engine-metrics, releng-tools, ovirt-engine-extension-aaa-jdbc, ovirt-engine-keycloak, ovirt-hosted-engine-ha, engine-db-query, ovirt-cockpit-sso, ovirt-lldp-labeler, ovirt-engine-extensions-api, ovirt-log-collector, ovirt-engine-nodejs-modules, ovirt-engine-extension-aaa-misc, ovirt-jboss-modules-maven-plugin, ovirt-dependencies, ovirt-setup-lib, ovirt-engine-build-dependencies) Jean-Louis Dupond (Contributed to: ovirt-engine, vdsm, terraform-provider-ovirt, ovirt-web-ui, ovirt-engine-sdk, ovirt-ansible-collection, cockpit-ovirt, ovirt-engine-sdk-java, ovirt-node-ng-image, ovirt-appliance, ovirt-imageio, mom, ovirt-engine-sdk-ruby, ovirt-provider-ovn, ovirt-engine-api-model, ovirt-hosted-engine-setup, python-ovirt-engine-sdk4, ovirt-engine-sdk-go, ovirt-system-tests, java-client-kubevirt, ovirt-engine-extension-aaa-ldap, otopi, vdsm-jsonrpc-java, ovirt-engine-api-metamodel, ovirt-engine-ui-extensions, imgbased, ovirt-release, ovirt-openvswitch, ovirt-engine-metrics, ovirt-vmconsole, ovirt-engine-extension-aaa-jdbc, ovirt-dwh, ovirt-engine-keycloak, ost-images, ovirt-hosted-engine-ha, engine-db-query, ovirt-cockpit-sso, ioprocess, buildcontainer, ovirt-engine-extensions-api, ovirt-log-collector, ovirt-engine-nodejs-modules, ovirt-engine-extension-aaa-misc, ovirt-jboss-modules-maven-plugin, ovirt-dependencies, ovirt-engine-wildfly, ovirt-setup-lib, userstorage, ovirt-tinycore-linux, ovirt-resources-upload-action, ovirt-build-dependencies, ovirt-engine-build-dependencies) Anton (Contributed to: ovirt-imageio) Jiri Slezka (Contributed to: ovirt-engine) Joschokvc (Contributed to: ovirt-engine-extension-aaa-jdbc) José Enrique Gutiérrez Mazón (Contributed to: vdsm) Juan Hernandez (Contributed to: ovirt-engine-sdk-ruby, ovirt-engine-api-metamodel) Keenan Brock (Contributed to: ovirt-engine-sdk-ruby) Lev Veyde (Contributed to: ovirt-site) Marc Dequènes (Duck) (Contributed to: ovirt-site) Marcin Sobczyk (Contributed to: vdsm, ovirt-system-tests, ovirt-vmconsole, ost-images) Martin Necas (Contributed to: ovirt-ansible-collection) Martin Perina (Contributed to: ovirt-engine-extension-aaa-ldap, ovirt-engine-extension-aaa-misc) Maxime Besson (Contributed to: terraform-provider-ovirt) Michael Trapp (Contributed to: vdsm) Michalskrivanek (Contributed to: ovirt-node-ng-image, ovirt-appliance, ovirt-system-tests) Peter Boden (Contributed to: ovirt-engine, vdsm, ovirt-ansible-collection, ovirt-provider-ovn, ovirt-engine-api-model, ovirt-system-tests, otopi, vdsm-jsonrpc-java, ovirt-vmconsole, releng-tools, ovirt-dwh, ost-images, ovirt-tinycore-linux, ovirt-engine-build-dependencies) Puhamihai (Contributed to: terraform-provider-ovirt) Raaghav Wadhawan (Contributed to: ovirt-engine) Sandro Bonazzola (Contributed to: ovirt-site, 512-byte-vm, ovirt-node-ng-image, ovirt-engine-sdk-ruby, python-ovirt-engine-sdk4, ovirt-system-tests, ovirt-engine-api-metamodel, imgbased, ovirt-release, ovirt-dwh, ost-images, ovirt-host, ioprocess, safelease, upload-rpms-action, checkout-action, ovirt-engine-build-dependencies) Sergii Kuzko (Contributed to: vdsm) Shubhaoracle (Contributed to: vdsm, ovirt-ansible-collection) Stanislav Melnichuk (Contributed to: ovirt-engine, ovirt-dwh, ovirt-engine-extension-aaa-misc, ovirt-engine-build-dependencies) Tomáš Golembiovský (Contributed to: mom) Vic Demuzere (Contributed to: ovirt-engine-sdk-go) Yedidyah Bar David (Contributed to: ovirt-dwh) New cpu’s Intel: Sapphire Rapids Server Secure Sapphire Rapids Server (all security features mentioned in v2 on qemu) AMD: EPYC Milan Secure EPYC Milan (all security features mentioned in v2 on qemu) EPYC Rome EPYC Rome v2 (all features mentioned in v2 on qemu) EPYC Genoa IBM: POWER10

3 3

oVirt 4.5.7 upgrade guide for RHEL8 systems
by Kapetanakis Giannis 20 Jan '26

20 Jan '26

oVirt 4.5.7 release is definitely good news and kudos to the devs behind this release. Can we have a documentation ideally on https://www.ovirt.org/documentation/upgrade_guide/ or at least in the mailing list for the upgrade path from RHEL8 (and derivatives) and 4.5.6 to 4.5.7 on newer OS? I see on release notes that only RHEL9+ is supported for both engine and hosts. Our systems, both standalone engine as well as hosts are all on Rocky 8. Will a backup of engine, install of 4.5.7 on new OS and restore from backup will be able to see and manage the non-upgraded RHEL8 hosts? Maybe upgrade the hosts first and the engine later? What is the recommended way of making the upgrade? On more question: RHEL10 does not see v2 hosts. Alma does support them. Are there v2 binaries released for RHEL10 systems (engine and hosts) or should we stick to RHEL9. Thanks, Giannis

1 0

Deploy process frezzes with "Wait for the host to be up"
by Leandro Pereira 19 Jan '26

19 Jan '26

Hello everyone I'm installing ovirt 4.5 on a homelab VMWare Workstation (which I did several times weeks ago). Not so much that I'm going through technical problems. The deploy engine works in a stage called '[ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Wait for the host to be up]'. I couldn't find any error messages in both the Host logs and the Engine. Try different ways to automatically create the ovirtmgmt network, as you previously created it. The fact is that at this stage the engine is still not connected to the ovirtmgmt network, and from this point the depoloy does not pass through the host cannot communicate with the Engine with the FQDN informed.

3 3

oVirt thick client Python+QT6 - any interest?
by John Boero 17 Jan '26

17 Jan '26

Hi I've been a longtime fan of oVirt since my Red Hat days. I was just playing around with vibe coding a thick client in Python + QT6 to give oVirt the app I think it always deserved. Results are early but pretty slick actually. Is anybody interested in pulling this into the GH org and developing further? An early beta after about 2 hours of playing can be found here: https://github.com/jboero/ovirt_client John Boero

1 0

Unable to install oVirt on RHEL7.5
by SS00514758＠techmahindra.com 15 Jan '26

15 Jan '26

Hi All, I am unable to install oVirt on RHEL7.5, to install it I am taking reference of below link, https://www.ovirt.org/documentation/install-guide/chap-Installing_oVirt.html But though it is not working for me, couple of dependencies is not getting installed, and because of this I am not able to run the ovirt-engine, below are the depencies packages that unable to install, Error: Package: collectd-write_http-5.8.0-6.1.el7.x86_64 (@ovirt-4.2-centos-opstools) Requires: collectd(x86-64) = 5.8.0-6.1.el7 Removing: collectd-5.8.0-6.1.el7.x86_64 (@ovirt-4.2-centos-opstools) collectd(x86-64) = 5.8.0-6.1.el7 Updated By: collectd-5.8.1-1.el7.x86_64 (epel) collectd(x86-64) = 5.8.1-1.el7 Available: collectd-5.7.2-1.el7.x86_64 (ovirt-4.2-centos-opstools) collectd(x86-64) = 5.7.2-1.el7 Available: collectd-5.7.2-3.el7.x86_64 (ovirt-4.2-centos-opstools) collectd(x86-64) = 5.7.2-3.el7 Available: collectd-5.8.0-2.el7.x86_64 (ovirt-4.2-centos-opstools) collectd(x86-64) = 5.8.0-2.el7 Available: collectd-5.8.0-3.el7.x86_64 (ovirt-4.2-centos-opstools) collectd(x86-64) = 5.8.0-3.el7 Available: collectd-5.8.0-5.el7.x86_64 (ovirt-4.2-centos-opstools) collectd(x86-64) = 5.8.0-5.el7 Help me to install this. Looking forward to resolve this issue. Regards Sumit Sahay

8 10

Offline installation - is is possible?
by postecom＠gmail.com 15 Jan '26

15 Jan '26

I have been looking at oVirt for a while. My current virtualization is an older version of RHV. With RHV, I could have my hypervisors completely isolated from the internet and all updates come through Red Hat's Satellite. Is is possible to add the installation repos as a product in Satellite? It is very important that the hypervisors not have access to the Internet, but all the documentation and installation info that I can find wants the hypervisors to use the COPR plugin and have direct access to centos stream. Thank you

7 9

install el10 host with ovirt45-testing
by Jiří Sléžka 02 Jan '26

02 Jan '26

Hi, I am testing host installation from ovirt45-testing repo. I choose Alma Linux 10 for it as it still support Spice. Engine runs also 4.5.7 but on Rocky Linux 9. Other hosts are Rocky Linux 8. First small glitch is that after yum install centos-release-ovirt45-testing the repo centos-ovirt45-testing is disabled by default. I did not mention it and try to create new host witch failed early in Install stage (playbook can't find ovirt packages). I know it is not typical problem but in this case I ended up with host stucked in Install stage and cannot switch it to maintenance and/or remove it. I had to do it directly in db. Second try was without problems but after I set-up network I ended in Non operational mode because "Host does not comply with the cluster emulated machine. The cluster emulated machine is pc-i440fx-rhel7.6.0;pc-q35-rhel8.6.0 and the host emulated machines are pc-q35-rhel9.6.0,pc-q35-rhel9.4.0,q35,pc-q35-rhel9.2.0,pc-q35-rhel9.0.0,pc-q35-rhel10.0.0,pc,pc-i440fx-rhel10.0.0." As I read list archives I could try "Reset Emulated Machine" in Cluster menu. Current emulated machine type is pc-q35-rhel8.6.0. One odd thing is that "Clusters hosts must be down in order to perform this action." which leads me to question whether it is safe or possible in my current mix of el8 and el10 hosts. Cheers, Jiri

2 1