- Users - oVirt List Archives

Re: [ovirt-announce]oVirt - project update
by Jorge Luis Andrade Escobar 25 Sep '25

25 Sep '25

Congratulation to the team for the effort. I will be nice to see this product evolve. On Tue, Sep 23, 2025 at 2:58 AM Jean-Louis Dupond via Announce <announce(a)ovirt.org> wrote: > > Hi everyone! > > It's been a while since something was announced. But in the background, a lot of work has been done! > Since RedHat fully stepped down from the oVirt development, my team did an awesome job to take the development into our hands and continue building a strong product. > > A lot of steps were taken to just make everything working again. From CI pipelines to build processes to fixing deprecated components etc. > > Next to that, we dropped all support for CentOS 8, as this OS is EOL. > > CentOS Stream 10 / EL 10 > > But next to just the house keeping, we also did a lot of effort to make the project fully building on CentOS Stream 10 (and also on EL 10). > The ovirt-engine (and all other java codebases) now build on OpenJDK 21 instead of OpenJDK 11. > This because OpenJDK 21 is available on both CentOS 9 as CentOS 10. This way the code can be built on the same version for both OS'es. > Still the code is built with release target 11, so you can run it on OpenJDK 11+. > > Next to the Java code, all the python code was reviewed and python-six/python-nose was removed and replaced with native Python 3 code and PyTest. > This to make the code more future proof. > > Also all the needed dependencies were added to the oVirt VIRT SIG to have all oVirt dependencies available on CentOS 10. > > Testing > > As everything builds on CentOS 9 and CentOS 10 now, everyone that wants can easily test the current master version of oVirt. > You can find the fresh builds on COPR: https://copr.fedorainfracloud.org/coprs/ovirt/ovirt-master-snapshot/ > Please note that you need EPEL enabled on CentOS/RHEL 10 builds. As we don't build all our dependencies ourselves when they are available in EPEL. > > The CentOS 9 builds should work smoothly. > The CentOS 10 builds should work ... :) But bugs are expected. > > Therefor it's very helpful if you spend some time testing the new builds, and if you hit any issue, please report it with the needed logs/errors/reproducing steps. > This will help us resolving those issues! > > Deprecated? > > Some things are most likely going to be deprecated or are already removed in CentOS 10 builds: > > Cinderlib > > Cinderlib is not maintained anymore, and not available anymore on CentOS 10. > Therefor we decided to drop the support for cinderlib in CentOS 10. > You will still be able to use it on CentOS 9. > We are looking for some alternative, more updates on this when available :) > > GlusterFS > > As we all know, GlusterFS is also (quite) in maintenance mode. > Packages for GlusterFS are not available on CentOS 10 anymore. So GlusterFS support is dropped on CentOS 10! > > CollectD > > CollectD was used in oVirt to gather metrics of the hosts etc. > As this is neither available on CentOS 10, this has also been removed as a requirement on CentOS 10. > > ovirt-node-ng > > The oVirt node ISO images are currently only partially tested and build not very frequently. > This because the technology used to build those images might need a refresh. > But next to that, we feel like the advantages of having an oVirt node ISO is fairly small. And it even has some major disadvantages, like the fact you need to wait for a new ISO to receive a security update. > Therefor we are thinking of just deprecating ovirt-node-ng ISO's. > You can just install a fresh RHEL/CentOS/Alma/Rocky/... and install the ovirt packages on it. > > Chat > > Some months ago we also introduced a new way of communication, Matrix! > You can find us and other users on https://matrix.to/#/#ovirt:ovirt.tech > Feel free to join, and have a discussion or help each other out with issues! > > Next? > > Currently we try to focus on some testing of the current builds and fix the issues that arise. > Once we feel comfortable, we will create a new release for testing. > Without any major issue, that will be our next oVirt 4.5 release. > > Help > > There are still a lot of things that need love, can get improved, etc. > if you want to help, feel free to reach out. Or just send in some PR's :) > There are easy things (like the website itself https://github.com/oVirt/ovirt-site) that can use some attention. > > Or you can help adding translations via our new Weblate setup on https://translate.ovirt.tech/. > > THANKS! > > Next to that I also want to thank Sandro from RedHat to assist us with questions or with reaching the right people! > And of course all the other people that send in PR's, helped us in the background, upgraded the mailinglist, etc :) > > If there are questions, comments, whatever. Feel free to join us on Matrix, and open the discussion. > > Let's have a great future ahead! > > Jean-Louis > > _______________________________________________ > Announce mailing list -- announce(a)ovirt.org > To unsubscribe send an email to announce-leave(a)ovirt.org > Privacy Statement: https://www.ovirt.org/privacy-policy.html > oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ > List Archives: https://lists.ovirt.org/archives/list/announce@ovirt.org/message/73ZFF255MU… -- Jorge Luis Andrade Escobar jandrade(a)i-t-m.com jandrade(a)itm.gt Red Hat Certified Architect (RHCA) Red Hat Certified Instructor/Examiner (RHCX) # 100-000-967 gpg: 685C 68E8 9F55 771B ED7C 3CC7 5E65 8385 88D3 09A5 Phone: +502 2305-0800 ext. 4005 http://www.i-t-m.com

1 0

Re: [ovirt-announce]oVirt - project update
by Nathanaël Blanchet 23 Sep '25

23 Sep '25

Le mardi 23 septembre 2025 à 10:40 +0200, Jean-Louis Dupond via Announce a écrit : Thank you for the great job! It may be a good idea to communicate such good news on the ovirt website. > > Hi everyone! > > It's been a while since something was announced. But in the > background, a lot of work has been done! > Since RedHat fully stepped down from the oVirt development, my team > did an awesome job to take the development into our hands and > continue building a strong product. > > A lot of steps were taken to just make everything working again. > From CI pipelines to build processes to fixing deprecated components > etc. > > Next to that, we dropped all support for CentOS 8, as this OS is > EOL. > > CentOS Stream 10 / EL 10 > > But next to just the house keeping, we also did a lot of effort to > make the project fully building on CentOS Stream 10 (and also on EL > 10). > The ovirt-engine (and all other java codebases) now build on OpenJDK > 21 instead of OpenJDK 11. > This because OpenJDK 21 is available on both CentOS 9 as CentOS 10. > This way the code can be built on the same version for both OS'es. > Still the code is built with release target 11, so you can run it on > OpenJDK 11+. > > Next to the Java code, all the python code was reviewed and python- > six/python-nose was removed and replaced with native Python 3 code > and PyTest. > This to make the code more future proof. > > Also all the needed dependencies were added to the oVirt VIRT SIG to > have all oVirt dependencies available on CentOS 10. > > Testing > > As everything builds on CentOS 9 and CentOS 10 now, everyone that > wants can easily test the current master version of oVirt. > You can find the fresh builds on COPR: > https://copr.fedorainfracloud.org/coprs/ovirt/ovirt-master-snapshot/ > Please note that you need EPEL enabled on CentOS/RHEL 10 builds. As > we don't build all our dependencies ourselves when they are available > in EPEL. > > The CentOS 9 builds should work smoothly. > The CentOS 10 builds should work ... :) But bugs are expected. > > Therefor it's very helpful if you spend some time testing the new > builds, and if you hit any issue, please report it with the needed > logs/errors/reproducing steps. > This will help us resolving those issues! > > > > Deprecated? > > Some things are most likely going to be deprecated or are already > removed in CentOS 10 builds: > > Cinderlib > > Cinderlib is not maintained anymore, and not available anymore on > CentOS 10. > Therefor we decided to drop the support for cinderlib in CentOS 10. > You will still be able to use it on CentOS 9. > We are looking for some alternative, more updates on this when > available :) > > GlusterFS > > As we all know, GlusterFS is also (quite) in maintenance mode. > Packages for GlusterFS are not available on CentOS 10 anymore. So > GlusterFS support is dropped on CentOS 10! > > CollectD > > CollectD was used in oVirt to gather metrics of the hosts etc. > As this is neither available on CentOS 10, this has also been > removed as a requirement on CentOS 10. > > ovirt-node-ng > > The oVirt node ISO images are currently only partially tested and > build not very frequently. > This because the technology used to build those images might need a > refresh. > But next to that, we feel like the advantages of having an oVirt > node ISO is fairly small. And it even has some major disadvantages, > like the fact you need to wait for a new ISO to receive a security > update. > Therefor we are thinking of just deprecating ovirt-node-ng ISO's. > You can just install a fresh RHEL/CentOS/Alma/Rocky/... and install > the ovirt packages on it. > > Chat > > Some months ago we also introduced a new way of communication, > Matrix! > You can find us and other users on > https://matrix.to/#/#ovirt:ovirt.tech > Feel free to join, and have a discussion or help each other out with > issues! > > Next? > > Currently we try to focus on some testing of the current builds and > fix the issues that arise. > Once we feel comfortable, we will create a new release for testing. > Without any major issue, that will be our next oVirt 4.5 release. > > Help > > There are still a lot of things that need love, can get improved, > etc. > if you want to help, feel free to reach out. Or just send in some > PR's :) > There are easy things (like the website itself > https://github.com/oVirt/ovirt-site) that can use some attention. > > Or you can help adding translations via our new Weblate setup on > https://translate.ovirt.tech/. > > THANKS! > > Next to that I also want to thank Sandro from RedHat to assist us > with questions or with reaching the right people! > And of course all the other people that send in PR's, helped us in > the background, upgraded the mailinglist, etc :) > > > > If there are questions, comments, whatever. Feel free to join us on > Matrix, and open the discussion. > > Let's have a great future ahead! > > Jean-Louis > > _______________________________________________ > Announce mailing list -- announce(a)ovirt.org > To unsubscribe send an email to announce-leave(a)ovirt.org > Privacy Statement: https://www.ovirt.org/privacy-policy.html > oVirt Code of Conduct: > https://www.ovirt.org/community/about/community-guidelines/ > List Archives: > https://lists.ovirt.org/archives/list/announce@ovirt.org/message/73ZFF255MU… -- Nathanaël Blanchet Administrateur Systèmes et Réseaux Service Informatique et REseau (SIRE) Département des systèmes d'information 227 avenue Professeur-Jean-Louis-Viala 34193 MONTPELLIER CEDEX 5 Tél. 33 (0)4 67 54 84 55 Fax 33 (0)4 67 54 84 14 blanchet(a)abes.fr

1 0

GlusterFS & NFS Storage Performance in OLVM/Ovirt – Tuning Advice Needed
by Gunasekhar Kothapalli 18 Sep '25

18 Sep '25

Hi all, I’m benchmarking storage performance on OLVM using fio across several scenarios (local brick, GlusterFS, NFS, both on host and as storage domains in VMs). I’m seeing significant differences in throughput and latency, especially with GlusterFS and OLVM guest disks. Summary of Results: Location IOPS Bandwidth Total IO Avg Latency Block Size Jobs CPU (sys) Notes Local Brick 1816 1816 MiB/s 109 GiB 587 µs 1M 4 45% Fastest, direct disk OLVM Guest Disk using GlusterFS Storage Domain 117 118 MiB/s 8196 MiB 12.3 ms 1M 4 3.80% Virtualization overhead GlusterFS Mounted on Host 211 211 MiB/s 12.4 GiB 18.8 ms 1M 4 3.50% Improved, but still slower NFS Mount on Host 4241 4242 MiB/s 249 GiB 613 µs 1M 4 80% Fastest network storage OLVM Guest Disk using NFS Storage domain 532 532 MiB/s 32.8 GiB 5.4 ms 1M 4 17.40% NFS on OLVM guest Observation: Both GlusterFS and NFS are on the same network VLAN, but NFS consistently outperforms GlusterFS (both on host and as a storage domain in OLVM). This suggests the network isn’t the bottleneck. The issue may be with GlusterFS configuration, protocol overhead, or OLVM’s handling of storage domains. Questions: Has anyone tuned GlusterFS or OLVM for better performance in similar scenarios? Are there recommended settings or architectural changes to improve GlusterFS throughput/latency? Any best practices for OLVM storage domain configuration (GlusterFS vs NFS)? Is this performance gap expected, or should I look deeper into my setup? Test Details: fio commands used Any advice, tuning tips, or references would be greatly appreciated!

1 0

Bugs with Ovirt
by Александр Грибанов 18 Sep '25

18 Sep '25

Dear Sirs, While using virtualization system Ovirt our company meets a bug in the Snapshoot removal service. When trying to delete Snapshoot in the VM with 2 disks the removal service got hung up and generated unavailability error. Just VM switch-off via request poweroff terminates a frozen process. Please let us know if you know about this bug and if you have any solutions to fix the bug. Sep 9 10:22:43 neutron17 libvirtd[3562]: Timed out during operation: cannot acquire state change lock Sep 9 10:22:43 neutron17 libvirtd[3562]: Failed to terminate process 698578 with SIGTERM: Device or resource busy Sep 9 10:22:43 neutron17 libvirtd[3562]: operation failed: domain is not running Sep 9 10:22:43 neutron17 libvirtd[3562]: Cannot start job (modify, none, none) in API remoteDispatchDomainSetSchedulerParameters for domain in-extnc-01-new; current job is (none, none, none) owned by (0 <null>, 0 <null>, 0 <null> (flags=0x0)) for (0s, 0s, 0s) -- С уважением, Александр Грибанов Служба Главного инженера АО "Интерфакс" Aleksandr.Gribanov(a)interfax.ru<mailto:Aleksandr.Gribanov@interfax.ru> Внешний номер: (495) 787-52-12 Внутренний номер: 3036 [1624867792272]

1 0

Is oVirt a dead project ???
by Diggy Mc 17 Sep '25

17 Sep '25

Based on the lack of list activity and updates, I am starting to think oVirt is a dead project. I sure hope not. It is a great product. My two cents: Whomever at Red Hat decided to abandon RHEV is an idiot. j/s Does anyone know if Oracle plans to fund the oVirt project? I think it would be a great move on their part. I believe virtualization still has a future for years to come. If oVirt is a dead project, what is the next best choice enterprise virtualization? ProxMox? Microsoft Hypervisor? Something else? Feedback is appreciated because I manage/recommend virtualization solutions for several small- and medium-sized companies.

5 4

please ignore, it's just a test
by Marc Dequènes (Duck) 17 Sep '25

17 Sep '25

a very taisty test -- Marc Dequènes (Duck) RedHat OSPO CommInfra

1 0

Is the ovirt permanently dead or will there be a new version?
by ecsi＠ecsi.hu 16 Sep '25

16 Sep '25

Hi all! There hasn't been a new release for almost two years... Someone should say something, but not empty promises.

3 2

Is the ovirt permanently dead or will there be a new version?
by ecsi＠ecsi.hu 15 Sep '25

15 Sep '25

Hi all! There hasn't been a new release for almost two years... Someone should say something, but not empty promises.

1 0

Is the ovirt permanently dead or will there be a new version?
by ecsi＠ecsi.hu 15 Sep '25

15 Sep '25

Hi all! There hasn't been a new release for almost two years... Someone should say something, but not empty promises.

1 0

Unable to launch new VM on few hosts due "Max free Memory for scheduling new VMs:" has less value
by dushyantk.sun＠gmail.com 11 Sep '25

11 Sep '25

Few hosts shows unable to launch vms due memory is not available to schedule vm. However vm has enough memory when check free command. If any one come across such issue, please let me know how we can fix it in oracle olvm

1 2