- Users - oVirt List Archives

URGENT : VM Manager Down, error sanlock no ids file
by wodel youchi 28 Oct '25

28 Oct '25

Hi, I've an ovirt HCI deployment, and after a certificate expiration, and some bad cli commands, the VM Manager is down and won't start. The problem is with sanlock, the ids file on dom_md of the hosted storage does not exist anymore. sanlock open error -2 /rhev/data-center/mnt/glusterSD/node10.example.com: _engine/5146d5c4-fb3a-4937-9107-fe020146c2ed/dom_md/ids Is there a way to recreate this file? Regards.

1 0

Installing oVirt on Oracle Linux 9
by Igor Filipovic 22 Oct '25

22 Oct '25

Hi, In case anyone's interested: Today I successfully deployed a new oVirt 4.5.7 on Oracle Linux 9.6 hosts. The bottom line: deployment went fine on a minimal OL9.6 install. In addition to the ovirt/ovirt-master-snapshot repository, you must also enable the ol9_codeready_builder repository — it's required to install libvirt-lock-sanlock. After that SHE installation went smoothly. OS Version: RHEL - 9.6 - 1.0.9.el9 OS Description: Oracle Linux Server 9.6 Kernel Version: 6.12.0 - 104.43.4.2.el9uek.x86_64 KVM Version: 9.1.0 - 15.el9_6.9 LIBVIRT Version: libvirt-10.10.0-7.7.0.1.el9_6 VDSM Version: vdsm-4.50.6-202510211310.git33e8c2c63.el9

1 0

Hosted engine deployment failing on step Check OVF_STORE volume status
by igor.filipovic＠power.in.rs 21 Oct '25

21 Oct '25

Hi, I have tried several different physical hosts and several different OS releases (Alma 9.6, Rocky 9.6, CentOS 9 stream) to deploy hosted engine. My scenario is physical hosts with shared FC storage. Deployment always fails at step "Check OVF_STORE volume status" ... Any ideas ? BR, Igor Details in log: # cat /var/log/ovirt-hosted-engine-setup/ovirt-hosted-engine-setup-20251019183708-eo1ffp.log | grep ERROR ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 62940 2025-10-19 19:15:36,379+0200 ERROR otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:113 {'changed': True, 'stdout': '{\n "apparentsize": "134217728",\n "capacity": "134217728",\n "children": [],\n "ctime": "1760893778",\n "description": "{\\"DiskAlias\\":\\"OVF_STORE\\",\\"DiskDescription\\":\\"OVF_STORE\\"}",\n "disktype": "OVFS",\n "domain": "08d9d3f1-86fe-4159-95a8-bd686f44716d",\n "format": "RAW",\n "generation": 0,\n "image": "0d4c388c-37a8-4161-9e5b-874af83c03c7",\n "lease": {\n "offset": 106954752,\n "owners": [],\n "path": "/dev/08d9d3f1-86fe-4159-95a8-bd686f44716d/leases",\n "version": null\n },\n "legality": "LEGAL",\n "mtime": "0",\n "parent": "00000000-0000-0000-0000-000000000000",\n "pool": "",\n "sequence": 1,\n "status": "OK",\n "truesize": "134217728",\n "type": "PREALLOCATED",\n "uuid": "1c41fd5e-7e6e-4b2b-be76-3deb47b30c05",\n "voltype": "LEAF"\n}', 'stderr': '', 'rc': 0, 'cmd': ['vdsm-client', 'Volume', 'getInfo', 'storagepoolID=e6d35c1a-ad0c-11f0-a750-00163e67b4b6', 'storagedomainID=08d9d3f1-86fe-4159-95a8-bd686f44716d', 'imageID=0d4c388c-37a8-4161-9e5b-874af83c03c7', 'volumeID=1c41fd5e-7e6e-4b2b-be76-3deb47b30c05'], 'start': '2025-10-19 19:13:28.803335', 'end': '2025-10-19 19:13:29.074381', 'delta': '0:00:00.271046', 'msg': '', 'invocation': {'module_args': {'_raw_params': 'vdsm-client Volume getInfo storagepoolID=e6d35c1a-ad0c-11f0-a750-00163e67b4b6 storagedomainID=08d9d3f1-86fe-4159-95a8-bd686f44716d imageID=0d4c388c-37a8-4161-9e5b-874af83c03c7 volumeID=1c41fd5e-7e6e-4b2b-be76-3deb47b30c05', '_uses_shell': False, 'stdin_add_newline': True, 'strip_empty_ends': True, 'argv': None, 'chdir': None, 'executable': None, 'creates': None, 'removes': None, 'stdin': None}}, 'stdout_lines': ['{', ' "apparentsize": "134217728",', ' "capacity": "134217728",', ' "children": [],', ' "ctime": "1760893778",', ' "description": "{\\"DiskAlias\\":\\"OVF_STORE\\",\\"DiskDescription\\":\\"OVF_STORE\\"}",', ' "disktype": "OVFS",', ' "domain": "08d9d3f1-86fe-4159-95a8-bd686f44716d",', ' "format": "RAW",', ' "generation": 0,', ' "image": "0d4c388c-37a8-4161-9e5b-874af83c03c7",', ' "lease": {', ' "offset": 106954752,', ' "owners": [],', ' "path": "/dev/08d9d3f1-86fe-4159-95a8-bd686f44716d/leases",', ' "version": null', ' },', ' "legality": "LEGAL",', ' "mtime": "0",', ' "parent": "00000000-0000-0000-0000-000000000000",', ' "pool": "",', ' "sequence": 1,', ' "status": "OK",', ' "truesize": "134217728",', ' "type": "PREALLOCATED",', ' "uuid": "1c41fd5e-7e6e-4b2b-be76-3deb47b30c05",', ' "voltype": "LEAF"', '}'], 'stderr_lines': [], '_ansible_no_log': False, 'failed': True, 'attempts': 12, 'item': {'name': 'OVF_STORE', 'image_id': '1c41fd5e-7e6e-4b2b-be76-3deb47b30c05', 'id': '0d4c388c-37a8-4161-9e5b-874af83c03c7'}, 'ansible_loop_var': 'item', '_ansible_item_label': {'name': 'OVF_STORE', 'image_id': '1c41fd5e-7e6e-4b2b-be76-3deb47b30c05', 'id': '0d4c388c-37a8-4161-9e5b-874af83c03c7'}} 2025-10-19 19:15:36,481+0200 ERROR otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:113 {'changed': True, 'stdout': '{\n "apparentsize": "134217728",\n "capacity": "134217728",\n "children": [],\n "ctime": "1760893778",\n "description": "{\\"DiskAlias\\":\\"OVF_STORE\\",\\"DiskDescription\\":\\"OVF_STORE\\"}",\n "disktype": "OVFS",\n "domain": "08d9d3f1-86fe-4159-95a8-bd686f44716d",\n "format": "RAW",\n "generation": 0,\n "image": "4e00f0d5-d002-47aa-98ea-cd4b55dc4a2d",\n "lease": {\n "offset": 105906176,\n "owners": [],\n "path": "/dev/08d9d3f1-86fe-4159-95a8-bd686f44716d/leases",\n "version": null\n },\n "legality": "LEGAL",\n "mtime": "0",\n "parent": "00000000-0000-0000-0000-000000000000",\n "pool": "",\n "sequence": 1,\n "status": "OK",\n "truesize": "134217728",\n "type": "PREALLOCATED",\n "uuid": "933a3401-13cf-49c8-81a2-0656926bb33d",\n "voltype": "LEAF"\n}', 'stderr': '', 'rc': 0, 'cmd': ['vdsm-client', 'Volume', 'getInfo', 'storagepoolID=e6d35c1a-ad0c-11f0-a750-00163e67b4b6', 'storagedomainID=08d9d3f1-86fe-4159-95a8-bd686f44716d', 'imageID=4e00f0d5-d002-47aa-98ea-cd4b55dc4a2d', 'volumeID=933a3401-13cf-49c8-81a2-0656926bb33d'], 'start': '2025-10-19 19:15:35.773925', 'end': '2025-10-19 19:15:36.051910', 'delta': '0:00:00.277985', 'msg': '', 'invocation': {'module_args': {'_raw_params': 'vdsm-client Volume getInfo storagepoolID=e6d35c1a-ad0c-11f0-a750-00163e67b4b6 storagedomainID=08d9d3f1-86fe-4159-95a8-bd686f44716d imageID=4e00f0d5-d002-47aa-98ea-cd4b55dc4a2d volumeID=933a3401-13cf-49c8-81a2-0656926bb33d', '_uses_shell': False, 'stdin_add_newline': True, 'strip_empty_ends': True, 'argv': None, 'chdir': None, 'executable': None, 'creates': None, 'removes': None, 'stdin': None}}, 'stdout_lines': ['{', ' "apparentsize": "134217728",', ' "capacity": "134217728",', ' "children": [],', ' "ctime": "1760893778",', ' "description": "{\\"DiskAlias\\":\\"OVF_STORE\\",\\"DiskDescription\\":\\"OVF_STORE\\"}",', ' "disktype": "OVFS",', ' "domain": "08d9d3f1-86fe-4159-95a8-bd686f44716d",', ' "format": "RAW",', ' "generation": 0,', ' "image": "4e00f0d5-d002-47aa-98ea-cd4b55dc4a2d",', ' "lease": {', ' "offset": 105906176,', ' "owners": [],', ' "path": "/dev/08d9d3f1-86fe-4159-95a8-bd686f44716d/leases",', ' "version": null', ' },', ' "legality": "LEGAL",', ' "mtime": "0",', ' "parent": "00000000-0000-0000-0000-000000000000",', ' "pool": "",', ' "sequence": 1,', ' "status": "OK",', ' "truesize": "134217728",', ' "type": "PREALLOCATED",', ' "uuid": "933a3401-13cf-49c8-81a2-0656926bb33d",', ' "voltype": "LEAF"', '}'], 'stderr_lines': [], '_ansible_no_log': False, 'failed': True, 'attempts': 12, 'item': {'name': 'OVF_STORE', 'image_id': '933a3401-13cf-49c8-81a2-0656926bb33d', 'id': '4e00f0d5-d002-47aa-98ea-cd4b55dc4a2d'}, 'ansible_loop_var': 'item', '_ansible_item_label': {'name': 'OVF_STORE', 'image_id': '933a3401-13cf-49c8-81a2-0656926bb33d', 'id': '4e00f0d5-d002-47aa-98ea-cd4b55dc4a2d'}} 2025-10-19 19:15:59,830+0200 ERROR otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:113 fatal: [localhost]: FAILED! => {"changed": false, "msg": "The system may not be provisioned according to the playbook results: please check the logs for the issue, fix accordingly or re-deploy from scratch.\n"} 2025-10-19 19:16:00,155+0200 ERROR otopi.context context._executeMethod:151 Failed to execute stage 'Closing up': Failed executing ansible-playbook 2025-10-19 19:16:32,551+0200 ERROR otopi.context context._executeMethod:151 Failed to execute stage 'Clean up': [Errno 2] No such file or directory: '/var/lib/ovirt-hosted-engine-setup/answers/answers-20251019191632.conf' 2025-10-19 19:16:32,597+0200 ERROR otopi.plugins.gr_he_common.core.misc misc._terminate:164 Hosted Engine deployment failed: please check the logs for the issue, fix accordingly or re-deploy from scratch.

2 2

Migrating hosted engine to new storage
by Seann G. Clark 20 Oct '25

20 Oct '25

All, I have been working on this issue for a few weeks now. I am moving off old fiber-channel storage to new iSCSI, and the last device to move is the hosted-engine. From everything I have read, the standard procedure/mentality on migrating this should look as follows for 4.5, which is the version I am on: 1.) Backup existing hosted engine 2.) Set cluster into global maintenance 3.) Re-install hosted engine from backup taken in step 1 (this step fails, never gets to the point to select a new storage backend. Can't seem to find anything on why it fails reading the logs) 4.) Select new storage backend 5.) Decommission/cleanup legacy storage I have run into a few issues, mostly self-inflicted that have caused issues with upgrades, specifically using custom/external certificates for the management console instead of the default out of the box certificate set from initial install. This was done by the book, so to speak using the well documented approach on it. That is the only real customization that was done with the solution, though. This also caused issues with keycloak install/setup. As part of my continued troubleshooting with this, is there a way to revert the Apache certificates back to the internally setup/initially deployed SSL keys after the original ones have long expired? If anyone has any idea's that might help, I am open to that as well. Regards, Seann

2 1

vm only starts with a built in indtance template
by eevans＠digitaldatatechs.com 18 Oct '25

18 Oct '25

I have a 3 host ovirt hosts 4.5 and gluster 1o. The firewall is confiirured and SELinux enforcing. I have the same issue with selinux and firewall disabled. I cannot start a vm unless I use the preconfigured instance templates. You cannot add a network card or it fails. I honestly at a loss. Otherwise it works fine except for the scheduling does not balance with 12 vms. I am sure yoy are also aware sso is noit working and seems to be widespread. It looks like you can get a working one somewhere with out a red hat entitlement. It says it cannot fine remote executable in /usr/sbin. I can't find it any where and it comes with the cockpit-ws package whick is installed and double checked to make syre dependancies were covered. Any help or insight woiuld be appreciated Thanks for your time. Eric

1 1

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

15 Oct '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

2 1

Update CA on HostedEngine
by Denis L. 15 Oct '25

15 Oct '25

Hi there! I have two oVirt nodes and one HostedEngine (in VM). I need to refresh CA on engine. Before it im execute hosted-engine --set-maintenance --mode=global I begin it from engine-setup --offline My output was Engine database name : engine Engine database host : localhost Engine database port : 5432 Engine database host name validation : False Engine installation : True PKI organization : local Renew PKI : True DWH installation : True DWH database secured connection : False DWH database host : localhost DWH database user name : ovirt_engine_history DWH database name : ovirt_engine_history Backup DWH database : True DWH database port : 5432 DWH database host name validation : False Configure Image I/O Proxy : True Configure VMConsole Proxy : True Configure WebSocket Proxy : True Please confirm installation settings (OK, Cancel) [OK]: [ INFO ] Cleaning async tasks and compensations [ INFO ] Unlocking existing entities [ INFO ] Checking the Engine database consistency [ INFO ] Stage: Transaction setup [ INFO ] Stopping engine service [ INFO ] Stopping ovirt-fence-kdump-listener service [ INFO ] Stopping dwh service [ INFO ] Stopping Image I/O Proxy service [ INFO ] Stopping vmconsole-proxy service [ INFO ] Stopping websocket-proxy service [ INFO ] Stage: Misc configuration [ INFO ] Stage: Package installation [ INFO ] Stage: Misc configuration [ INFO ] Upgrading CA [ INFO ] Renewing CA [ INFO ] Renewing engine certificate [ INFO ] Renewing jboss certificate [ INFO ] Renewing websocket-proxy certificate [WARNING] Failed to read or parse '/etc/pki/ovirt-engine/keys/apache.p12' Perhaps it was changed since last Setup. Error was: Mac verify error: invalid password? [ INFO ] Renewing reports certificate [ INFO ] Renewing imageio-proxy certificate [ INFO ] Backing up database localhost:engine to '/var/lib/ovirt-engine/backups/engine-20251014234621.8qQq3R.dump'. [ INFO ] Creating/refreshing Engine database schema [ INFO ] Backing up database localhost:ovirt_engine_history to '/var/lib/ovirt-engine-dwh/backups/dwh-20251014234644.N8VIFY.dump'. [ INFO ] Creating/refreshing DWH database schema [ INFO ] Configuring Image I/O Proxy [ INFO ] Configuring WebSocket Proxy [ INFO ] Creating/refreshing Engine 'internal' domain database schema Unregistering existing client registration info. [ INFO ] Generating post install configuration file '/etc/ovirt-engine-setup.conf.d/20-setup-ovirt-post.conf' [ INFO ] Stage: Transaction commit [ INFO ] Stage: Closing up [ INFO ] Starting engine service [ INFO ] Starting dwh service [ INFO ] Restarting ovirt-vmconsole proxy service --== SUMMARY ==-- [ INFO ] Restarting httpd Web access is enabled at: http://ovirtengine.local:80/ovirt-engine https://ovirtengine.local:443/ovirt-engine Internal CA F3:93:46:1E:E5:8D:B6:55:0E:4D:52:9C:CF:03:2D:AB:80:DB:C0:E5 [WARNING] Internal CA was renewed, please refresh manually distributed copies SSH fingerprint: SHA256:hhhhhhhhhhhhhhhhhhhhhhhhhhh --== END OF SUMMARY ==-- [ INFO ] Stage: Clean up Log file is located at /var/log/ovirt-engine/setup/ovirt-engine-setup-20251014234414-b50wjo.log [ INFO ] Generating answer file '/var/lib/ovirt-engine/setup/answers/20251014234734-setup.conf' [ INFO ] Stage: Pre-termination [ INFO ] Stage: Termination [ INFO ] Execution of setup completed successfully I would please you to explain what should i do after that Warning ( please refresh manually distributed copies)? Running Enrol Certificate from web interface complete this process? Much thanks!

1 2

Installing oVirt on RHEL vs CentOS Stream, Alma or Rocky Linux
by Richard W.M. Jones 06 Oct '25

06 Oct '25

I'm still struggling to get oVirt installed. It absolutely will not install on RHEL 8, the documentation here is flat out wrong: https://www.ovirt.org/documentation/installing_ovirt_as_a_standalone_manage… javapackages-tools is not a module that exists in RHEL 8. Apparently it's a CentOS PowerTools module. Since original CentOS no longer really exists either, does anyone have any opinions or experience with installing oVirt on any of: - CentOS Stream 8 - Alma Linux 8.5 - Rocky Linux Alma in particular looks like a straight replacement for old CentOS. Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com virt-top is 'top' for virtual machines. Tiny program with many powerful monitoring features, net stats, disk stats, logging, etc. http://people.redhat.com/~rjones/virt-top

8 10

[ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Wait for the host to be up]
by Frederico Madeira 03 Oct '25

03 Oct '25

Hi Guys, I´m trying to setup a new installation of Ovirt 4.5.5 During the processe of deployment, it fail at this point: [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Wait for the host to be up] Analyzing logs, we have this loop: recovery: waiting for storage pool to go up return={'poollist': []} In deployment process, the playbook skips storage configuration: [root@servernode ~]# hosted-engine --deploy --4 [ INFO ] Etapa: Inicializando [ INFO ] Etapa: Configuração de ambiente Durante a personalização use CTRL-D para abortar. Continuing will configure this host for serving as hypervisor and will create a local VM with a running engine. The locally running engine will be used to configure a new storage domain and create a VM there. At the end the disk of the local VM will be moved to the shared storage. Are you sure you want to continue? (Sim, Não)[Sim]: Configuration files: Arquivo de log: /var/log/ovirt-hosted-engine-setup/ovirt-hosted-engine-setup-20251002121023-pzejjd.log Versão: otopi-1.10.4 (otopi-1.10.4-1.el9) [ INFO ] Etapa: Configuração dos pacotes de ambiente [ INFO ] Etapa: Detecção de programas [ INFO ] Etapa: Environment setup (late) [ INFO ] Etapa: Personalização do ambiente --== CONFIGURAÇÃO DO ARMAZENAMENTO ==-- --== HOST NETWORK CONFIGURATION ==-- Please indicate the gateway IP address [192.168.0.1]: Does anyone know what happening here ? How can I force playbook to ask for storage parameters ? thanks

1 0

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

02 Oct '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!

2 1