June 2022 - Users - oVirt List Archives

Install Ovirt 4.5.1 on Centos Stream 8.6
by moula.badji＠gmail.com 28 Jun '22

28 Jun '22

Hello, I'm trying to install ovirt-engine on centos Stream 8.6 and it's still not possible due to outdated dependencies. ovirt-engine-keycloak ovirt-engine-keycloak-setup mod_auth_openidc Thank's. Moula.

2 2

Regarding oVirt VM Hosting
by Nishith Vyas 27 Jun '22

27 Jun '22

Dear Users, I've initiated this mail communication for the very first time. Recently, I've started using *oVirt-Engine* & *oVirt-Node* in my lab as I want to host a openstack kind of infrastructure hosting environment for my company. Prior to that, I'd like to get information on the below listed statement. ---------------------------------------------------------------------------------- I've created data domain, iso domain & export domain over the NFS. Now, my VM is created by loading CentOS 7.9 ISO from "iso domain" & storing "VM" data on "data domain". Here, I'm just curious to know about the NFS efficiency to manage VMs because the OS boots/loads from remote "NFS Data Domain", not from the local storage (i.e. oVirt-Node) Which is more efficient? NFS or iSCSI for VM Hosting? ----------------------------------------------------------------------------------- Regards, *Nishit**h **N. Vyas* *Ca**l**l:** +91 98**79597301* *https://www.linkedin.com/in/nishithvyas <https://www.linkedin.com/in/nishithvyas>* *Tha**nk** you for not printing this email! Save trees & Go Green!*

1 0

oVirt Survey Summer 2022
by Sandro Bonazzola 27 Jun '22

27 Jun '22

oVirt Survey Summer 2022 As we continue to develop oVirt 4.5, the oVirt community would value insights on your experience with the oVirt project. Please help us to hit the mark by completing this short survey: https://forms.gle/2LxoDKb7njEQwr4f7 . Survey will close on July 29th 2022. Please note the answers to this survey will be publicly accessible. This survey is under oVirt Privacy Policy available at https://ovirt.org/privacy-policy.html . -- Sandro Bonazzola MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://www.redhat.com/> *Red Hat respects your work life balance. Therefore there is no need to answer this email out of your office hours.*

1 0

VMs missing following Import of Storage Domain
by simon＠justconnect.ie 27 Jun '22

27 Jun '22

Hi All, I have 2 oVirt 3 node Clusters in 2 Datacenters - effectively 2 independent environements with stretched VLANs for DR purposes. Each volume is geo replicated to the other datacenter. Each volume is a separate Storage Domain. In a DR event the geo-replicated volumes/Storage Domains are imported in the other Datacenter and the VMs imported once it's attached. The issue I am seeing is that some of the VMs are not listed when I click 'VM Import' from the imported Storage Domain. The disks for those missing VMs however, do exist in 'Disk Import' Tab of the imported Storage Domain. Prior to importing the Storage Domain in Site B, all VM disks were migrated to a single Storage Domain in Site A and geo-replication allowed to sync. Kind Regards Simon...

3 7

VM hangs after migration
by Giorgio Biacchi 26 Jun '22

26 Jun '22

Hi, I have a fresh Ovirt installation (4.4.10.7-1.el8 engine and oVirt Node 4.4.10) on a Dell VRTX chassis. There are 3 blades, two of them are identical hardware (PowerEdge M630) and the third is a little newer (PowerEdge M640). The third has different CPUs, more RAM, and slower NICs. I also have a bunch of data domains some on the shared PERC internal storage and others on an external iSCSI storage, all seems configured correctly and all the hosts are operational. I can migrate a VM back and forth from the first two blades without any problem, I can migrate a VM to the third blade but when I migrate a VM from the third blade to any of the other two the task terminate successfully, the VM is marked as up on the target host but the VM hangs, the console is frozen and the VM stops to respond to ping. I have no clues about why this is happening and I'm looking for suggestions about how to debug and hopefully fix this issue. Thanks in advance -- gb PGP Key: http://pgp.mit.edu/ Primary key fingerprint: C510 0765 943E EBED A4F2 69D3 16CC DC90 B9CB 0F34

3 2

Re: Failed to Start services ovirt-imageio
by Nir Soffer 26 Jun '22

26 Jun '22

On Fri, Jun 24, 2022 at 1:33 AM АБИОЛА А. Э <abiolaemma01(a)gmail.com> wrote: > > Hello Nir, Hi АБИОЛА, you forgot to reply to users(a)ovirt.org. Please always reply to the mailing list so the discussion is public. > I am so grateful for your reply and helpful information. I have successfully deployed the Ovirt engine and it is up and running fine, but now I am having another issue uploading .ISO files to disk. I tried to upload .iso files but the status was "Paused by the system" and was waiting 15 hours for the status to change but still no changes, i tried to delete the .ISO file but i can't remove at all, its status was "Finalizing cleaning up" i waited 20 hours for the status to change but with no success. Kindly guard me through the process to fix this errors, so I can upload .ISO files to the Disk to launch the VM successfully. Please see below picture for the error. When the system pauses an upload, you can cancel the upload from the upload menu: Storage > Disks > Upload > Cancel This will delete the new disk and end the image transfer. To understand why the system paused the transfer, please share more info: - Which oVirt version are you running? - Did you add the engine CA certificate to the browser? You can check if the browser is configured correctly by opening an upload dialog: Storage > Disks > Upload > Start and clicking the "Test Connection" button. If this fails, you need to add the engine CA to the browser. When "Test Connection" is successful, try to upload again. If the upload fails again, please share logs showing the timeframe of this error: - engine log from /var/log/ovirt-engine/engine.log - vdsm log from the host performing the upload (see the events tag in engine UI) from /var/log/vdsm/vdsm.log - ovirt-imageio log from the host performing the upload from /var/log/ovirt-imageio/daemon.log Nir > > I will be glad to read from you soon. > > Appreciated > > > On Tue, Jun 21, 2022 at 3:19 PM Nir Soffer <nsoffer(a)redhat.com> wrote: >> >> On Tue, Jun 21, 2022 at 8:18 AM АБИОЛА А. Э <abiolaemma01(a)gmail.com> wrote: >> > >> > Hello Sir, >> > I am new to Ovirt and I tried to deploy it 3weeks into my oracle linux with no success. >> > I got the following error messages >> > Please how can i fix this error to successfully deploy it. >> > I will be glad to read from you soon. >> > Appreciated >> > AAE. >> >> Which oVirt version is this? >> >> You can try to check: >> >> systemctl status ovirt-imageio >> >> It usually show the latest logs which may help to understand why the >> service could not start. >> >> What do you have in /var/log/ovirt-imageio/daemon.log? >> >> Nir >>

1 0

can not access engine when hosted engine is up
by adam_xu＠adagene.com.cn 25 Jun '22

25 Jun '22

Hi ovirt list, I need help. I ran “dnf update” on my engine and reboot it. Then I lost connection of the engine. When I access one of my host web management https://ovirthost1:9090, I saw engine status is “Hosted Engine is up!”, but another host of the cluster is in down status. How can I bring up my engine since it is “UP” now. �

2 9

ovirt 4.5 default username
by adam_xu＠adagene.com.cn 25 Jun '22

25 Jun '22

Hi all, I just setup a new ovirt 4.5 cluster for testing purpose. It was successful. But I can’t login using my password. Is there any changes between 4.4 and 4.5?

1 1

API how to increase extend resize disk VM
by ovirt.org＠nevim.eu 25 Jun '22

25 Jun '22

Hello, please how to increase extend resize disk of VM? I can working with ansible or REST API. Ansible working is here, but i not found manual for update size: https://docs.ansible.com/ansible/2.3/ovirt_disks_module.html On official ovirt documentation i cant found how to update. I found only old manual in KB page, but not working on lastest: https://www.ovirt.org/develop/release-management/features/storage/online-vi… PUT /api/vms/{VM_ID}/disks/{DISK_ID} HTTP/1.1 Accept: application/xml Content-type: application/xml <disk> <size>{NEW_SIZE_IN_BYTES}</size> </disk> Thanks for advice.

5 13

Re: [External]: Re: Need to transfer a VM from oVirt to vSphere
by Gianluca Cecchi 24 Jun '22

24 Jun '22

On Fri, Jun 24, 2022 at 4:38 PM David M. Hornsby <dmhornsby(a)mueller1875.com> wrote: > I have done this before quite a few times. What I did was: > > > 1. Export the qcow2 or raw file and convert it: qemu-img convert -f > qcow2 -O vmdk > 2. Import the vmdk into vsphere storage and convert it to thin with > vmkfstools > 3. Then create the vm definition. > 4. There will be some minor driver and ethernet type stuff to fix. > > This process has worked everytime. You probably could use a tool like virt > v2v or veeam to accomplish this as well. > > David > > Thanks David, I didn't see your e-mail while I was writing my answer. I confirm I went a similar way (but passing anyway from OVA and then extracting the disk...) Gianluca

1 0

Need to transfer a VM from oVirt to vSphere
by Gianluca Cecchi 24 Jun '22

24 Jun '22

Hello, I need to transfer a VM from oVirt 4.4 to vSphere. I see that the "Export as OVA" in the GUI exports in a format compatible with oVirt but not vSphere. Any hint? Any way to easily convert the oVirt generated OVA to a vSPhere compatible one? Thanks, Gianluca

3 3

HCI Upgrade 4.4 to 4.5 Gluster 10
by simon＠justconnect.ie 24 Jun '22

24 Jun '22

Hi All, When Upgrading ovirt 4.4 to 4.5 when using GlusterFS, should Gluster be upgraded manually before the nodes are upgraded? Simon...

2 7

Unable to ugprade cluster level to 4.7 for the hosted engine (only)
by lists＠pequod.io 24 Jun '22

24 Jun '22

Hello, i upgraded my engine and nodes to 4.5 a few days ago and now planning to upgrade the cluster level compatibility from 4.6 to 4.7. First i tried doing this from the cluster settings, but it fails because hosted-engine settings are locked. So i tried it by hand but again got the locked error, i found i cant change any values on the hosted engine. Changing compatiblity level on all other VMs worked fine and there are on 4.7 now. I read about the timezone issue in 4.4.8, so i checked the timezone of my hosted engine it is filled with "Standard: (GMTZ) Greenwhich Standard Time". To be sure, i just did a "/usr/share/ovirt-engine/dbscripts/engine-psql.sh -c "update vm_static SET time_zone='Etc/GMT' where vm_name='HostedEngine';"" and it changed the timezone, but settings are still locked and i am unable to change the compatibility level. Any idea how to solve this?

4 6

oVirt Node 4.5.1
by Lev Veyde 23 Jun '22

23 Jun '22

On June 23rd 2022 the oVirt project released an update of oVirt Node (4.5.1) delivering several security fixes, bug fixes and enhancements. The update is already available on resources.ovirt.org and should land on oVirt mirrors within 24 hours. With oVirt 4.5.1 oVirt Node based on CentOS Stream 9 is also available as a tech preview. Known issues: - On oVirt Node based on CentOS Stream 9 with UEFI secure boot, vdsm fails to decode DMI data due to Bug 2081648 <https://bugzilla.redhat.com/show_bug.cgi?id=2081648> – python-dmidecode module fails to decode DMI data Updates on el8 based oVirt Node: Security fixes: - Important - Bug 2082616 <https://bugzilla.redhat.com/show_bug.cgi?id=2082616> - CVE-2022-24903 - rsyslog: Heap-based overflow in TCP syslog server - Important - Bug 2072376 <https://bugzilla.redhat.com/show_bug.cgi?id=2072376> - CVE-2018-25032 - zlib: A flaw in zlib-1.2.11 when compressing (not decompressing!) certain inputs. - Important - Bug 2065568 <https://bugzilla.redhat.com/show_bug.cgi?id=2065568> - CVE-2022-27666 - kernel: buffer overflow in IPsec ESP transformation code Other updates: - CentOS Stream 8 latest updates - Full list of changes compared to oVirt Node 4.5.0.3: oVirt Node 4.5.0.3 oVirt Node 4.5.1 NetworkManager 1.39.3-1.el8 1.39.5-1.el8 NetworkManager-config-server 1.39.3-1.el8 1.39.5-1.el8 NetworkManager-libnm 1.39.3-1.el8 1.39.5-1.el8 NetworkManager-ovs 1.39.3-1.el8 1.39.5-1.el8 NetworkManager-team 1.39.3-1.el8 1.39.5-1.el8 NetworkManager-tui 1.39.3-1.el8 1.39.5-1.el8 binutils 2.30-114.el8 2.30-116.el8 centos-release-ovirt45 8.7-1.el8s 8.7-2.el8s cockpit 264.1-1.el8 270-1.el8 cockpit-bridge 264.1-1.el8 270-1.el8 cockpit-storaged 264.1-1.el8 269-1.el8 cockpit-system 264.1-1.el8 270-1.el8 cockpit-ws 264.1-1.el8 270-1.el8 cronie 1.5.2-6.el8 1.5.2-7.el8 cronie-anacron 1.5.2-6.el8 1.5.2-7.el8 cups-libs 2.2.6-45.el8 device-mapper-multipath 0.8.4-23.el8 0.8.4-25.el8 device-mapper-multipath-libs 0.8.4-23.el8 0.8.4-25.el8 dnf 4.7.0-9.el8 4.7.0-10.el8 dnf-data 4.7.0-9.el8 4.7.0-10.el8 dracut 049-201.git20220131.el8 049-202.git20220511.el8 dracut-config-generic 049-201.git20220131.el8 049-202.git20220511.el8 dracut-live 049-201.git20220131.el8 049-202.git20220511.el8 dracut-network 049-201.git20220131.el8 049-202.git20220511.el8 dracut-squash 049-201.git20220131.el8 049-202.git20220511.el8 e2fsprogs 1.45.6-4.el8 1.45.6-5.el8 e2fsprogs-libs 1.45.6-4.el8 1.45.6-5.el8 elfutils-default-yama-scope 0.186-1.el8 0.187-4.el8 elfutils-libelf 0.186-1.el8 0.187-4.el8 elfutils-libs 0.186-1.el8 0.187-4.el8 fence-agents-all 4.2.1-94.el8 4.2.1-97.el8 fence-agents-amt-ws 4.2.1-94.el8 4.2.1-97.el8 fence-agents-apc 4.2.1-94.el8 4.2.1-97.el8 fence-agents-apc-snmp 4.2.1-94.el8 4.2.1-97.el8 fence-agents-bladecenter 4.2.1-94.el8 4.2.1-97.el8 fence-agents-brocade 4.2.1-94.el8 4.2.1-97.el8 fence-agents-cisco-mds 4.2.1-94.el8 4.2.1-97.el8 fence-agents-cisco-ucs 4.2.1-94.el8 4.2.1-97.el8 fence-agents-common 4.2.1-94.el8 4.2.1-97.el8 fence-agents-compute 4.2.1-94.el8 4.2.1-97.el8 fence-agents-drac5 4.2.1-94.el8 4.2.1-97.el8 fence-agents-eaton-snmp 4.2.1-94.el8 4.2.1-97.el8 fence-agents-emerson 4.2.1-94.el8 4.2.1-97.el8 fence-agents-eps 4.2.1-94.el8 4.2.1-97.el8 fence-agents-heuristics-ping 4.2.1-94.el8 4.2.1-97.el8 fence-agents-hpblade 4.2.1-94.el8 4.2.1-97.el8 fence-agents-ibmblade 4.2.1-94.el8 4.2.1-97.el8 fence-agents-ifmib 4.2.1-94.el8 4.2.1-97.el8 fence-agents-ilo-moonshot 4.2.1-94.el8 4.2.1-97.el8 fence-agents-ilo-mp 4.2.1-94.el8 4.2.1-97.el8 fence-agents-ilo-ssh 4.2.1-94.el8 4.2.1-97.el8 fence-agents-ilo2 4.2.1-94.el8 4.2.1-97.el8 fence-agents-intelmodular 4.2.1-94.el8 4.2.1-97.el8 fence-agents-ipdu 4.2.1-94.el8 4.2.1-97.el8 fence-agents-ipmilan 4.2.1-94.el8 4.2.1-97.el8 fence-agents-kdump 4.2.1-94.el8 4.2.1-97.el8 fence-agents-mpath 4.2.1-94.el8 4.2.1-97.el8 fence-agents-redfish 4.2.1-94.el8 4.2.1-97.el8 fence-agents-rhevm 4.2.1-94.el8 4.2.1-97.el8 fence-agents-rsa 4.2.1-94.el8 4.2.1-97.el8 fence-agents-rsb 4.2.1-94.el8 4.2.1-97.el8 fence-agents-sbd 4.2.1-94.el8 4.2.1-97.el8 fence-agents-scsi 4.2.1-94.el8 4.2.1-97.el8 fence-agents-vmware-rest 4.2.1-94.el8 4.2.1-97.el8 fence-agents-vmware-soap 4.2.1-94.el8 4.2.1-97.el8 fence-agents-wti 4.2.1-94.el8 4.2.1-97.el8 glibc 2.28-200.el8 2.28-203.el8 glibc-common 2.28-200.el8 2.28-203.el8 glibc-langpack-en 2.28-200.el8 2.28-203.el8 kernel 4.18.0-383.el8 4.18.0-394.el8 kernel-core 4.18.0-383.el8 4.18.0-394.el8 kernel-modules 4.18.0-383.el8 4.18.0-394.el8 kernel-tools 4.18.0-383.el8 4.18.0-394.el8 kernel-tools-libs 4.18.0-383.el8 4.18.0-394.el8 kexec-tools 2.0.24-1.el8 2.0.24-2.el8 kpartx 0.8.4-23.el8 0.8.4-25.el8 libbasicobjects 0.1.1-39.el8 0.1.1-40.el8 libcap 2.48-2.el8 2.48-4.el8 libcollection 0.7.0-39.el8 0.7.0-40.el8 libcom_err 1.45.6-4.el8 1.45.6-5.el8 libdhash 0.5.0-39.el8 0.5.0-40.el8 libini_config 1.3.1-39.el8 1.3.1-40.el8 libldb 2.4.1-1.el8 2.5.0-1.el8 libpath_utils 0.2.1-39.el8 0.2.1-40.el8 libref_array 0.1.5-39.el8 0.1.5-40.el8 libss 1.45.6-4.el8 1.45.6-5.el8 libtdb 1.4.4-1.el8 1.4.6-1.el8 libtevent 0.11.0-0.el8 0.12.0-0.el8 libwbclient 4.15.5-8.el8 4.16.1-0.el8 mesa-dri-drivers 21.3.4-1.el8 21.3.4-1.0.1.el8 mesa-filesystem 21.3.4-1.el8 21.3.4-1.0.1.el8 mesa-libEGL 21.3.4-1.el8 21.3.4-1.0.1.el8 mesa-libGL 21.3.4-1.el8 21.3.4-1.0.1.el8 mesa-libgbm 21.3.4-1.el8 21.3.4-1.0.1.el8 mesa-libglapi 21.3.4-1.el8 21.3.4-1.0.1.el8 nmap-ncat 7.70-6.el8 7.70-7.el8 openvswitch-selinux-extra-policy 1.0-28.el8 1.0-29.el8s osinfo-db 20211216-1.el8 20220516-1.el8 ovirt-ansible-collection 2.0.3-1.el8 2.1.0-1.el8 ovirt-hosted-engine-setup 2.6.3-1.el8 2.6.4-1.el8 ovirt-imageio-client 2.4.3-1.el8 2.4.5-1.el8 ovirt-imageio-common 2.4.3-1.el8 2.4.5-1.el8 ovirt-imageio-daemon 2.4.3-1.el8 2.4.5-1.el8 ovirt-node-ng-image-update-placeholder 4.5.0.3-1.el8 4.5.1-1.el8 ovirt-release-host-node 4.5.0.3-1.el8 4.5.1-1.el8 pacemaker-cluster-libs 2.1.2-4.el8 2.1.3-1.el8 pacemaker-libs 2.1.2-4.el8 2.1.3-1.el8 pacemaker-schemas 2.1.2-4.el8 2.1.3-1.el8 pam 1.3.1-16.el8 1.3.1-20.el8 python3-dnf 4.7.0-9.el8 4.7.0-10.el8 python3-perf 4.18.0-383.el8 4.18.0-394.el8 python38-ovirt-imageio-client 2.4.3-1.el8 2.4.5-1.el8 python38-ovirt-imageio-common 2.4.3-1.el8 2.4.5-1.el8 rpcbind 1.2.5-8.el8 1.2.5-9.el8 rsyslog 8.2102.0-9.el8 8.2102.0-10.el8 rsyslog-elasticsearch 8.2102.0-9.el8 8.2102.0-10.el8 rsyslog-mmjsonparse 8.2102.0-9.el8 8.2102.0-10.el8 rsyslog-mmnormalize 8.2102.0-9.el8 8.2102.0-10.el8 rsyslog-openssl 8.2102.0-9.el8 8.2102.0-10.el8 samba-client-libs 4.15.5-8.el8 4.16.1-0.el8 samba-common 4.15.5-8.el8 4.16.1-0.el8 samba-common-libs 4.15.5-8.el8 4.16.1-0.el8 scap-security-guide 0.1.60-7.el8 0.1.60-9.el8 selinux-policy 3.14.3-98.el8 3.14.3-99.el8 selinux-policy-targeted 3.14.3-98.el8 3.14.3-99.el8 sos 4.2-15.el8 4.3-1.el8 vdsm 4.50.0.13-1.el8 4.50.1.4-1.el8 vdsm-api 4.50.0.13-1.el8 4.50.1.4-1.el8 vdsm-client 4.50.0.13-1.el8 4.50.1.4-1.el8 vdsm-common 4.50.0.13-1.el8 4.50.1.4-1.el8 vdsm-gluster 4.50.0.13-1.el8 4.50.1.4-1.el8 vdsm-http 4.50.0.13-1.el8 4.50.1.4-1.el8 vdsm-jsonrpc 4.50.0.13-1.el8 4.50.1.4-1.el8 vdsm-network 4.50.0.13-1.el8 4.50.1.4-1.el8 vdsm-python 4.50.0.13-1.el8 4.50.1.4-1.el8 vdsm-yajsonrpc 4.50.0.13-1.el8 4.50.1.4-1.el8 yum 4.7.0-9.el8 4.7.0-10.el8 zlib 1.2.11-17.el8 1.2.11-19.el8 Additional resources: - Read more about the oVirt 4.5.1 release highlights: https://www.ovirt.org/release/4.5.1/ - Get more oVirt project updates on Twitter: https://twitter.com/ovirt - Check out the latest project news on the oVirt blog: https://blogs.ovirt.org/ Thanks in advance, -- Lev Veyde Senior Software Engineer, RHCE | RHCVA | MCITP Red Hat Israel <https://www.redhat.com> lev(a)redhat.com | lveyde(a)redhat.com <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>

1 0

import vm disk image on ISCSI Data Domain
by sultanu＠inbox.ru 23 Jun '22

23 Jun '22

Hello, all Maybe somebody have experiance. I have cluster 3 hosts + ISCSI storage as Data Domain. How can i upload vm image from my old ovirt (baremetal with local storage) to my new cluster from CLI, NOT from WEB UI? Dowload on my local computer and post from WEB UI it take long period of time. Thak you for your time.

1 0

Lost space in /var/log
by Andrei Verovski 22 Jun '22

22 Jun '22

Hi ! I have strange situation with low disk space on /var/log/, yet I can't figure out what have consumed so much space. Look at the du output. Thanks in advance for any suggestion(s). # df -h Filesystem Size Used Avail Use% Mounted on /dev/mapper/centos-var 15G 1.3G 13G 9% /var /dev/mapper/centos-var_log 7.8G 7.1G 293M 97% /var/log /dev/mapper/centos-var_log_audit 2.0G 41M 1.8G 3% /var/log/audit # # du -ah /var/log | sort -n -r | head -n 20 664K /var/log/vdsm 660K /var/log/vdsm/vdsm.log 624K /var/log/gdm 580K /var/log/anaconda/storage.log 480K /var/log/anaconda/packaging.log 380K /var/log/gdm/:0.log.4 316K /var/log/anaconda/syslog 276K /var/log/tuned 252K /var/log/libvirt/qemu/NextCloud-Collabora-LVM.log-20210806 220K /var/log/Xorg.0.log 168K /var/log/gdm/:0.log 156K /var/log/yum.log-20191117 156K /var/log/secure-20180726 132K /var/log/libvirt/qemu/NextCloud-Collabora-Active.log 128K /var/log/anaconda/anaconda.log 120K /var/log/hp-snmp-agents 116K /var/log/hp-snmp-agents/cma.log 112K /var/log/vinchin 104K /var/log/vinchin/kvm_backup_service 104K /var/log/tuned/tuned.log.2 # # find . -printf '%s %p\n'| sort -nr | head -10 16311686 ./rhsm/rhsm.log 4070423 ./cron-20180726 3667146 ./anaconda/journal.log 3409071 ./secure 3066660 ./rhsm/rhsm.log-20180726 2912670 ./audit/audit.log 1418007 ./sanlock.log 1189580 ./vdsm/vdsm.log 592718 ./anaconda/storage.log 487567 ./anaconda/packaging.log

3 4

Re: Lost space in /var/log
by Michael Thomas 22 Jun '22

22 Jun '22

This can also happen with a misconfigured logrotate config. If a process is writing to a large log file, and logrotate comes along and removes it, then the process still has an open filehandle to the large file even though you can't see it. The space won't get removed until the process closes the filehandle (eg rebooting). The following command should give you a list of these ghost files that are still open but have been removed from the directory tree: lsof | grep '(deleted)' Stackexchange has some additional useful tips: https://unix.stackexchange.com/questions/68523/find-and-remove-large-files-… --Mike On 6/22/22 15:49, Matthew.Stier(a)fujitsu.com wrote: > Deleted some files to "clean up" /var/log, but the space was not recovered? > > Space for deleted files are only recovered when all references to that space are removed. This includes the directory reference, and any open file-handles to the file. > > The is a popular trick for a self-deleting scratch file. Create a file, open file-handle to it, and then remove the file. The open file-handle can then be written to, and read from, as long as you like, but when the file-handle is closed, explicitly or implicitly, the space is automatically recovered. > > > -----Original Message----- > From: Andrei Verovski <andreil1(a)starlett.lv> > Sent: Wednesday, June 22, 2022 3:27 PM > To: users(a)ovirt.org > Subject: [ovirt-users] Lost space in /var/log > > Hi ! > > I have strange situation with low disk space on /var/log/, yet I can't figure out what have consumed so much space. > Look at the du output. > > Thanks in advance for any suggestion(s). > > > # df -h > > Filesystem Size Used Avail Use% Mounted on > /dev/mapper/centos-var 15G 1.3G 13G 9% /var > /dev/mapper/centos-var_log 7.8G 7.1G 293M 97% /var/log > /dev/mapper/centos-var_log_audit 2.0G 41M 1.8G 3% /var/log/audit > > # > # du -ah /var/log | sort -n -r | head -n 20 > > 664K /var/log/vdsm > 660K /var/log/vdsm/vdsm.log > 624K /var/log/gdm > 580K /var/log/anaconda/storage.log > 480K /var/log/anaconda/packaging.log > 380K /var/log/gdm/:0.log.4 > 316K /var/log/anaconda/syslog > 276K /var/log/tuned > 252K /var/log/libvirt/qemu/NextCloud-Collabora-LVM.log-20210806 > 220K /var/log/Xorg.0.log > 168K /var/log/gdm/:0.log > 156K /var/log/yum.log-20191117 > 156K /var/log/secure-20180726 > 132K /var/log/libvirt/qemu/NextCloud-Collabora-Active.log > 128K /var/log/anaconda/anaconda.log > 120K /var/log/hp-snmp-agents > 116K /var/log/hp-snmp-agents/cma.log > 112K /var/log/vinchin > 104K /var/log/vinchin/kvm_backup_service > 104K /var/log/tuned/tuned.log.2 > > # > # find . -printf '%s %p\n'| sort -nr | head -10 > > 16311686 ./rhsm/rhsm.log > 4070423 ./cron-20180726 > 3667146 ./anaconda/journal.log > 3409071 ./secure > 3066660 ./rhsm/rhsm.log-20180726 > 2912670 ./audit/audit.log > 1418007 ./sanlock.log > 1189580 ./vdsm/vdsm.log > 592718 ./anaconda/storage.log > 487567 ./anaconda/packaging.log > _______________________________________________ > Users mailing list -- users(a)ovirt.org > To unsubscribe send an email to users-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/users@ovirt.org/message/N566CST3DAXIL… > _______________________________________________ > Users mailing list -- users(a)ovirt.org > To unsubscribe send an email to users-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/users@ovirt.org/message/JCAQU32UZSEWK…

1 0

Q: Error ID 119 - ioctl(KVM_CREATE_VM) failed: Cannot allocate memory
by Andrei Verovski 22 Jun '22

22 Jun '22

Hi ! Does this error message means node runs out of RAM? Quite strange since there are about 20 GB of free RAN, and VM requires only 8. I noticed this happen till Vinchin was in a process of removing snapshot from another VM. Thanks. VM Jumis_VM-Active is down with error. Exit message: internal error: process exited while connecting to monitor: ioctl(KVM_CREATE_VM) failed: 12 Cannot allocate memory 2022-06-22T19:50:46.501704Z qemu-kvm: failed to initialize KVM: Cannot allocate memory.

1 0

Move Master Storage Domain
by john＠penrod.net 22 Jun '22

22 Jun '22

Running oVirt 4.3.10. Three storage domains. #1 is the current master. No disks/data remain on it. All virtual machines have been moved. I plan to put it in maintenance mode and let it force an election. I don't care which of the remaining two become master. Will this impact virtual machines that are currently running? If possible, I need to keep them running. Thoughts?

1 0

Cannot export VM to another data domain. "o.original_template is undefined"
by Gilboa Davara 22 Jun '22

22 Jun '22

Hello, 4.4.10 Gluster based cluster w/ 3 nodes. I'm backing up all VMs before upgrading the setup to 4.5. (Hopefully done right before 4.5.1 w/ Gluster fix is released). When trying to export a VM to another data domain, several VMs show the following error: "Export VM Failed. o.original_template is undefined". Engine log looks clean (I see nothing about the failed upgrade). Any idea what's broken? - Gilboa

2 11

datacenter, node becam non responsive after power cut
by moulayhakim3＠yahoo.com 22 Jun '22

22 Jun '22

hello team, i have self hosted engine, after power cut , the datacenter and node becam non responsive, can you help me please

1 0

Gluster Volume cannot be activated Ovirt 4.5 Centos 8 Stream
by m.rohweder＠itm-h.de 21 Jun '22

21 Jun '22

Hi, i convertet my ovirt 4.5 tu ovirt 4.5 hyperconverged. (activate on cluster the gluster service and reinstalled all hosts) I can create bricks on hosts and i'm able to create a Volume. All with the Ovirt GUI. But if i want to activate the Volume, i get the error mesage that no host with running gluster is found in my cluster. All hosts show message that ovirt think glusterd ist not running, but its running on all hosts. What can i du to use gluster with the lokal storage on each host? Greatings Michael

2 2

Ovirt 4.4 - starting just-installed host from ovirt console fails
by David Johnson 21 Jun '22

21 Jun '22

Good afternoon all, I recently had to rebuild my cluster due to a self inflicted error. I have finally managed to get the ovirt host software installed and communicating on all hosts. The first host installed and started cleanly. However, after installation the second host is failing to start. Prior to my cluster crash, this host was running well in the cluster. During the downtime, we applied microcode and BIOS updates as part of the recovery process. I have reviewed this chain: https://lists.ovirt.org/archives/list/users@ovirt.org/thread/N3PPT34GBRLPLT… and reached a dead end. Based on what I see (in the long stream of logs and info following), it looks like I should change the cluster CPU type from Cascadelake to Haswell to restore normal operation. The long involved stuff: The Engine reports: [image: image.png] Host CPU type is not compatible with Cluster Properties. [image: image.png] The host CPU does not match the Cluster CPU Type and is running in a degraded mode. It is missing the following CPU flags: model_Cascadelake-Server-noTSX. Please update the host CPU microcode or change the Cluster CPU Type. The Cluster definition is: [image: image.png] *lscpu returns:* Architecture: x86_64 CPU op-mode(s): 32-bit, 64-bit Byte Order: Little Endian CPU(s): 48 On-line CPU(s) list: 0-47 Thread(s) per core: 2 Core(s) per socket: 12 Socket(s): 2 NUMA node(s): 2 Vendor ID: GenuineIntel BIOS Vendor ID: Intel(R) Corporation CPU family: 6 Model: 63 Model name: Intel(R) Xeon(R) CPU E5-2680 v3 @ 2.50GHz BIOS Model name: Intel(R) Xeon(R) CPU E5-2680 v3 @ 2.50GHz Stepping: 2 CPU MHz: 3300.000 CPU max MHz: 3300.0000 CPU min MHz: 1200.0000 BogoMIPS: 4988.45 Virtualization: VT-x L1d cache: 32K L1i cache: 32K L2 cache: 256K L3 cache: 30720K NUMA node0 CPU(s): 0-11,24-35 NUMA node1 CPU(s): 12-23,36-47 Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid dca sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm cpuid_fault epb invpcid_single pti intel_ppin ssbd ibrs ibpb stibp tpr_shadow vnmi flexpriority ept vpid ept_ad fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid cqm xsaveopt cqm_llc cqm_occup_llc dtherm ida arat pln pts md_clear flush_l1d *cpuid returns:* CPU 0: vendor_id = "GenuineIntel" version information (1/eax): processor type = primary processor (0) family = 0x6 (6) model = 0xf (15) stepping id = 0x2 (2) extended family = 0x0 (0) extended model = 0x3 (3) (family synth) = 0x6 (6) (model synth) = 0x3f (63) (simple synth) = Intel (unknown type) (Haswell C1/M1/R2) {Haswell}, 22nm *virsh domcapabilities returns:* <domainCapabilities> <path>/usr/libexec/qemu-kvm</path> <domain>kvm</domain> <machine>pc-i440fx-rhel7.6.0</machine> <arch>x86_64</arch> <vcpu max='240'/> <iothreads supported='yes'/> <os supported='yes'> <enum name='firmware'/> <loader supported='yes'> <value>/usr/share/OVMF/OVMF_CODE.secboot.fd</value> <enum name='type'> <value>rom</value> <value>pflash</value> </enum> <enum name='readonly'> <value>yes</value> <value>no</value> </enum> <enum name='secure'> <value>no</value> </enum> </loader> </os> <cpu> <mode name='host-passthrough' supported='yes'> <enum name='hostPassthroughMigratable'> <value>on</value> <value>off</value> </enum> </mode> <mode name='maximum' supported='yes'> <enum name='maximumMigratable'> <value>on</value> <value>off</value> </enum> </mode> <mode name='host-model' supported='yes'> <model fallback='forbid'>Haswell-noTSX-IBRS</model> <vendor>Intel</vendor> <feature policy='require' name='vme'/> <feature policy='require' name='ss'/> <feature policy='require' name='vmx'/> <feature policy='require' name='pdcm'/> <feature policy='require' name='f16c'/> <feature policy='require' name='rdrand'/> <feature policy='require' name='hypervisor'/> <feature policy='require' name='arat'/> <feature policy='require' name='tsc_adjust'/> <feature policy='require' name='umip'/> <feature policy='require' name='md-clear'/> <feature policy='require' name='stibp'/> <feature policy='require' name='arch-capabilities'/> <feature policy='require' name='ssbd'/> <feature policy='require' name='xsaveopt'/> <feature policy='require' name='pdpe1gb'/> <feature policy='require' name='abm'/> <feature policy='require' name='invtsc'/> <feature policy='require' name='ibpb'/> <feature policy='require' name='ibrs'/> <feature policy='require' name='amd-stibp'/> <feature policy='require' name='amd-ssbd'/> <feature policy='require' name='skip-l1dfl-vmentry'/> <feature policy='require' name='pschange-mc-no'/> </mode> <mode name='custom' supported='yes'> <model usable='yes'>qemu64</model> <model usable='yes'>qemu32</model> <model usable='no'>phenom</model> <model usable='yes'>pentium3</model> <model usable='yes'>pentium2</model> <model usable='yes'>pentium</model> <model usable='yes'>n270</model> <model usable='yes'>kvm64</model> <model usable='yes'>kvm32</model> <model usable='yes'>coreduo</model> <model usable='yes'>core2duo</model> <model usable='no'>athlon</model> <model usable='yes'>Westmere-IBRS</model> <model usable='yes'>Westmere</model> <model usable='no'>Snowridge</model> <model usable='no'>Skylake-Server-noTSX-IBRS</model> <model usable='no'>Skylake-Server-IBRS</model> <model usable='no'>Skylake-Server</model> <model usable='no'>Skylake-Client-noTSX-IBRS</model> <model usable='no'>Skylake-Client-IBRS</model> <model usable='no'>Skylake-Client</model> <model usable='yes'>SandyBridge-IBRS</model> <model usable='yes'>SandyBridge</model> <model usable='yes'>Penryn</model> <model usable='no'>Opteron_G5</model> <model usable='no'>Opteron_G4</model> <model usable='no'>Opteron_G3</model> <model usable='yes'>Opteron_G2</model> <model usable='yes'>Opteron_G1</model> <model usable='yes'>Nehalem-IBRS</model> <model usable='yes'>Nehalem</model> <model usable='yes'>IvyBridge-IBRS</model> <model usable='yes'>IvyBridge</model> <model usable='no'>Icelake-Server-noTSX</model> <model usable='no'>Icelake-Server</model> <model usable='no' deprecated='yes'>Icelake-Client-noTSX</model> <model usable='no' deprecated='yes'>Icelake-Client</model> <model usable='yes'>Haswell-noTSX-IBRS</model> <model usable='yes'>Haswell-noTSX</model> <model usable='no'>Haswell-IBRS</model> <model usable='no'>Haswell</model> <model usable='no'>EPYC-Rome</model> <model usable='no'>EPYC-Milan</model> <model usable='no'>EPYC-IBPB</model> <model usable='no'>EPYC</model> <model usable='no'>Dhyana</model> <model usable='no'>Cooperlake</model> <model usable='yes'>Conroe</model> <model usable='no'>Cascadelake-Server-noTSX</model> <model usable='no'>Cascadelake-Server</model> <model usable='no'>Broadwell-noTSX-IBRS</model> <model usable='no'>Broadwell-noTSX</model> <model usable='no'>Broadwell-IBRS</model> <model usable='no'>Broadwell</model> <model usable='yes'>486</model> </mode> </cpu> <memoryBacking supported='yes'> <enum name='sourceType'> <value>file</value> <value>anonymous</value> <value>memfd</value> </enum> </memoryBacking> <devices> <disk supported='yes'> <enum name='diskDevice'> <value>disk</value> <value>cdrom</value> <value>floppy</value> <value>lun</value> </enum> <enum name='bus'> <value>ide</value> <value>fdc</value> <value>scsi</value> <value>virtio</value> <value>usb</value> <value>sata</value> </enum> <enum name='model'> <value>virtio</value> <value>virtio-transitional</value> <value>virtio-non-transitional</value> </enum> </disk> <graphics supported='yes'> <enum name='type'> <value>vnc</value> <value>spice</value> <value>egl-headless</value> </enum> </graphics> <video supported='yes'> <enum name='modelType'> <value>vga</value> <value>cirrus</value> <value>qxl</value> <value>virtio</value> <value>none</value> <value>bochs</value> <value>ramfb</value> </enum> </video> <hostdev supported='yes'> <enum name='mode'> <value>subsystem</value> </enum> <enum name='startupPolicy'> <value>default</value> <value>mandatory</value> <value>requisite</value> <value>optional</value> </enum> <enum name='subsysType'> <value>usb</value> <value>pci</value> <value>scsi</value> </enum> <enum name='capsType'/> <enum name='pciBackend'/> </hostdev> <rng supported='yes'> <enum name='model'> <value>virtio</value> <value>virtio-transitional</value> <value>virtio-non-transitional</value> </enum> <enum name='backendModel'> <value>random</value> <value>egd</value> <value>builtin</value> </enum> </rng> <filesystem supported='yes'> <enum name='driverType'> <value>path</value> <value>handle</value> <value>virtiofs</value> </enum> </filesystem> <tpm supported='yes'> <enum name='model'> <value>tpm-tis</value> <value>tpm-crb</value> </enum> <enum name='backendModel'> <value>passthrough</value> <value>emulator</value> </enum> </tpm> </devices> <features> <gic supported='no'/> <vmcoreinfo supported='yes'/> <genid supported='yes'/> <backingStoreInput supported='yes'/> <backup supported='yes'/> <sev supported='no'/> </features> </domainCapabilities> Please advise.

1 1

Preferred RHEL Based Distro For oVirt
by Clint Boggio 21 Jun '22

21 Jun '22

Good Day All; i am inquiring about which RHEL based distros are currently preferred and which ones are currently supported. I know the oVirt project is a RH entity and so RHEL and CentOS-Stream are the base offering. Would it, or is it, feasible for Rocky 8.X, or Alma 8.X to be the base OS for an oVirt deployment seeing as though they both RHEL clones ? How confident is the user community in the stability of CentOS-Stream in terms of production use as compared to Alma or Rocky ?

3 4

failed to mount hosted engine gluster storage - how to debug?
by diego.ercolani＠ssis.sm 21 Jun '22

21 Jun '22

Hello, I have an issue probably related to my particular implementation but I think some controls are missing Here is the story. I have a cluster of two nodes 4.4.10.3 with an upgraded kernel as the cpu (Ryzen 5) suffer from an incompatibility issue with the kernel provided by 4.4.10.x series. On each node there are three glusterfs "partitions" in replica mode, one for the hosted_engine, the other two are for user usage. The third node was an old i3 workstation only used to provide the arbiter partition to the glusterfs cluster. I installed a new server (ryzen processor) with 4.5.0 and successfully installed glusterfs 10.1 and inserted the arbiter bricks implemented on glusterfs 10.1 while the replica bricks are 8.6 after removing the old i3 provided bricks. I successfully imported the new node in the ovirt engine (after updating the engine to 4.5) The problem is that the ovirt-ha-broker doesn't start complaining that is not possible to connect the storage. (I suppose the hosted_engine storage) so I did some digs that I'm going to show here: #### 1. The node seem to be correctly configured: [root@ovirt-node3 devices]# vdsm-tool validate-config SUCCESS: ssl configured to true. No conflicts [root@ovirt-node3 devices]# vdsm-tool configure Checking configuration status... libvirt is already configured for vdsm SUCCESS: ssl configured to true. No conflicts sanlock is configured for vdsm Managed volume database is already configured lvm is configured for vdsm Current revision of multipath.conf detected, preserving Running configure... Done configuring modules to VDSM. [root@ovirt-node3 devices]# vdsm-tool validate-config SUCCESS: ssl configured to true. No conflicts #### 2. the node refuses to mount via hosted-engine (same error in broker.log) [root@ovirt-node3 devices]# hosted-engine --connect-storage Traceback (most recent call last): File "/usr/lib64/python3.6/runpy.py", line 193, in _run_module_as_main "__main__", mod_spec) File "/usr/lib64/python3.6/runpy.py", line 85, in _run_code exec(code, run_globals) File "/usr/lib/python3.6/site-packages/ovirt_hosted_engine_setup/connect_storage_server.py", line 30, in <module> timeout=ohostedcons.Const.STORAGE_SERVER_TIMEOUT, File "/usr/lib/python3.6/site-packages/ovirt_hosted_engine_ha/client/client.py", line 312, in connect_storage_server sserver.connect_storage_server(timeout=timeout) File "/usr/lib/python3.6/site-packages/ovirt_hosted_engine_ha/lib/storage_server.py", line 451, in connect_storage_server 'Connection to storage server failed' RuntimeError: Connection to storage server failed ##### 3. manually mount of glusterfs work correctly [root@ovirt-node3 devices]# grep storage /etc/ovirt-hosted-engine/hosted-engine.conf storage=ovirt-node2.ovirt:/gveng # The following are used only for iSCSI storage [root@ovirt-node3 devices]# [root@ovirt-node3 devices]# mount -t glusterfs ovirt-node2.ovirt:/gveng /mnt/tmp/ [root@ovirt-node3 devices]# ls -l /mnt/tmp total 0 drwxr-xr-x. 6 vdsm kvm 64 Dec 15 19:04 7b8f1cc9-e3de-401f-b97f-8c281ca30482 What else should I control? Thank you and sorry for the long message Diego

5 9