- Users - oVirt List Archives

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

16 Feb '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.

4 4

oVirt offline install
by Ethan Provensen 16 Feb '26

16 Feb '26

For the last 3-4 months, I have been trying to install oVirt on 3 bare metal servers with 1 SAN on an air-gapped network (no internet connection). I have failed with every attempt. I first determined what repositories I needed to upload to my air-gapped network to my Apache server, so the 3 bare metal servers could get the needed RPMs to install oVirt. I uploaded the following repositories from the internet: copr:copr.fedorainfracloud.org:ovirt:ovirt-master-snapshot ovirt-appliance-master-snapshot ovirt-master-centos-stream-ceph-pacific-testing ovirt-master-centos-stream-gluster10-testing ovirt-master-centos-stream-nfv-openvswitch2-testing ovirt-master-centos-stream-openstack-yoga-testing ovirt-master-centos-stream-opstools-collectd5-testing ovirt-master-centos-stream-ovirt45-testing ovirt-node-master-snapshot I first tried to install a oVirt self-hosted engine architecture on 1 server running Alma 9, but I ran into multiple dead ends with errors that I did not understand. My second attempt was to refresh the 1 Alma 9 server and install the oVirt CentOS9 node ISO instead on the 1 server. Again, I ran into multiple errors and did not understand the error messages. Recently, the oVirt Blog recommended we stopped using the oVirt CentOS9 node ISO for oVirt v4.5.7, so I went back on tried to install oVirt on Alma 9, and again I ran into multiple errors. I do not know what I am doing wrong. I have followed all the directions and Googled all the error messages I received, and still don't understand any of it. Now I am wondering if it's even possible to install oVirt on an server that doesn't have a DHCP connection to the internet. The last time I tried to create the "HostedEngineLocal" virtual machine on the server, I noticed the virtual machine creation relied on an internet connection and that is why the Hosted Engine setup failed everytime. Am I wrong? What am I doing wrong? Can someone help?

2 1

Unable to deploy hosted engine. It keeps stuck wait for the host to be up.
by dushyantk.sun＠gmail.com 15 Feb '26

15 Feb '26

I am trying to deploy hosted engine 4.5 on OL8.10. However it keeps getting stuck at step "wait for the host to be up." without any error. During this i found that vdsm service and related services went down. I am able to ssh into temp local hosted engine. But installation just stuck there. Nothing in ovirt-hosted-engine-setup logs.

1 0

Expanding blockSD volume
by Devin A. Bougie 12 Feb '26

12 Feb '26

What is the proper procedure for expanding the “blockSD” volume in our ovirt 4.5.6 cluster? We’ve started getting "No space left on device” errors when trying to clone a snapshot into a VM for backup purposes. Here’s the error: ——— VDSM lnxvirt06 command HSMGetAllTasksStatusesVDS failed: value=low level Image copy failed: ("Command ['/usr/bin/qemu-img', 'convert', '-p', '-t', 'none', '-T', 'none', '-f', 'qcow2', '-O', 'qcow2', '-o', 'compat=1.1', '/rhev/data-center/mnt/blockSD/86867486-e14e-4ff4-bf7c-1b0c94816032/images/211e91b0-2c72-45ad-90ca-badc63cb03f3/0a1b650f-8ab5-4eef-bee0-ea557c6eeb9f', '/rhev/data-center/mnt/blockSD/86867486-e14e-4ff4-bf7c-1b0c94816032/images/a2d4cef1-0342-41c0-85c2-e1b2ba6768b1/017e6d7e-4016-4108-8edc-188d8096a719'] failed with rc=1 out=b'' err=bytearray(b'qemu-img: error while writing at byte 3220937441280: No space left on device\\nqemu-img: Failed to flush the refcount block cache: No space left on device\\n')",) abortedcode=261 ——— And here’s what the host OS shows: ——— [root@lnxvirt06 ~]# df -h |grep rhev ovirtfs:/mnt/ovirtbackup 75T 36T 40T 47% /rhev/data-center/mnt/ovirtfs:_mnt_ovirtbackup /dev/mapper/86867486--e14e--4ff4--bf7c--1b0c94816032-master 975M 84K 924M 1% /rhev/data-center/mnt/blockSD/86867486-e14e-4ff4-bf7c-1b0c94816032/master ——— Please let me know if there’s any more information I can provide. Many thanks, Devin

1 0

hci setup with replica3 but one brick is not used
by Jiri Slezka 10 Feb '26

10 Feb '26

Hi, I am using distributed-replicated volume for vm's storage. There are 3 bricks (mounts on separate disks) in each of 3 hosts, so topology is 3x3 Volume Name: vms Type: Distributed-Replicate Volume ID: 52032ec6-99d4-4210-8fb8-ffbd7a1e0bf7 Status: Started Snapshot Count: 0 Number of Bricks: 3 x 3 = 9 Transport-type: tcp Bricks: Brick1: 10.0.4.11:/gluster_bricks/vms/vms Brick2: 10.0.4.13:/gluster_bricks/vms/vms Brick3: 10.0.4.12:/gluster_bricks/vms/vms Brick4: 10.0.4.11:/gluster_bricks/vms2/vms2 Brick5: 10.0.4.13:/gluster_bricks/vms2/vms2 Brick6: 10.0.4.12:/gluster_bricks/vms2/vms2 Brick7: 10.0.4.11:/gluster_bricks/vms3/vms3 Brick8: 10.0.4.12:/gluster_bricks/vms3/vms3 Brick9: 10.0.4.13:/gluster_bricks/vms3/vms3 I can see that bricks vms and vms2 are used but vms3 is almost (256MB vs hundreds of GBs) empty. In the fact I added vms3 bricks later and did not mention it because free volume space was reported (as I believed) correctly. Today I added one vm with 400GB disk and creating of disk failed because "OSError: [Errno 28] No space left on device". Now vms and vms2 bricks are full but vms volume has (should have) 914GiB of free space. I cannot see nothing interesting in glusterfs logs, glusterfs volume info and status looks good. There are errors in engine and vdsm logs but as can I see, it is just because of lack of space (vdsm side) and because image creation failed (engine side) Also as side effect, vms volume is full and disk from that new vm is locked (I would like to delete it). Any ideas what can be wrong or where to look and how to debug? Thanks in advance, Jiri

1 2

Hosted Engine Deployment timeout waiting for VM
by Jonas Liechti 09 Feb '26

09 Feb '26

Hello users, I am currently trying to deploy the self-hosted engine via the web interface but it seems stuck at the task "Wait for the local VM" (https://github.com/oVirt/ovirt-ansible-collection/blob/master/roles/hosted_…) I am unsure what to look at for getting more info as I haven't worked a lot with Ansible before. Do you have any idea how to debug? The temporary IP is added to /etc/hosts and I can also login to the VM via SSH: [root@server-005 ~]# cat /etc/hosts 192.168.1.97 ovirt-engine-test.admin.int.rabe.ch # temporary entry added by hosted-engine-setup for the bootstrap VM 127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4 ::1 localhost localhost.localdomain localhost6 localhost6.localdomain6 10.128.16.5 server-005.admin.int.rabe.ch 10.128.16.6 server-006.admin.int.rabe.ch 10.128.16.7 server-007.admin.int.rabe.ch #10.128.32.2 ovirt-engine-test.admin.int.rabe.ch 10.132.16.5 server-005.storage.int.rabe.ch 10.132.16.6 server-006.storage.int.rabe.ch 10.132.16.7 server-007.storage.int.rabe.ch [root@server-005 ~]# ssh ovirt-engine-test.admin.int.rabe.ch root(a)ovirt-engine-test.admin.int.rabe.ch's password: Web console: https://ovirt-engine-test.admin.int.rabe.ch:9090/ or https://192.168.1.97:9090/ Last login: Mon Apr 18 11:33:53 2022 from 192.168.1.1 [root@ovirt-engine-test ~]# ip a 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000 link/ether 00:16:3e:58:7a:a3 brd ff:ff:ff:ff:ff:ff inet 192.168.1.97/24 brd 192.168.1.255 scope global dynamic noprefixroute eth0 valid_lft 2313sec preferred_lft 2313sec inet6 fe80::216:3eff:fe58:7aa3/64 scope link valid_lft forever preferred_lft forever Thank you for any tips for debugging. Jonas

5 7

Odd behavior of VMs in Cluster
by dan.midthun＠gmail.com 08 Feb '26

08 Feb '26

I recently have had some odd / inconsistent behaviors with VMs that I am completely baffled by: packets being dropped for no apparent reason. This possibly started around 1/1/2026. I started having issues with maintaining connectivity to [vm2], and then more VMs on the cluster (specifically the engine!, then others) No sense. No config changes. No hardware changes. _NO_ changes. 2 vms, same host, same network, same storage, same configuration. ping google, vm1: 0% packet loss vm2: n% packet loss migrate host for vm2, no change. still packet loss. migrate host for vm1, no change, NO packet loss. mind you, these are clones. literally. the only difference is in configured IP address. I've been doing IT for the last 30 years, and I have NEVER seen anything like this. So, decided maybe update the hosts. (ikd ... why not)..... long story short, I am on Node 4.5.5 (was previously, too) now engine 4.5.7; still the same problem. What information is needed for someone to help me troubleshoot this issue

1 0

Upgrade to latest version
by Andrea Chierici 06 Feb '26

06 Feb '26

Hi, I am trying to update my old 4.5.5 system to the latest one, right now with no luck: I am writing to share some experience and hopefully to be pointed to the correct process. My system runs entirely on centos8, version is 4.5.5-1.el8, engine is on a vm hosted on vmware, no self hosted engine. The idea is to install a new engine vm, with almalinux10, import the backup taken from the old engine, and restore the system. After that I would upgrade all the hosts, one at a time. I tried today the first time, unsuccesfully. Here are all the steps: 1. take the almalinux10 vm, install the ovirt software with these commands: dnf copr enable -y ovirt/ovirt-master-snapshot rhel-10-x86_64 dnf install -y ovirt-release-master epel-release dnf install -y ovirt-engine Operation ended succesfully 2. import the backup taken from current 4.5.5 engine: engine-backup --mode=restore --scope=all --file=/backup.tar.gz --log=/tmp/restore.log --restore-permissions Operation ended successfully 3. Run engine-setup, here is the output (removed fqdn for privacy): --== CONFIGURATION PREVIEW ==-- Host FQDN : xxxxxxx.yyy.it Firewall manager : firewalld Update Firewall : True Set up Cinderlib integration : False Engine database host : localhost Engine database port : 5432 Engine database secured connection : False Engine database host name validation : False Engine database name : engine Engine database user name : engine Engine installation : True PKI organization : yyy.it Set up ovirt-provider-ovn : True DWH installation : True DWH database host : localhost DWH database port : 5432 DWH database secured connection : False DWH database host name validation : False DWH database name : ovirt_engine_history DWH database user name : ovirt_engine_history Backup DWH database : False Grafana integration : True Grafana database user name : ovirt_engine_history_grafana 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 ] DNF Repository copr:copr.fedorainfracloud.org:ovirt:ovirt-master-snapshot is listed more than once in the configuration [ INFO ] Stopping engine service [ INFO ] Stopping ovirt-fence-kdump-listener service [ INFO ] Stopping dwh service [ INFO ] Stopping vmconsole-proxy service [ INFO ] Stopping websocket-proxy service [ INFO ] Stage: Misc configuration (early) [ INFO ] Stage: Package installation [ INFO ] Stage: Misc configuration [ INFO ] Upgrading CA [ INFO ] Configuring WebSocket Proxy [ INFO ] Backing up database localhost:engine to '/var/lib/ovirt-engine/backups/engine-20260127180343.q9xj84af.dump'. [ INFO ] Creating/refreshing Engine database schema [ INFO ] Creating/refreshing DWH database schema [ INFO ] Updating OVN SSL configuration [ INFO ] Updating OVN timeout configuration [ INFO ] Creating/refreshing Engine 'internal' domain database schema Unregistering existing client registration info. Updating the engine FQDN in the Data Warehouse Database. [ 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 --== SUMMARY ==-- [ INFO ] Starting dwh service [ INFO ] Starting Grafana service [ ERROR ] Failed to execute stage 'Closing up': Failed to start service 'grafana-server' [ INFO ] Stage: Clean up Log file is located at /var/log/ovirt-engine/setup/ovirt-engine-setup-20260127180313-lps532.log [ INFO ] Generating answer file '/var/lib/ovirt-engine/setup/answers/20260127180410-setup.conf' [ INFO ] Stage: Pre-termination [ INFO ] Stage: Termination [ ERROR ] Execution of setup failed The log provided is so verbose that I can't spot the possible problem. I wonder, anyway, if this procedure is correct or whether I should do something different. For example I noticed that I am not asked to configure keycloak, since in the current production system I have freeipa. Thanks for the possible help, Andrea -- Andrea Chierici - INFN-CNAF Viale Berti Pichat 6/2, 40127 BOLOGNA Office Tel: +39 051 2095463 --

3 2

Q: VM Stuck in Powering Down Status
by Andrei Verovski 06 Feb '26

06 Feb '26

Hi, I have 1 VM which stuck in my ”Powering Down” status. This is what I did before in similar situations before: engine=# select vm_guid from vm_static where vm_name=‘My_VM-Active'; vm_guid -------------------------------------- f4e44168-92e2-40ec-a04e-c374ba2ef9b8 (1 row) engine=# select status from vm_dynamic where vm_guid='f4e44168-92e2-40ec-a04e-c374ba2ef9b8'; status -------- 16 (1 row) engine=# update vm_dynamic SET status=0 where vm_guid='f4e44168-92e2-40ec-a04e-c374ba2ef9b8'; UPDATE 1 engine=# update vm_dynamic SET run_on_vds=null WHERE vm_guid='f4e44168-92e2-40ec-a04e-c374ba2ef9b8'; UPDATE 1 But now this receipt doesn’t work. Running again engine=# select status from vm_dynamic where vm_guid='f4e44168-92e2-40ec-a04e-c374ba2ef9b8'; status -------- 16 (1 row) shows status didn’t changed. How to fix this ? Thanks in advance. Andrei

1 0

VM Template Reuse Between Clusters
by lmd＠gto.net 28 Jan '26

28 Jan '26

Good Morning! I recently added a second cluster to an oVirt environment and I am looking to re-use a number of templates between the clusters while providing self-service to users through the VM Portal. I would like to describe what I am seeing and ask whether you might know of what I am missing - or if you could share your experience. For sake of discussion, let us call the clusters "CORE" and "PROD" (the new cluster) and the template "UbuntuServer24". The template was created in cluster CORE against Storage Domain "CORE1". The template is visible to all users (role "UserTemplateBasedVm" for Everyone). CORE and PROD clusters contain the same networks and the hosts mount the same Storage Domains though, by policy, PROD cluster users are restricted to creating Disks only on Storage Domain "PROD1" through roles/permissions. User JDOE is a PROD cluster user, has VM Portal/"User role" rights to the cluster and Storage Domain and is able to deploy and manage VMs in Cluster PROD. JDOE is not intended to have any permissions against Cluster CORE. JDOE has temporary Admin Portal rights but I would prefer they operate through VM Portal at all times. Here is what I am seeing: Using the Administrator Portal, JDOE can deploy template UbuntuServer24 in PROD without any trouble. Using the VM Portal, using "Create Virtual Machine", JDOE does not see the "UbuntuServer24" template in the list of available templates. It appears to be filtered out of the list. Based on research so far, I can create a second copy of the template (ex: deploy a VM and capture a template in cluster PROD) as different name "UbuntuServer24-PROD". With no other changes, user JDOE can successfully deploy this new template into cluster PROD via VM Portal. I think this proves JDOE permissions and roles are in good shape. For testing I have also temporarily added equivalent permissions for JDOE against Cluster CORE and can confirm that the "UbuntuServer24" is only displayed as a Template when cluster "CORE" is selected as the target for the new VM in the "Create Virtual Machine" flow. The duplicated template approach does work but it means that there are two templates to offer the same result in each of the two clusters. I am concerned that this leaves an opportunity for de-sync, some additional storage consumption, and an enforced requirement for a different template name (string) which complicates user-facing documentation. Ideally I would like to maintain a single template to keep things simple and make it easy for other team members to use and maintain the environment. I tried to find a reference to my query in the docs as well as web search but didn't come up with something I was confident was on the right path. Is there a way to reuse templates between clusters in this manner and, if so, could you kindly please point me in the right direction? Thank you very much for any advice you may have, Dan Galway

1 0