- Users - oVirt List Archives

ovirt-4.4 repo fails
by atatur.yildirim＠gmail.com 04 Mar '22

04 Mar '22

Hello all, I try to deploy the latest ovirt 4.4.10.3, but deploy script fails with DNF Failed to download metadata for repo 'ovirt-4.4-centos-ovirt44': repomd.xml parser error: Parse error at line: 18 (Opening and ending tag mismatch: link line 0 and head Can you please help ? Thank you..

1 1

Multiple dependencies unresolved
by Andrea Chierici 03 Mar '22

03 Mar '22

Dear all, lately the engine started notifying me about some "errors": "Failed to check for available updates on host XYZ with message 'Task Ensure Python3 is installed for CentOS/RHEL8 hosts failed to execute. Please check logs for more details" I do understand this is not something that can impact my cluster stability, since it's only a matter of checking updates, anyway it annoys me a lot. I checked the logs and apparently the issue is related to some repos that are missing/unresolved. Right now on my hosts I have these repos: ovirt-release44-4.4.8.3-1.el8.noarch epel-release-8-13.el8.noarch centos-stream-release-8.6-1.el8.noarch puppet5-release-5.0.0-5.el8.noarch The problems come from: Error: Failed to download metadata for repo 'ovirt-4.4-centos-gluster8': Cannot prepare internal mirrorlist: No URLs in mirrorlist Error: Failed to download metadata for repo 'ovirt-4.4-centos-opstools': Cannot prepare internal mirrorlist: No URLs in mirrorlist Error: Failed to download metadata for repo 'ovirt-4.4-openstack-victoria': Cannot download repomd.xml: Cannot download repodata/repomd.xml: All mirrors were tried If I disable these repos "yum update" can finish but then I get a large number of unresolved dependencies and "problems": Error: Problem 1: package cockpit-ovirt-dashboard-0.15.1-1.el8.noarch requires ansible, but none of the providers can be installed - package ansible-core-2.12.2-2.el8.x86_64 obsoletes ansible < 2.10.0 provided by ansible-2.9.25-1.el8.noarch - package ansible-core-2.12.2-2.el8.x86_64 obsoletes ansible < 2.10.0 provided by ansible-2.9.27-1.el8.noarch - package ansible-core-2.12.2-2.el8.x86_64 obsoletes ansible < 2.10.0 provided by ansible-2.9.17-1.el8.noarch - package ansible-core-2.12.2-2.el8.x86_64 obsoletes ansible < 2.10.0 provided by ansible-2.9.18-2.el8.noarch - package ansible-core-2.12.2-2.el8.x86_64 obsoletes ansible < 2.10.0 provided by ansible-2.9.20-2.el8.noarch - package ansible-core-2.12.2-2.el8.x86_64 obsoletes ansible < 2.10.0 provided by ansible-2.9.21-2.el8.noarch - package ansible-core-2.12.2-2.el8.x86_64 obsoletes ansible < 2.10.0 provided by ansible-2.9.23-2.el8.noarch - package ansible-core-2.12.2-2.el8.x86_64 obsoletes ansible < 2.10.0 provided by ansible-2.9.24-2.el8.noarch - package ansible-2.9.27-2.el8.noarch conflicts with ansible-core > 2.11.0 provided by ansible-core-2.12.2-2.el8.x86_64 - package ansible-core-2.12.2-2.el8.x86_64 obsoletes ansible < 2.10.0 provided by ansible-2.9.27-2.el8.noarch - cannot install the best update candidate for package cockpit-ovirt-dashboard-0.15.1-1.el8.noarch - cannot install the best update candidate for package ansible-2.9.25-1.el8.noarch - package ansible-2.9.20-1.el8.noarch is filtered out by exclude filtering Problem 2: package fence-agents-ibm-powervs-4.2.1-84.el8.noarch requires fence-agents-common = 4.2.1-84.el8, but none of the providers can be installed - cannot install both fence-agents-common-4.2.1-88.el8.noarch and fence-agents-common-4.2.1-84.el8.noarch - cannot install the best update candidate for package fence-agents-ibm-powervs-4.2.1-77.el8.noarch - cannot install the best update candidate for package fence-agents-common-4.2.1-77.el8.noarch Problem 3: cannot install both fence-agents-common-4.2.1-88.el8.noarch and fence-agents-common-4.2.1-84.el8.noarch - package fence-agents-ibm-vpc-4.2.1-84.el8.noarch requires fence-agents-common = 4.2.1-84.el8, but none of the providers can be installed - package fence-agents-amt-ws-4.2.1-88.el8.noarch requires fence-agents-common >= 4.2.1-88.el8, but none of the providers can be installed - cannot install the best update candidate for package fence-agents-ibm-vpc-4.2.1-77.el8.noarch - cannot install the best update candidate for package fence-agents-amt-ws-4.2.1-77.el8.noarch Problem 4: problem with installed package fence-agents-ibm-vpc-4.2.1-77.el8.noarch - package fence-agents-ibm-vpc-4.2.1-77.el8.noarch requires fence-agents-common = 4.2.1-77.el8, but none of the providers can be installed - package fence-agents-ibm-vpc-4.2.1-78.el8.noarch requires fence-agents-common = 4.2.1-78.el8, but none of the providers can be installed - package fence-agents-ibm-vpc-4.2.1-82.el8.noarch requires fence-agents-common = 4.2.1-82.el8, but none of the providers can be installed - package fence-agents-ibm-vpc-4.2.1-83.el8.noarch requires fence-agents-common = 4.2.1-83.el8, but none of the providers can be installed - package fence-agents-ibm-vpc-4.2.1-84.el8.noarch requires fence-agents-common = 4.2.1-84.el8, but none of the providers can be installed - cannot install both fence-agents-common-4.2.1-88.el8.noarch and fence-agents-common-4.2.1-77.el8.noarch - cannot install both fence-agents-common-4.2.1-88.el8.noarch and fence-agents-common-4.2.1-78.el8.noarch - cannot install both fence-agents-common-4.2.1-88.el8.noarch and fence-agents-common-4.2.1-82.el8.noarch - cannot install both fence-agents-common-4.2.1-88.el8.noarch and fence-agents-common-4.2.1-83.el8.noarch - cannot install both fence-agents-common-4.2.1-88.el8.noarch and fence-agents-common-4.2.1-84.el8.noarch - package fence-agents-apc-4.2.1-88.el8.noarch requires fence-agents-common >= 4.2.1-88.el8, but none of the providers can be installed - cannot install the best update candidate for package fence-agents-apc-4.2.1-77.el8.noarch Problem 5: problem with installed package fence-agents-ibm-powervs-4.2.1-77.el8.noarch - package fence-agents-ibm-powervs-4.2.1-77.el8.noarch requires fence-agents-common = 4.2.1-77.el8, but none of the providers can be installed - package fence-agents-ibm-powervs-4.2.1-78.el8.noarch requires fence-agents-common = 4.2.1-78.el8, but none of the providers can be installed - package fence-agents-ibm-powervs-4.2.1-82.el8.noarch requires fence-agents-common = 4.2.1-82.el8, but none of the providers can be installed - package fence-agents-ibm-powervs-4.2.1-83.el8.noarch requires fence-agents-common = 4.2.1-83.el8, but none of the providers can be installed - package fence-agents-ibm-powervs-4.2.1-84.el8.noarch requires fence-agents-common = 4.2.1-84.el8, but none of the providers can be installed - cannot install both fence-agents-common-4.2.1-88.el8.noarch and fence-agents-common-4.2.1-77.el8.noarch - cannot install both fence-agents-common-4.2.1-88.el8.noarch and fence-agents-common-4.2.1-78.el8.noarch - cannot install both fence-agents-common-4.2.1-88.el8.noarch and fence-agents-common-4.2.1-82.el8.noarch - cannot install both fence-agents-common-4.2.1-88.el8.noarch and fence-agents-common-4.2.1-83.el8.noarch - cannot install both fence-agents-common-4.2.1-88.el8.noarch and fence-agents-common-4.2.1-84.el8.noarch - package fence-agents-apc-snmp-4.2.1-88.el8.noarch requires fence-agents-common >= 4.2.1-88.el8, but none of the providers can be installed - cannot install the best update candidate for package fence-agents-apc-snmp-4.2.1-77.el8.noarch My question is: since I am not willing to update anything right now, and I just want to get rid of the stupid python3 error, should I disable these repos, even if now I get some dep issues or the solution is another? Any suggestion? Thanks, Andrea -- Andrea Chierici - INFN-CNAF Viale Berti Pichat 6/2, 40127 BOLOGNA Office Tel: +39 051 2095463 SkypeID ataruz --

3 5

Does memory ballooning works if memory overcommit is disabled in the cluster
by sohail_akhter3＠hotmail.com 03 Mar '22

03 Mar '22

Hi All, We have one ovirt 4.4 environment running. In Cluster Optimization settings we have checked "None - Disable memory overcommit" Option in Memory Optimization. But Memory Balloon check box option is enabled. My understanding is that Ballooning only works when memory overcommit is enabled. If it is true then this check box should be disabled when we are not overcommitting memory. Or Still memory ballooning works even if we disabled memory overcommit. According to below link ballooning works when memory overcommit is enabled. https://lists.ovirt.org/pipermail/users/2017-October/084675.html Please let me know if any further information is required. Many thanks. Regards Sohail

2 1

[ANN] oVirt Node 4.4.10.2 Async update
by Sandro Bonazzola 03 Mar '22

03 Mar '22

On March 3rd 2022 the oVirt project released an async update of oVirt Node (4.4.10.2) delivering fixes for the following issues: Bug 2057447 <https://bugzilla.redhat.com/show_bug.cgi?id=2057447> - CVE-2022-24407 <https://access.redhat.com/security/cve/CVE-2022-24407> cyrus-sasl: failure to properly escape SQL input allows an attacker to execute arbitrary SQL commands [ovirt-4.4] Bug 2055098 <https://bugzilla.redhat.com/show_bug.cgi?id=2055098> - CVE-2022-22942 <https://access.redhat.com/security/cve/CVE-2022-22942> kernel: failing usercopy allows for use-after-free exploitation [ovirt-4.4] Bug 2047640 <https://bugzilla.redhat.com/show_bug.cgi?id=2047640> - CVE-2021-0920 <https://access.redhat.com/security/cve/CVE-2021-0920> kernel: Use After Free in unix_gc() which could result in a local privilege escalation [ovirt-4.4] Bug 2047630 <https://bugzilla.redhat.com/show_bug.cgi?id=2047630> - CVE-2021-4154 <https://access.redhat.com/security/cve/CVE-2021-4154> kernel: local privilege escalation by exploiting the fsconfig syscall parameter leads to container breakout [ovirt-4.4] Bug 2046005 <https://bugzilla.redhat.com/show_bug.cgi?id=2046005> - CVE-2022-0330 <https://access.redhat.com/security/cve/CVE-2022-0330> kernel: possible privileges escalation due to missing TLB flush [ovirt-4.4] Bug 2043471 <https://bugzilla.redhat.com/show_bug.cgi?id=2043471> - CVE-2021-45417 <https://access.redhat.com/security/cve/CVE-2021-45417> aide: heap-based buffer overflow on outputs larger than B64_BUF [ovirt-4.4] Several bug fixes and improvements from CentOS Stream. Here’s the full list of changes: ovirt-node-ng-4.4.10.1 ovirt-node-ng-4.4.10.2 NetworkManager 1.36.0-0.4.el8 1.36.0-1.el8 NetworkManager-config-server 1.36.0-0.4.el8 1.36.0-1.el8 NetworkManager-libnm 1.36.0-0.4.el8 1.36.0-1.el8 NetworkManager-ovs 1.36.0-0.4.el8 1.36.0-1.el8 NetworkManager-team 1.36.0-0.4.el8 1.36.0-1.el8 NetworkManager-tui 1.36.0-0.4.el8 1.36.0-1.el8 aide 0.16-14.el8 0.16-14.el8_5.1 alsa-lib 1.2.6.1-1.el8 1.2.6.1-3.el8 audispd-plugins 3.0.7-1.el8 3.0.7-2.el8 audit 3.0.7-1.el8 3.0.7-2.el8 audit-libs 3.0.7-1.el8 3.0.7-2.el8 autofs 5.1.4-77.el8 5.1.4-82.el8 bind-export-libs 9.11.36-2.el8 9.11.36-3.el8 bind-libs 9.11.36-2.el8 9.11.36-3.el8 bind-libs-lite 9.11.36-2.el8 9.11.36-3.el8 bind-license 9.11.36-2.el8 9.11.36-3.el8 bind-utils 9.11.36-2.el8 9.11.36-3.el8 blivet-data 3.4.0-8.el8 3.4.0-9.el8 cairo 1.15.12-3.el8 1.15.12-6.el8 cockpit 261-1.el8 264-1.el8 cockpit-bridge 261-1.el8 264-1.el8 cockpit-storaged 261-1.el8 264-1.el8 cockpit-system 261-1.el8 264-1.el8 cockpit-ws 261-1.el8 264-1.el8 cryptsetup 2.3.3-4.el8 2.3.7-2.el8 cryptsetup-libs 2.3.3-4.el8 2.3.7-2.el8 cups-libs 2.2.6-42.el8 2.2.6-44.el8 cyrus-sasl 2.1.27-5.el8 2.1.27-6.el8_5 cyrus-sasl-gssapi 2.1.27-5.el8 2.1.27-6.el8_5 cyrus-sasl-lib 2.1.27-5.el8 2.1.27-6.el8_5 cyrus-sasl-scram 2.1.27-5.el8 2.1.27-6.el8_5 device-mapper-multipath 0.8.4-21.el8 0.8.4-22.el8 device-mapper-multipath-libs 0.8.4-21.el8 0.8.4-22.el8 dnf 4.7.0-5.el8 4.7.0-7.el8 dnf-data 4.7.0-5.el8 4.7.0-7.el8 dnf-plugins-core 4.0.21-8.el8 4.0.21-10.el8 dnsmasq 2.79-20.el8 2.79-21.el8 dracut 049-191.git20210920.el8 049-201.git20220131.el8 dracut-config-generic 049-191.git20210920.el8 049-201.git20220131.el8 dracut-live 049-191.git20210920.el8 049-201.git20220131.el8 dracut-network 049-191.git20210920.el8 049-201.git20220131.el8 dracut-squash 049-191.git20210920.el8 049-201.git20220131.el8 e2fsprogs 1.45.6-2.el8 1.45.6-3.el8 e2fsprogs-libs 1.45.6-2.el8 1.45.6-3.el8 edk2-ovmf 20210527gite1999b264f1f-3.el8 20220126gitbb1bba3d77-1.el8.test expat 2.2.5-4.el8 2.2.5-5.el8 fence-agents-all 4.2.1-85.el8 4.2.1-88.el8 fence-agents-amt-ws 4.2.1-85.el8 4.2.1-88.el8 fence-agents-apc 4.2.1-85.el8 4.2.1-88.el8 fence-agents-apc-snmp 4.2.1-85.el8 4.2.1-88.el8 fence-agents-bladecenter 4.2.1-85.el8 4.2.1-88.el8 fence-agents-brocade 4.2.1-85.el8 4.2.1-88.el8 fence-agents-cisco-mds 4.2.1-85.el8 4.2.1-88.el8 fence-agents-cisco-ucs 4.2.1-85.el8 4.2.1-88.el8 fence-agents-common 4.2.1-85.el8 4.2.1-88.el8 fence-agents-compute 4.2.1-85.el8 4.2.1-88.el8 fence-agents-drac5 4.2.1-85.el8 4.2.1-88.el8 fence-agents-eaton-snmp 4.2.1-85.el8 4.2.1-88.el8 fence-agents-emerson 4.2.1-85.el8 4.2.1-88.el8 fence-agents-eps 4.2.1-85.el8 4.2.1-88.el8 fence-agents-heuristics-ping 4.2.1-85.el8 4.2.1-88.el8 fence-agents-hpblade 4.2.1-85.el8 4.2.1-88.el8 fence-agents-ibmblade 4.2.1-85.el8 4.2.1-88.el8 fence-agents-ifmib 4.2.1-85.el8 4.2.1-88.el8 fence-agents-ilo-moonshot 4.2.1-85.el8 4.2.1-88.el8 fence-agents-ilo-mp 4.2.1-85.el8 4.2.1-88.el8 fence-agents-ilo-ssh 4.2.1-85.el8 4.2.1-88.el8 fence-agents-ilo2 4.2.1-85.el8 4.2.1-88.el8 fence-agents-intelmodular 4.2.1-85.el8 4.2.1-88.el8 fence-agents-ipdu 4.2.1-85.el8 4.2.1-88.el8 fence-agents-ipmilan 4.2.1-85.el8 4.2.1-88.el8 fence-agents-kdump 4.2.1-85.el8 4.2.1-88.el8 fence-agents-mpath 4.2.1-85.el8 4.2.1-88.el8 fence-agents-redfish 4.2.1-85.el8 4.2.1-88.el8 fence-agents-rhevm 4.2.1-85.el8 4.2.1-88.el8 fence-agents-rsa 4.2.1-85.el8 4.2.1-88.el8 fence-agents-rsb 4.2.1-85.el8 4.2.1-88.el8 fence-agents-sbd 4.2.1-85.el8 4.2.1-88.el8 fence-agents-scsi 4.2.1-85.el8 4.2.1-88.el8 fence-agents-vmware-rest 4.2.1-85.el8 4.2.1-88.el8 fence-agents-vmware-soap 4.2.1-85.el8 4.2.1-88.el8 fence-agents-wti 4.2.1-85.el8 4.2.1-88.el8 firewalld 0.9.3-11.el8 0.9.3-13.el8 firewalld-filesystem 0.9.3-11.el8 0.9.3-13.el8 fuse 2.9.7-12.el8 2.9.7-15.el8 fuse-common 3.2.1-12.el8 3.3.0-15.el8 fuse-libs 2.9.7-12.el8 2.9.7-15.el8 fuse3-libs 3.2.1-12.el8 3.3.0-15.el8 gawk 4.2.1-2.el8 4.2.1-4.el8 glibc 2.28-184.el8 2.28-189.el8 glibc-common 2.28-184.el8 2.28-189.el8 glibc-langpack-en 2.28-184.el8 2.28-189.el8 gpgme 1.13.1-9.el8 1.13.1-11.el8 hwdata 0.314-8.11.el8 0.314-8.12.el8 info 6.5-6.el8 6.5-7.el8_5 initscripts 10.00.15-1.el8 10.00.17-1.el8 iotop 0.6-16.el8 0.6-17.el8 iproute 5.15.0-2.el8 5.15.0-3.el8 iproute-tc 5.15.0-2.el8 5.15.0-3.el8 iputils 20180629-8.el8 20180629-9.el8 iwl100-firmware 39.31.5.1-105.el8.1 39.31.5.1-106.el8.1 iwl1000-firmware 39.31.5.1-105.el8.1 39.31.5.1-106.el8.1 iwl105-firmware 18.168.6.1-105.el8.1 18.168.6.1-106.el8.1 iwl135-firmware 18.168.6.1-105.el8.1 18.168.6.1-106.el8.1 iwl2000-firmware 18.168.6.1-105.el8.1 18.168.6.1-106.el8.1 iwl2030-firmware 18.168.6.1-105.el8.1 18.168.6.1-106.el8.1 iwl3160-firmware 25.30.13.0-105.el8.1 25.30.13.0-106.el8.1 iwl5000-firmware 8.83.5.1_1-105.el8.1 8.83.5.1_1-106.el8.1 iwl5150-firmware 8.24.2.2-105.el8.1 8.24.2.2-106.el8.1 iwl6000-firmware 9.221.4.1-105.el8.1 9.221.4.1-106.el8.1 iwl6000g2a-firmware 18.168.6.1-105.el8.1 18.168.6.1-106.el8.1 iwl6050-firmware 41.28.5.1-105.el8.1 41.28.5.1-106.el8.1 iwl7260-firmware 25.30.13.0-105.el8.1 25.30.13.0-106.el8.1 kernel 4.18.0-358.el8 4.18.0-365.el8 kernel-core 4.18.0-358.el8 4.18.0-365.el8 kernel-modules 4.18.0-358.el8 4.18.0-365.el8 kernel-tools 4.18.0-358.el8 4.18.0-365.el8 kernel-tools-libs 4.18.0-358.el8 4.18.0-365.el8 kmod-kvdo 6.2.6.3-82.el8 6.2.6.14-83.el8 kpartx 0.8.4-21.el8 0.8.4-22.el8 libblkid 2.32.1-32.el8 2.32.1-34.el8 libcap 2.26-5.el8 2.48-2.el8 libcom_err 1.45.6-2.el8 1.45.6-3.el8 libdnf 0.63.0-5.el8 0.63.0-7.el8 libfdisk 2.32.1-32.el8 2.32.1-34.el8 libfdt 1.6.0-1.el8 libguestfs 1.44.0-4.module_el8.6.0+983+a7505f3f 1.44.0-5.module_el8.6.0+1087+b42c8331 libguestfs-appliance 1.44.0-4.module_el8.6.0+983+a7505f3f 1.44.0-5.module_el8.6.0+1087+b42c8331 libguestfs-tools-c 1.44.0-4.module_el8.6.0+983+a7505f3f 1.44.0-5.module_el8.6.0+1087+b42c8331 libmount 2.32.1-32.el8 2.32.1-34.el8 libnfsidmap 2.3.3-47.el8 2.3.3-50.el8 libosinfo 1.9.0-2.el8 1.9.0-3.el8 libsemanage 2.9-6.el8 2.9-8.el8 libsmartcols 2.32.1-32.el8 2.32.1-34.el8 libss 1.45.6-2.el8 1.45.6-3.el8 libtpms 0.7.4-6.20201106git2452a24dab.module_el8.6.0+983+a7505f3f 0.9.1-0.20211126git1ff6fe1f43.module_el8.6.0+1087+b42c8331 libudisks2 2.9.0-7.el8 2.9.0-9.el8 libuuid 2.32.1-32.el8 2.32.1-34.el8 libvirt 7.10.0-1.module_el8.6.0+1046+bd8eec5e 8.0.0-2.module_el8.6.0+1087+b42c8331 libvirt-client 7.10.0-1.module_el8.6.0+1046+bd8eec5e 8.0.0-2.module_el8.6.0+1087+b42c8331 libvirt-daemon 7.10.0-1.module_el8.6.0+1046+bd8eec5e 8.0.0-2.module_el8.6.0+1087+b42c8331 libvirt-daemon-config-network 7.10.0-1.module_el8.6.0+1046+bd8eec5e 8.0.0-2.module_el8.6.0+1087+b42c8331 libvirt-daemon-config-nwfilter 7.10.0-1.module_el8.6.0+1046+bd8eec5e 8.0.0-2.module_el8.6.0+1087+b42c8331 libvirt-daemon-driver-interface 7.10.0-1.module_el8.6.0+1046+bd8eec5e 8.0.0-2.module_el8.6.0+1087+b42c8331 libvirt-daemon-driver-network 7.10.0-1.module_el8.6.0+1046+bd8eec5e 8.0.0-2.module_el8.6.0+1087+b42c8331 libvirt-daemon-driver-nodedev 7.10.0-1.module_el8.6.0+1046+bd8eec5e 8.0.0-2.module_el8.6.0+1087+b42c8331 libvirt-daemon-driver-nwfilter 7.10.0-1.module_el8.6.0+1046+bd8eec5e 8.0.0-2.module_el8.6.0+1087+b42c8331 libvirt-daemon-driver-qemu 7.10.0-1.module_el8.6.0+1046+bd8eec5e 8.0.0-2.module_el8.6.0+1087+b42c8331 libvirt-daemon-driver-secret 7.10.0-1.module_el8.6.0+1046+bd8eec5e 8.0.0-2.module_el8.6.0+1087+b42c8331 libvirt-daemon-driver-storage 7.10.0-1.module_el8.6.0+1046+bd8eec5e 8.0.0-2.module_el8.6.0+1087+b42c8331 libvirt-daemon-driver-storage-core 7.10.0-1.module_el8.6.0+1046+bd8eec5e 8.0.0-2.module_el8.6.0+1087+b42c8331 libvirt-daemon-driver-storage-disk 7.10.0-1.module_el8.6.0+1046+bd8eec5e 8.0.0-2.module_el8.6.0+1087+b42c8331 libvirt-daemon-driver-storage-gluster 7.10.0-1.module_el8.6.0+1046+bd8eec5e 8.0.0-2.module_el8.6.0+1087+b42c8331 libvirt-daemon-driver-storage-iscsi 7.10.0-1.module_el8.6.0+1046+bd8eec5e 8.0.0-2.module_el8.6.0+1087+b42c8331 Libvirt-daemon-driver-storage-iscsi-direct 7.10.0-1.module_el8.6.0+1046+bd8eec5e 8.0.0-2.module_el8.6.0+1087+b42c8331 libvirt-daemon-driver-storage-logical 7.10.0-1.module_el8.6.0+1046+bd8eec5e 8.0.0-2.module_el8.6.0+1087+b42c8331 libvirt-daemon-driver-storage-mpath 7.10.0-1.module_el8.6.0+1046+bd8eec5e 8.0.0-2.module_el8.6.0+1087+b42c8331 libvirt-daemon-driver-storage-rbd 7.10.0-1.module_el8.6.0+1046+bd8eec5e 8.0.0-2.module_el8.6.0+1087+b42c8331 libvirt-daemon-driver-storage-scsi 7.10.0-1.module_el8.6.0+1046+bd8eec5e 8.0.0-2.module_el8.6.0+1087+b42c8331 libvirt-daemon-kvm 7.10.0-1.module_el8.6.0+1046+bd8eec5e 8.0.0-2.module_el8.6.0+1087+b42c8331 libvirt-libs 7.10.0-1.module_el8.6.0+1046+bd8eec5e 8.0.0-2.module_el8.6.0+1087+b42c8331 libvirt-lock-sanlock 7.10.0-1.module_el8.6.0+1046+bd8eec5e 8.0.0-2.module_el8.6.0+1087+b42c8331 libwbclient 4.15.4-0.el8 4.15.5-4.el8 libxml2 2.9.7-11.el8 2.9.7-13.el8 linux-firmware 20211119-105.gitf5d51956.el8 20220210-106.git6342082c.el8 mdadm 4.2-rc3.el8 4.2-2.el8 microcode_ctl 20210608-1.el8 20220207-1.el8 nbdkit 1.24.0-3.module_el8.6.0+983+a7505f3f 1.24.0-4.module_el8.6.0+1087+b42c8331 nbdkit-basic-filters 1.24.0-3.module_el8.6.0+983+a7505f3f 1.24.0-4.module_el8.6.0+1087+b42c8331 nbdkit-basic-plugins 1.24.0-3.module_el8.6.0+983+a7505f3f 1.24.0-4.module_el8.6.0+1087+b42c8331 nbdkit-curl-plugin 1.24.0-3.module_el8.6.0+983+a7505f3f 1.24.0-4.module_el8.6.0+1087+b42c8331 nbdkit-python-plugin 1.24.0-3.module_el8.6.0+983+a7505f3f 1.24.0-4.module_el8.6.0+1087+b42c8331 nbdkit-server 1.24.0-3.module_el8.6.0+983+a7505f3f 1.24.0-4.module_el8.6.0+1087+b42c8331 nbdkit-ssh-plugin 1.24.0-3.module_el8.6.0+983+a7505f3f 1.24.0-4.module_el8.6.0+1087+b42c8331 nbdkit-vddk-plugin 1.24.0-3.module_el8.6.0+983+a7505f3f 1.24.0-4.module_el8.6.0+1087+b42c8331 net-snmp 5.8-24.el8 5.8-25.el8 net-snmp-agent-libs 5.8-24.el8 5.8-25.el8 net-snmp-libs 5.8-24.el8 5.8-25.el8 net-snmp-utils 5.8-24.el8 5.8-25.el8 nfs-utils 2.3.3-47.el8 2.3.3-50.el8 nftables 0.9.3-24.el8 0.9.3-25.el8 nmstate 1.2.1-0.2.alpha2.el8 1.2.1-1.el8 nmstate-plugin-ovsdb 1.2.1-0.2.alpha2.el8 1.2.1-1.el8 openscap 1.3.5-10.el8 1.3.6-3.el8 openscap-scanner 1.3.5-10.el8 1.3.6-3.el8 ovirt-node-ng-image-update-placeholder 4.4.10.1-1.el8 4.4.10.2-1.el8 ovirt-release-host-node 4.4.10.1-1.el8 4.4.10.2-1.el8 ovirt-release44 4.4.10.1-1.el8 4.4.10.2-1.el8 pam 1.3.1-15.el8 1.3.1-16.el8 passwd 0.80-3.el8 0.80-4.el8 pixman 0.38.4-1.el8 0.38.4-2.el8 plymouth 0.9.4-10.20200615git1e36e30.el8 0.9.4-11.20200615git1e36e30.el8 plymouth-core-libs 0.9.4-10.20200615git1e36e30.el8 0.9.4-11.20200615git1e36e30.el8 plymouth-scripts 0.9.4-10.20200615git1e36e30.el8 0.9.4-11.20200615git1e36e30.el8 policycoreutils 2.9-18.el8 2.9-19.el8 policycoreutils-python-utils 2.9-18.el8 2.9-19.el8 postfix 3.5.8-3.el8 3.5.8-4.el8 python-oslo-utils-lang 4.6.0-2.el8 4.6.1-1.el8 python3-audit 3.0.7-1.el8 3.0.7-2.el8 python3-bind 9.11.36-2.el8 9.11.36-3.el8 python3-blivet 3.4.0-8.el8 3.4.0-9.el8 python3-configobj 5.0.6-11.el8 python3-dnf 4.7.0-5.el8 4.7.0-7.el8 python3-dnf-plugin-versionlock 4.0.21-8.el8 4.0.21-10.el8 python3-dnf-plugins-core 4.0.21-8.el8 4.0.21-10.el8 python3-ethtool 0.14-4.el8 0.14-5.el8 python3-firewall 0.9.3-11.el8 0.9.3-13.el8 python3-gpg 1.13.1-9.el8 1.13.1-11.el8 python3-hawkey 0.63.0-5.el8 0.63.0-7.el8 python3-libdnf 0.63.0-5.el8 0.63.0-7.el8 python3-libnmstate 1.2.1-0.2.alpha2.el8 1.2.1-1.el8 python3-libsemanage 2.9-6.el8 2.9-8.el8 python3-libvirt 7.10.0-1.module_el8.6.0+1046+bd8eec5e 8.0.0-1.module_el8.6.0+1087+b42c8331 python3-libxml2 2.9.7-11.el8 2.9.7-13.el8 python3-nftables 0.9.3-24.el8 0.9.3-25.el8 python3-oslo-service 2.4.0-2.el8 2.4.1-1.el8 python3-oslo-utils 4.6.0-2.el8 4.6.1-1.el8 python3-perf 4.18.0-358.el8 4.18.0-365.el8 python3-policycoreutils 2.9-18.el8 2.9-19.el8 python3-rpm 4.14.3-21.el8 4.14.3-22.el8 qemu-guest-agent 6.1.0-5.module_el8.6.0+1040+0ae94936 6.2.0-5.module_el8.6.0+1087+b42c8331 qemu-img 6.0.0-33.el8s 6.2.0-5.module_el8.6.0+1087+b42c8331 qemu-kvm 6.0.0-33.el8s 6.2.0-5.module_el8.6.0+1087+b42c8331 qemu-kvm-block-curl 6.0.0-33.el8s 6.2.0-5.module_el8.6.0+1087+b42c8331 qemu-kvm-block-gluster 6.0.0-33.el8s 6.2.0-5.module_el8.6.0+1087+b42c8331 qemu-kvm-block-iscsi 6.0.0-33.el8s 6.2.0-5.module_el8.6.0+1087+b42c8331 qemu-kvm-block-rbd 6.0.0-33.el8s 6.2.0-5.module_el8.6.0+1087+b42c8331 qemu-kvm-block-ssh 6.0.0-33.el8s 6.2.0-5.module_el8.6.0+1087+b42c8331 qemu-kvm-common 6.0.0-33.el8s 6.2.0-5.module_el8.6.0+1087+b42c8331 qemu-kvm-core 6.0.0-33.el8s 6.2.0-5.module_el8.6.0+1087+b42c8331 qemu-kvm-docs 6.0.0-33.el8s 6.2.0-5.module_el8.6.0+1087+b42c8331 qemu-kvm-hw-usbredir 6.0.0-33.el8s 6.2.0-5.module_el8.6.0+1087+b42c8331 qemu-kvm-ui-opengl 6.0.0-33.el8s 6.2.0-5.module_el8.6.0+1087+b42c8331 qemu-kvm-ui-spice 6.0.0-33.el8s 6.2.0-5.module_el8.6.0+1087+b42c8331 radvd 2.17-15.el8 rpm 4.14.3-21.el8 4.14.3-22.el8 rpm-build-libs 4.14.3-21.el8 4.14.3-22.el8 rpm-libs 4.14.3-21.el8 4.14.3-22.el8 rpm-plugin-selinux 4.14.3-21.el8 4.14.3-22.el8 samba-client-libs 4.15.4-0.el8 4.15.5-4.el8 samba-common 4.15.4-0.el8 4.15.5-4.el8 samba-common-libs 4.15.4-0.el8 4.15.5-4.el8 scap-security-guide 0.1.59-1.el8 0.1.60-7.el8 seabios-bin 1.14.0-1.module_el8.6.0+983+a7505f3f 1.15.0-1.module_el8.6.0+1087+b42c8331 seavgabios-bin 1.14.0-1.module_el8.6.0+983+a7505f3f 1.15.0-1.module_el8.6.0+1087+b42c8331 selinux-policy 3.14.3-89.el8 3.14.3-93.el8 selinux-policy-targeted 3.14.3-89.el8 3.14.3-93.el8 sos 4.2-13.el8 4.2-15.el8 swtpm 0.6.0-2.20210607gitea627b3.module_el8.6.0+983+a7505f3f 0.7.0-1.20211109gitb79fd91.module_el8.6.0+1087+b42c8331 swtpm-libs 0.6.0-2.20210607gitea627b3.module_el8.6.0+983+a7505f3f 0.7.0-1.20211109gitb79fd91.module_el8.6.0+1087+b42c8331 swtpm-tools 0.6.0-2.20210607gitea627b3.module_el8.6.0+983+a7505f3f 0.7.0-1.20211109gitb79fd91.module_el8.6.0+1087+b42c8331 systemd 239-56.el8 239-58.el8 systemd-container 239-56.el8 239-58.el8 systemd-libs 239-56.el8 239-58.el8 systemd-pam 239-56.el8 239-58.el8 systemd-udev 239-56.el8 239-58.el8 tuned 2.16.0-1.el8 2.18.0-2.el8 udisks2 2.9.0-7.el8 2.9.0-9.el8 util-linux 2.32.1-32.el8 2.32.1-34.el8 vdo 6.2.6.7-14.el8 6.2.6.14-14.el8 vim-minimal 8.0.1763-16.el8_5.4 8.0.1763-16.el8_5.12 yum 4.7.0-5.el8 4.7.0-7.el8 -- 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

CPU compatibility issues
by Adam Xu 03 Mar '22

03 Mar '22

Dear ovirt community, my cluster cpu type is "Intel Skylake Server Family" . I have 3 hosts with "Xeon Silver 4114" and 1 host with "Xeon Gold 5118", everything works ok. I try to add a new host with "Xeon Silver 4314" now. But it failed. error log: Host ovirt7 moved to Non-Operational state as host does not meet the cluster's minimum CPU level. Missing CPU features : model_Skylake-Server. How can I add the new host to cluster? Thanks.

2 2

Unable to access internet after installing ovirt 4.4.10
by louisb＠ameritech.net 03 Mar '22

03 Mar '22

I recently installed ovirt on my server that has four/4 network adapters. I recently installed ovirt on the server successfully; however; after the installation I've not been able to access the internet from the server. I have cockpit installed and I see that "ovirtmgmt" has taken control of the first network adapter. I three/3 remaining adapters left so I liked to just access the internet using one or all of the remaining network adapters. I can see using cockpit that there is a little receiving traffic taken place but no sending traffic. How do I get internet traffic going on one of the remaining network adapters? Could this be firewall issue? Thanks

1 0

I have so uploaded a new iso and then attach the iso to a new vm. But when I try to boot the vm I obtain this error
by Gangi Reddy 02 Mar '22

02 Mar '22

I have so uploaded a new iso and then attach the iso to a new vm. But when I try to boot the vm I obtain this error: booting from dvd/cd... boot failed: could not read from cdrom (code 0005) no bootable device Forum Solution: Find the location of the ISO image in the storage domain (search for the UUID in the file system) and re-copy the ISO over the top of the file. Just be 100% sure it's the ISO and not a VM disk (reference modification time, size etc). Once you replace the "uploaded" file with the ISO directly, everything works as expected. Kindly share detail steps on how to upload ISO image directly to Storage domain with UUID

1 0

Correct method to upload ISOs
by nroach44＠nroach44.id.au 02 Mar '22

02 Mar '22

As ISO domains are deprecated, what's the correct/modern procedure to upload ISOs to install / boot from? When I upload them to a data domain, they get converted into QCOW2 images (as confirmed by qemu-img info), but attached like ISOs to the qemu process. This means the VMs won't boot, until I manually overwrite the disk image on the datastore with the ISO directly (which works fine). My cluster started on 4.4 just after release, and is fully updated, if that changes things. Cheers, Nathaniel

2 3

VDSM command SetVolumeDescription failed every hours
by dvx.mellin＠gmail.com 02 Mar '22

02 Mar '22

Hi everyone, My configuration is 3 oVirt servers (CentOS Linux release 8.4.2105) with GlusterFS (glusterfs 8.6). Everything works well, but I have these errors appear every hours in the webgui of engine : WARN : Failed to update VMs/Templates OVF data for Storage Domain vmstore in Data Center Default. WARN : Failed to update OVF disks c2886e02-d0ea-4ff4-8f68-bf3e2ec684b7, OVF data isn't updated on those OVF stores (Data Center Default, Storage Domain vmstore). ERR : VDSM command SetVolumeDescriptionVDS failed: Could not acquire resource. Probably resource factory threw an exception.: () I guess it's related to these 4 messages in my engine.log : ./ovirt-engine/engine.log:2022-03-02 14:32:46,368+01 INFO [org.ovirt.engine.core.vdsbroker.irsbroker.SetVolumeDescriptionVDSCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-78) [7f7eee05] START, SetVolumeDescriptionVDSCommand( SetVolumeDescriptionVDSCommandParameters:{storagePoolId='a902d630-3674-11ec-8b5d-00163e388a46', ignoreFailoverLimit='false', storageDomainId='85b0066a-9dbb-4dfa-8359-5bf494c89c18', imageGroupId='c2886e02-d0ea-4ff4-8f68-bf3e2ec684b7', imageId='cde4b56e-645d-4f18-8eb1-a0ffb0c70599'}), log id: 41fdb7e1 ./ovirt-engine/engine.log:2022-03-02 14:32:46,368+01 INFO [org.ovirt.engine.core.vdsbroker.irsbroker.SetVolumeDescriptionVDSCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-78) [7f7eee05] ++ imageGroupGUID=c2886e02-d0ea-4ff4-8f68-bf3e2ec684b7 ./ovirt-engine/engine.log:2022-03-02 14:32:46,408+01 ERROR [org.ovirt.engine.core.vdsbroker.irsbroker.SetVolumeDescriptionVDSCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-78) [7f7eee05] Command 'SetVolumeDescriptionVDSCommand( SetVolumeDescriptionVDSCommandParameters:{storagePoolId='a902d630-3674-11ec-8b5d-00163e388a46', ignoreFailoverLimit='false', storageDomainId='85b0066a-9dbb-4dfa-8359-5bf494c89c18', imageGroupId='c2886e02-d0ea-4ff4-8f68-bf3e2ec684b7', imageId='cde4b56e-645d-4f18-8eb1-a0ffb0c70599'})' execution failed: IRSGenericException: IRSErrorException: Failed to SetVolumeDescriptionVDS, error = Could not acquire resource. Probably resource factory threw an exception.: (), code = 855 ./ovirt-engine/engine.log:2022-03-02 14:32:46,408+01 WARN [org.ovirt.engine.core.bll.storage.ovfstore.ProcessOvfUpdateForStorageDomainCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-78) [7f7eee05] failed to update domain '85b0066a-9dbb-4dfa-8359-5bf494c89c18' ovf store disk 'c2886e02-d0ea-4ff4-8f68-bf3e2ec684b7' ./ovirt-engine/engine.log:2022-03-02 14:32:46,416+01 WARN [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-78) [7f7eee05] EVENT_ID: UPDATE_FOR_OVF_STORES_FAILED(1,016), Failed to update OVF disks c2886e02-d0ea-4ff4-8f68-bf3e2ec684b7, OVF data isn't updated on those OVF stores (Data Center Default, Storage Domain vmstore). The disk which has the ID c2886e02-d0ea-4ff4-8f68-bf3e2ec684b7 is an OVF_STORE on one of my domains. Thanks for any help or advice and let me know if you need more informations. Best regards, Michael

1 0

Deleting Snapshot failed
by Jonathan Baecker 02 Mar '22

02 Mar '22

Hello everybody, last night my backup script was not able to finish the backup from a VM in the last step of deleting the snapshot. And now I also can not delete this snapshot by hand, the message says: VDSM onode2 command MergeVDS failed: Drive image file could not be found: {'driveSpec': {'poolID': 'c9baa5d4-3543-11eb-9c0c-00163e33f845', 'volumeID': '024e1844-c19b-40d8-a2ac-cb4ea6ec34e6', 'imageID': 'ad23c0db-1838-4f1f-811b-2b213d3a11cd', 'domainID': '3cf83851-1cc8-4f97-8960-08a60b9e25db'}, 'job': '96c7003f-e111-4270-b922-d9b215aaaea2', 'reason': 'Cannot find drive'} The full log you found in the attachment. Any idea? Best regard Jonathan

4 4

How to create a new Direct LUN with the API
by michael.wagenknecht＠continentale.de 02 Mar '22

02 Mar '22

Hi, I tried to create a new Fibre Channel Direct LUN with the API. But it doesn't work. My command is: curl -s \ --cacert '/etc/pki/ovirt-engine/ca.pem' \ --request POST \ --header 'Version: 4' \ --header 'Accept: application/xml' \ --user 'admin@internal:XXXXXXXXXX' \ --data ' <disk> <alias>DX600RZ2_OLVM_Test</alias> <name>DX600RZ2_OLVM_Test</name> <lun_storage> <type>fcp</type> <logical_units> <logical_unit id="3600000e00d2a0000002a0d15034d0000"> </logical_unit> </logical_units> </lun_storage> </disk> ' \ https://olvmmanager/ovirt-engine/api/disks I think there are parameter missing. But I can't find a working example. Please help. Best Regards, Michael

3 7

How I'd like to contribute
by Glen Jarvis 02 Mar '22

02 Mar '22

I am researching how to contribute to the oVirt community. I started here: https://www.ovirt.org/community/ And, I immediately saw to sign up for this email address and...send us an email saying how you would like to contribute. Visit our[mailing lists](https://lists.ovirt.org/archives/)page for other oVirt mailing lists to sign up for. My answers are: I want to be useful (and give more than I take). I can answer questions on mailing lists, help troubleshoot, write ovirt.ovirt Ansible collections, roles and custom modules. I am a seasoned Python programmer. My background: - Python programmer for 10+ years - I write custom Ansible modules, roles, playbook, etc. - Previous DBA for Informix (highly certified but who has heard of informix anymore). Postgres and Informix are cousins (both offspring from Ingres) - I have *some* rudimentary knowledge of Virtualization. However, I'm far from an expert - One of my favorite OS's is Qubes (an OS of virtual machines really) - I do a lot of technical training (writing materials and facilitating classes) - I work in an SRE / SysAd role at a large company that puts music in peoples ears (I'm hoping to move some of this from less SysAd and more SRE when with some of this oVirt stuff we're working on). My intermediate skills - I have bought a book on libvirt. But, it's still on my backlog. It feels that I'm always sucking an ocean through a straw so I have to pick and choose what I read next - My second favorite OS is Ubuntu as my main desktop (Qubes on separate computer for more secure stuff -- like crypto) - I'm just starting to use Virtual Machine Manager to run other OSs on Ubuntu My Oh-I-have-No-Idea skills: - things like luns, iSCSI and the `vdsm-tool config-lvm-filter` are making me pull my hair out. This is the reason I was frustrated enough to say "Let me join this community so I can learn more how this architecture works." - I work for a large company that has a RedHat support contract. We use RHV. I just wrote up this long descriptive case of the problem, uploaded sosreports, added as much detail as I could. But, it's crickets. If I knew more I could debug what was happening more myself. How did I do for an introduction? Cheers, Glen Jarvis

5 8

Invitation: oVirt 4.5.0 Alpha release test day @ Thu Mar 17, 2022 (users@ovirt.org)
by sbonazzo＠redhat.com 02 Mar '22

02 Mar '22

You have been invited to the following event. Title: oVirt 4.5.0 Alpha release test day If you're willing to help testing the release during the test daysplease join the oVirt development mailing list athttps://lists.ovirt.org/archives/list/devel@ovirt.org/ and report yourfeedback there.Instructions for installing oVirt 4.5.0 Alpha and oVirt 4.5.0 Beta fortesting will be added to the release pagehttps://www.ovirt.org/release/4.5.0/ when the corresponding versionwill be released. When: Thu Mar 17, 2022 Calendar: users(a)ovirt.org Who: (Guest list has been hidden at organizer's request) Event details: https://calendar.google.com/calendar/event?action=VIEW&eid=NnZ2Mzc1MWhjc2xv… Invitation from Google Calendar: https://calendar.google.com/calendar/ You are receiving this courtesy email at the account users(a)ovirt.org because you are an attendee of this event. To stop receiving future updates for this event, decline this event. Alternatively you can sign up for a Google account at https://calendar.google.com/calendar/ and control your notification settings for your entire calendar. Forwarding this invitation could allow any recipient to send a response to the organizer and be added to the guest list, or invite others regardless of their own invitation status, or to modify your RSVP. Learn more at https://support.google.com/calendar/answer/37135#forwarding

1 0

ovirt-4.4 morrors failing
by Ayansh Rocks 02 Mar '22

02 Mar '22

Hi All, Maximum mirrors are failing of ovirt-4.4 dependencies....what can be done here ? Error: Failed to download metadata for repo 'ovirt-4.4-centos-gluster8': Cannot prepare internal mirrorlist: No URLs in mirrorlist Errors during downloading metadata for repository 'ovirt-4.4-openstack-victoria': - Status code: 404 for http://mirror.centos.org/centos/8/cloud/x86_64/openstack-victoria/repodata/… (IP: 54.169.224.98) Error: Failed to download metadata for repo 'ovirt-4.4-openstack-victoria': Cannot download repomd.xml: Cannot download repodata/repomd.xml: All mirrors were tried Errors during downloading metadata for repository 'ovirt-4.4-centos-nfv-openvswitch': - Status code: 404 for http://mirror.centos.org/centos/8/nfv/x86_64/openvswitch-2/repodata/repomd.… (IP: 13.231.175.254) Error: Failed to download metadata for repo 'ovirt-4.4-centos-nfv-openvswitch': Cannot download repomd.xml: Cannot download repodata/repomd.xml: All mirrors were tried [root@iondelsvr12 yum.repos.d]# dnf install ovirt-hosted-engine-setup -y Ceph packages for x86_64 0.0 B/s | 0 B 00:00 Errors during downloading metadata for repository 'ovirt-4.4-centos-ceph-pacific': - Curl error (7): Couldn't connect to server for http://mirror.centos.org/centos/8/storage/x86_64/ceph-pacific/repodata/repo… [Failed to connect to mirror.centos.org port 80: Connection refused] Error: Failed to download metadata for repo 'ovirt-4.4-centos-ceph-pacific': Cannot download repomd.xml: Cannot download repodata/repomd.xml: All mirrors were tried

11 17

Re: VM Disk extend not reflected in VM oS
by Strahil Nikolov 27 Feb '22

27 Feb '22

Manually rescanning the scsi hosts is for new disks.The previous example 'echo 1 > .../rescan' should do the trick. Can we have the 'lsblk' & 'lsscsi' output ? Best Regards,Strahil Nikolov On Fri, Feb 25, 2022 at 18:53, Angus Clarke<angus(a)charworth.com> wrote: _______________________________________________ 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/4MOBAWODBQXMG…

1 0

[ANN] Schedule for oVirt 4.5.0
by Sandro Bonazzola 25 Feb '22

25 Feb '22

The oVirt development team leads are pleased to inform that the schedule for oVirt 4.5.0 has been finalized. The key dates follows: * Feature Freeze - String Freeze - Alpha release: 2022-03-15 * Alpha release test day: 2022-03-17 * Code freeze - Beta release: 2022-03-29 * Beta release test day: 2022-03-31 * General Availability release: 2022-04-12 A release management draft page has been created at: https://www.ovirt.org/release/4.5.0/ If you're willing to help testing the release during the test days please join the oVirt development mailing list at https://lists.ovirt.org/archives/list/devel@ovirt.org/ and report your feedback there. Instructions for installing oVirt 4.5.0 Alpha and oVirt 4.5.0 Beta for testing will be added to the release page https://www.ovirt.org/release/4.5.0/ when the corresponding version will be released. Professional Services, Integrators and Backup vendors: please plan a test session against your additional services, integrated solutions, downstream rebuilds, backup solution accordingly. If you're not listed here: https://ovirt.org/community/user-stories/users-and-providers.html consider adding your company there. If you're willing to help updating the localization for oVirt 4.5.0 please follow https://ovirt.org/develop/localization.html If you're willing to help promoting the oVirt 4.5.0 release you can submit your banner proposals for the oVirt home page and for the social media advertising at https://github.com/oVirt/ovirt-site/issues As an alternative please consider submitting a case study as in https://ovirt.org/community/user-stories/user-stories.html Feature owners: please start planning a presentation of your feature for oVirt Youtube channel: https://www.youtube.com/c/ovirtproject Do you want to contribute to getting ready for this release? Read more about oVirt community at https://ovirt.org/community/ and join the oVirt developers https://ovirt.org/develop/ Thanks, -- Sandro Bonazzola MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA sbonazzo(a)redhat.com Red Hat respects your work life balance. Therefore there is no need to answer this email out of your office hours.

2 5

Unable to migrate VMs to a newly upgraded Ovirt node host
by Giulio Casella 25 Feb '22

25 Feb '22

Hi guys, I just faced a problem after updating a host. I cannot migrate VM to updated host. Here's the error I see trying to migrate a VM to that host. Dec 16 10:13:11 host01.ovn.di.unimi.it systemd[1]: Starting Network Manager Script Dispatcher Service... Dec 16 10:13:11 host01.ovn.di.unimi.it libvirtd[5667]: Unable to read from monitor: Connection reset by peer Dec 16 10:13:11 host01.ovn.di.unimi.it libvirtd[5667]: internal error: qemu unexpectedly closed the monitor: 2021-12-16T10:13:00.447480Z qemu-kvm: -numa node,nodeid=0,cpus=0-15,mem=8192: warning: Parameter -numa node,mem is deprecated, use -numa node,memdev instead 2021-12-16T10:13:11.158057Z qemu-kvm: Failed to load pckbd:kbd 2021-12-16T10:13:11.158114Z qemu-kvm: error while loading state for instance 0x0 of device 'pckbd' 2021-12-16T10:13:11.158744Z qemu-kvm: load of migration failed: No such file or directory Dec 16 10:13:11 host01.ovn.xx.xxxxx.it kvm[35663]: 0 guests now active Instead I can start VM on that host, and migrate away VM from that host. Rolling back to ovirt-node-ng-4.4.9.1-0.20211207.0+1 via host console restores full functionality. The affected version is ovirt-node-ng-4.4.9.3-0.20211215.0+1 (and also previous one, I don't remember precisely, it was another async release). Any ideas? TIA, gc

3 2

Re: Migrate Hosted-Engine from one NFS mount to another NFS mount
by Sketch 24 Feb '22

24 Feb '22

On Wed, 23 Feb 2022, Matthew.Stier(a)fujitsu.com wrote: > I’ve always been told that migrating self-hosted-engine storage was a > backup, shutdown, and rebuild from backup procedure. > > In my iscsi environment it has never worked. (More due to the history of my > environment, than the procedure itself.) This didn't work for me either, though it may have had to do with the many issues I had moving from 4.3 to 4.4. What did work was backing up and restoring to a standalone engine. I had initially planned to migrate it back to a self-hosted setup later, but found that this setup is a lot less temperamental than the self-hosted engine. It also doesn't have to be a dedicated machine, it can be a VM hosted outside of oVirt, which may also be useful if you're hosting some stuff needed for bootstrapping the environment like DNS, NTP, etc. outside of oVirt.

3 2

Note about oVirt and Let's Encrypt SSL certs
by Chris Adams 24 Feb '22

24 Feb '22

I was setting up a new oVirt cluster yesterday, and deployed a Let's Encrypt SSL cert on it for the website. After that, I noticed that oVirt was getting errors synchronizing networks with ovirt-provider-ovn. It appears that the python library used for SSL by ovirt-provider-ovn has the same issue as older OpenSSL versions, and can't handle the default Let's Encrypt root cert path; the path used for old Android compatibility can end with an expired cert that's still in the CA store (even though there's another verification path that doesn't end with an expired cert). The solution was to switch the Let's Encrypt cert to the "ISRG Root X1" chain (which is fine, since I don't log in to oVirt from Android 7 devices). Just an FYI for anyone else using a Let's Encrypt cert (or other cert with a similar expired root path, they aren't the only one). -- Chris Adams <cma(a)cmadams.net>

1 0

Re: Gluster Performance issues
by Alex Morrison 24 Feb '22

24 Feb '22

Hello Sunil, [root@ovirt1 ~]# gluster --version glusterfs 8.6 same on all hosts On Wed, Feb 23, 2022 at 5:24 AM Sunil Kumar Heggodu Gopala Acharya < sheggodu(a)redhat.com> wrote: > Hi, > > Which version of gluster is in use? > > Regards, > > Sunil kumar Acharya > > Red Hat > > <https://www.redhat.com> > > T: +91-8067935170 <http://redhatemailsignature-marketing.itos.redhat.com/> > > <https://red.ht/sig> > TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> > > > > On Wed, Feb 23, 2022 at 2:17 PM Alex Morrison <alex(a)discoverygarden.ca> > wrote: > >> Hello All, >> >> We have 3 servers with a raid 50 array each, we are having extreme >> performance issues with our gluster, writes on gluster seem to take at >> least 3 times longer than on the raid directly. Can this be improved? I've >> read through several other performance issues threads but have been unable >> to make any improvements >> >> "gluster volume info" and "gluster volume profile vmstore info" is below >> >> >> ========================================================================================================================= >> >> -Inside Gluster - test took 35+ hours: >> [root@ovirt1 1801ed24-5b55-4431-9813-496143367f66]# bonnie++ -d . -s >> 600G -n 0 -m TEST -f -b -u root >> Using uid:0, gid:0. >> Writing intelligently...done >> Rewriting...done >> Reading intelligently...done >> start 'em...done...done...done...done...done... >> Version 1.98 ------Sequential Output------ --Sequential Input- >> --Random- >> -Per Chr- --Block-- -Rewrite- -Per Chr- --Block-- >> --Seeks-- >> Name:Size etc /sec %CP /sec %CP /sec %CP /sec %CP /sec %CP >> /sec %CP >> TEST 600G 35.7m 17 5824k 7 112m 13 >> 182.7 6 >> Latency 5466ms 12754ms 3499ms >> 1589ms >> >> >> 1.98,1.98,TEST,1,1644359706,600G,,8192,5,,,36598,17,5824,7,,,114950,13,182.7,6,,,,,,,,,,,,,,,,,,,5466ms,12754ms,,3499ms,1589ms,,,,,, >> >> >> ========================================================================================================================= >> >> -Outside Gluster - test took 18 minutes: >> [root@ovirt1 1801ed24-5b55-4431-9813-496143367f66]# bonnie++ -d . -s >> 600G -n 0 -m TEST -f -b -u root >> Using uid:0, gid:0. >> Writing intelligently...done >> Rewriting...done >> Reading intelligently...done >> start 'em...done...done...done...done...done... >> Version 1.98 ------Sequential Output------ --Sequential Input- >> --Random- >> -Per Chr- --Block-- -Rewrite- -Per Chr- --Block-- >> --Seeks-- >> Name:Size etc /sec %CP /sec %CP /sec %CP /sec %CP /sec %CP >> /sec %CP >> TEST 600G 567m 78 149m 30 307m 37 >> 83.0 57 >> Latency 205ms 4630ms 1450ms >> 679ms >> >> >> 1.98,1.98,TEST,1,1648288012,600G,,8192,5,,,580384,78,152597,30,,,314533,37,83.0,57,,,,,,,,,,,,,,,,,,,205ms,4630ms,,1450ms,679ms,,,,,, >> >> >> ========================================================================================================================= >> >> [root@ovirt1 1801ed24-5b55-4431-9813-496143367f66]# gluster volume info >> Volume Name: engine >> Type: Replicate >> Volume ID: 7ed15c5a-f054-450c-bac9-3ad1b4e5931b >> Status: Started >> Snapshot Count: 0 >> Number of Bricks: 1 x 3 = 3 >> Transport-type: tcp >> Bricks: >> Brick1: ovirt1-storage.dgi:/gluster_bricks/engine/engine >> Brick2: ovirt2-storage.dgi:/gluster_bricks/engine/engine >> Brick3: ovirt3-storage.dgi:/gluster_bricks/engine/engine >> Options Reconfigured: >> cluster.granular-entry-heal: enable >> performance.strict-o-direct: on >> network.ping-timeout: 30 >> storage.owner-gid: 36 >> storage.owner-uid: 36 >> server.event-threads: 4 >> client.event-threads: 4 >> cluster.choose-local: off >> user.cifs: off >> features.shard: on >> cluster.shd-wait-qlength: 10000 >> cluster.shd-max-threads: 8 >> cluster.locking-scheme: granular >> cluster.data-self-heal-algorithm: full >> cluster.server-quorum-type: server >> cluster.quorum-type: auto >> cluster.eager-lock: enable >> network.remote-dio: off >> performance.low-prio-threads: 32 >> performance.io-cache: off >> performance.read-ahead: off >> performance.quick-read: off >> transport.address-family: inet >> storage.fips-mode-rchecksum: on >> nfs.disable: on >> performance.client-io-threads: on >> diagnostics.latency-measurement: on >> diagnostics.count-fop-hits: on >> >> Volume Name: vmstore >> Type: Replicate >> Volume ID: 2670ff29-8d43-4610-a437-c6ec2c235753 >> Status: Started >> Snapshot Count: 0 >> Number of Bricks: 1 x 3 = 3 >> Transport-type: tcp >> Bricks: >> Brick1: ovirt1-storage.dgi:/gluster_bricks/vmstore/vmstore >> Brick2: ovirt2-storage.dgi:/gluster_bricks/vmstore/vmstore >> Brick3: ovirt3-storage.dgi:/gluster_bricks/vmstore/vmstore >> Options Reconfigured: >> cluster.granular-entry-heal: enable >> performance.strict-o-direct: on >> network.ping-timeout: 20 >> storage.owner-gid: 36 >> storage.owner-uid: 36 >> server.event-threads: 4 >> client.event-threads: 4 >> cluster.choose-local: off >> user.cifs: off >> features.shard: on >> cluster.shd-wait-qlength: 10000 >> cluster.shd-max-threads: 8 >> cluster.locking-scheme: granular >> cluster.data-self-heal-algorithm: full >> cluster.server-quorum-type: server >> cluster.quorum-type: auto >> cluster.eager-lock: enable >> network.remote-dio: off >> performance.low-prio-threads: 32 >> performance.io-cache: off >> performance.read-ahead: off >> performance.quick-read: off >> transport.address-family: inet >> storage.fips-mode-rchecksum: on >> nfs.disable: on >> performance.client-io-threads: on >> diagnostics.latency-measurement: on >> diagnostics.count-fop-hits: on >> server.tcp-user-timeout: 20 >> server.keepalive-time: 10 >> server.keepalive-interval: 2 >> server.keepalive-count: 5 >> cluster.lookup-optimize: off >> >> >> ========================================================================================================================= >> >> [root@ovirt1 ~]# gluster volume profile vmstore info >> Brick: ovirt1-storage.dgi:/gluster_bricks/vmstore/vmstore >> --------------------------------------------------------- >> Cumulative Stats: >> Block Size: 1b+ 4b+ >> 8b+ >> No. of Reads: 0 0 >> 0 >> No. of Writes: 4021 2 >> 64 >> >> Block Size: 64b+ 128b+ >> 256b+ >> No. of Reads: 0 134 >> 405 >> No. of Writes: 2 32 >> 119 >> >> Block Size: 512b+ 1024b+ >> 2048b+ >> No. of Reads: 2890 2617 >> 3059 >> No. of Writes: 113881 93551 >> 131776 >> >> Block Size: 4096b+ 8192b+ >> 16384b+ >> No. of Reads: 1096597 164931 >> 181569 >> No. of Writes: 41091001 20499776 >> 3230472 >> >> Block Size: 32768b+ 65536b+ >> 131072b+ >> No. of Reads: 212970 96574 >> 244017 >> No. of Writes: 1304688 991154 >> 3412866 >> >> Block Size: 262144b+ 524288b+ >> 1048576b+ >> No. of Reads: 0 0 >> 0 >> No. of Writes: 15 18 >> 65166 >> >> %-latency Avg-latency Min-Latency Max-Latency No. of calls >> Fop >> --------- ----------- ----------- ----------- ------------ >> ---- >> 0.00 0.00 us 0.00 us 0.00 us 6396 >> FORGET >> 0.00 0.00 us 0.00 us 0.00 us 189759 >> RELEASE >> 0.00 0.00 us 0.00 us 0.00 us 31292 >> RELEASEDIR >> 0.00 159.99 us 44.37 us 278.66 us 79 >> STAT >> 0.00 364.42 us 174.87 us 644.45 us 96 >> LINK >> 0.00 2714.10 us 203.53 us 47397.28 us 26 >> RMDIR >> 0.00 688.26 us 72.39 us 53857.63 us 186 >> SETXATTR >> 0.00 974.01 us 271.02 us 27298.52 us 176 >> RENAME >> 0.00 5254.64 us 159.48 us 84454.46 us 35 >> DISCARD >> 0.00 1133.84 us 86.47 us 87096.92 us 186 >> REMOVEXATTR >> 0.00 7907.47 us 221.82 us 182276.21 us 29 >> FALLOCATE >> 0.00 8304.51 us 311.89 us 42725.81 us 34 >> MKDIR >> 0.00 5758.19 us 296.39 us 21950.99 us 81 >> TRUNCATE >> 0.00 401.16 us 23.68 us 132668.93 us 3621 >> LK >> 0.00 545.48 us 14.22 us 1076517.76 us 6796 >> READDIR >> 0.00 2250.78 us 336.61 us 1071764.61 us 4257 >> CREATE >> 0.00 531.76 us 1.35 us 1723046.94 us 31292 >> OPENDIR >> 0.01 2058.67 us 196.74 us 1587752.27 us 21986 >> MKNOD >> 0.01 1241.28 us 22.61 us 1548642.70 us 52674 >> READDIRP >> 0.01 67508.32 us 100.01 us 3002069.81 us 1100 >> FTRUNCATE >> 0.01 412.74 us 10.94 us 5111334.35 us 209731 >> FLUSH >> 0.02 78668.59 us 183.06 us 3012629.87 us 1222 >> SETATTR >> 0.03 761.13 us 21.13 us 4611854.15 us 249094 >> STATFS >> 0.03 1132.33 us 45.51 us 3159531.87 us 185654 >> OPEN >> 0.03 2010.33 us 14.43 us 3158098.85 us 107824 >> GETXATTR >> 0.04 2765.29 us 61.38 us 3159208.13 us 100484 >> XATTROP >> 0.13 1367.04 us 51.46 us 8450420.87 us 595299 >> FSTAT >> 0.46 157440.90 us 47.62 us 13405712.93 us 18218 >> UNLINK >> 0.60 1274.67 us 19.60 us 11985005.14 us 2980806 >> LOOKUP >> 1.67 16645.99 us 12.80 us 6869488.64 us 631331 >> ENTRYLK >> 4.10 7504.86 us 39.52 us 11749528.82 us 3430506 >> READ >> 4.31 56942.36 us 16.57 us 23654127.65 us 475563 >> INODELK >> 6.09 660.89 us 11.02 us 20571410.32 us 57908331 >> FINODELK >> 20.59 1823.35 us 63.26 us 23639762.45 us 70934143 >> WRITE >> 25.70 2680.82 us 35.37 us 13636394.75 us 60223005 >> FXATTROP >> 36.14 3164.86 us 52.35 us 16805886.48 us 71739477 >> FSYNC >> 0.00 0.00 us 0.00 us 0.00 us 78458 >> UPCALL >> >> Duration: 404667 seconds >> Data Read: 59850935724 bytes >> Data Written: 1070158035683 bytes >> >> Interval 43 Stats: >> Block Size: 1b+ 256b+ >> 512b+ >> No. of Reads: 0 14 >> 3 >> No. of Writes: 12 4 >> 252 >> >> Block Size: 1024b+ 2048b+ >> 4096b+ >> No. of Reads: 0 0 >> 8105 >> No. of Writes: 100 34 >> 147355 >> >> Block Size: 8192b+ 16384b+ >> 32768b+ >> No. of Reads: 1559 1630 >> 1494 >> No. of Writes: 86013 17318 >> 8687 >> >> Block Size: 65536b+ 131072b+ >> No. of Reads: 532 764 >> No. of Writes: 8617 36317 >> %-latency Avg-latency Min-Latency Max-Latency No. of calls >> Fop >> --------- ----------- ----------- ----------- ------------ >> ---- >> 0.00 0.00 us 0.00 us 0.00 us 16 >> FORGET >> 0.00 0.00 us 0.00 us 0.00 us 665 >> RELEASE >> 0.00 0.00 us 0.00 us 0.00 us 52 >> RELEASEDIR >> 0.00 181.75 us 181.75 us 181.75 us 1 >> STAT >> 0.00 914.55 us 858.55 us 970.56 us 2 >> TRUNCATE >> 0.00 792.11 us 681.24 us 1051.32 us 4 >> RENAME >> 0.00 374.44 us 31.86 us 792.10 us 20 >> READDIR >> 0.00 399.48 us 306.97 us 562.69 us 28 >> UNLINK >> 0.00 752.40 us 636.14 us 907.29 us 16 >> CREATE >> 0.00 196.62 us 33.27 us 2586.77 us 336 >> GETXATTR >> 0.00 1107.98 us 288.51 us 29692.53 us 80 >> MKNOD >> 0.00 1074.80 us 74.41 us 2121.03 us 126 >> READDIRP >> 0.00 3119.52 us 3.17 us 157121.44 us 52 >> OPENDIR >> 0.01 972.14 us 21.72 us 329342.21 us 635 >> FLUSH >> 0.03 2122.15 us 31.97 us 377538.16 us 732 >> STATFS >> 0.06 4478.89 us 66.09 us 521289.10 us 649 >> OPEN >> 0.10 10273.00 us 88.19 us 478524.77 us 472 >> XATTROP >> 0.16 6969.92 us 16.14 us 385156.98 us 1138 >> ENTRYLK >> 0.20 4635.40 us 64.29 us 1098319.92 us 2097 >> FSTAT >> 0.65 4098.07 us 46.85 us 919617.66 us 7797 >> LOOKUP >> 2.36 87465.33 us 34.75 us 1224052.07 us 1317 >> INODELK >> 4.37 13897.55 us 57.89 us 1984970.27 us 15336 >> READ >> 5.24 1265.46 us 16.22 us 1638678.32 us 202165 >> FINODELK >> 21.05 3370.28 us 144.44 us 2264130.49 us 304724 >> WRITE >> 31.00 6411.68 us 39.84 us 2190355.42 us 235969 >> FXATTROP >> 34.75 6107.95 us 60.26 us 2270252.44 us 277643 >> FSYNC >> 0.00 0.00 us 0.00 us 0.00 us 368 >> UPCALL >> >> Duration: 1132 seconds >> Data Read: 292367566 bytes >> Data Written: 7495339692 bytes >> >> Brick: ovirt2-storage.dgi:/gluster_bricks/vmstore/vmstore >> --------------------------------------------------------- >> Cumulative Stats: >> Block Size: 1b+ 4b+ >> 8b+ >> No. of Reads: 0 0 >> 0 >> No. of Writes: 4802 2 >> 64 >> >> Block Size: 64b+ 128b+ >> 256b+ >> No. of Reads: 0 138 >> 828 >> No. of Writes: 2 32 >> 131 >> >> Block Size: 512b+ 1024b+ >> 2048b+ >> No. of Reads: 3595 4590 >> 6161 >> No. of Writes: 128976 99680 >> 132413 >> >> Block Size: 4096b+ 8192b+ >> 16384b+ >> No. of Reads: 930031 128995 >> 150468 >> No. of Writes: 48357551 23957030 >> 3689474 >> >> Block Size: 32768b+ 65536b+ >> 131072b+ >> No. of Reads: 154039 71949 >> 790010 >> No. of Writes: 1438859 1052045 >> 3715427 >> >> Block Size: 262144b+ 524288b+ >> 1048576b+ >> No. of Reads: 9 11 >> 40269 >> No. of Writes: 5 20 >> 50757 >> >> %-latency Avg-latency Min-Latency Max-Latency No. of calls >> Fop >> --------- ----------- ----------- ----------- ------------ >> ---- >> 0.00 0.00 us 0.00 us 0.00 us 7629 >> FORGET >> 0.00 0.00 us 0.00 us 0.00 us 228577 >> RELEASE >> 0.00 0.00 us 0.00 us 0.00 us 41524 >> RELEASEDIR >> 0.00 374.22 us 219.35 us 574.87 us 96 >> LINK >> 0.00 1712.22 us 164.90 us 22337.79 us 41 >> DISCARD >> 0.00 2840.25 us 245.24 us 46839.63 us 26 >> RMDIR >> 0.00 3660.92 us 229.86 us 86252.56 us 35 >> FALLOCATE >> 0.00 876.48 us 297.53 us 16685.63 us 188 >> RENAME >> 0.00 6660.10 us 379.21 us 52962.79 us 34 >> MKDIR >> 0.00 957.48 us 80.36 us 218059.88 us 355 >> REMOVEXATTR >> 0.00 1234.85 us 76.50 us 322955.27 us 355 >> SETXATTR >> 0.00 2326.62 us 84.07 us 250041.25 us 196 >> STAT >> 0.00 9660.45 us 289.50 us 295106.01 us 87 >> TRUNCATE >> 0.00 486.10 us 24.12 us 869966.79 us 5260 >> LK >> 0.00 453.69 us 18.32 us 426653.18 us 8135 >> READDIR >> 0.00 1832.38 us 296.61 us 261299.81 us 5050 >> CREATE >> 0.00 386.77 us 1.31 us 1300836.12 us 41524 >> OPENDIR >> 0.00 712.06 us 29.85 us 1441115.02 us 34874 >> READDIRP >> 0.01 1469.51 us 231.67 us 440065.71 us 22845 >> MKNOD >> 0.01 44229.36 us 75.58 us 1803963.42 us 871 >> FTRUNCATE >> 0.01 84433.20 us 149.47 us 3614869.24 us 1001 >> SETATTR >> 0.02 418.11 us 13.39 us 3515000.81 us 243820 >> FLUSH >> 0.03 1108.47 us 14.77 us 1658743.41 us 130647 >> GETXATTR >> 0.03 562.86 us 26.74 us 5043949.33 us 297799 >> STATFS >> 0.03 845.50 us 48.16 us 1998938.03 us 223680 >> OPEN >> 0.05 2236.13 us 56.08 us 5295998.22 us 120682 >> XATTROP >> 0.16 890.82 us 43.51 us 3653292.88 us 1012585 >> FSTAT >> 0.34 2974.20 us 12.92 us 7782497.74 us 642555 >> ENTRYLK >> 0.47 135831.21 us 70.35 us 11033867.90 us 19800 >> UNLINK >> 0.57 954.05 us 21.50 us 4553393.38 us 3414605 >> LOOKUP >> 1.79 14461.54 us 13.45 us 32841452.98 us 702915 >> INODELK >> 5.14 8014.78 us 40.70 us 5439109.56 us 3644063 >> READ >> 5.37 443.04 us 11.53 us 32863652.53 us 68909131 >> FINODELK >> 22.31 1780.31 us 33.59 us 11318712.62 us 71235991 >> FXATTROP >> 22.83 1571.16 us 74.86 us 32615055.19 us 82622840 >> WRITE >> 40.84 2762.75 us 52.77 us 8859115.35 us 84039509 >> FSYNC >> 0.00 0.00 us 0.00 us 0.00 us 95492 >> UPCALL >> >> Duration: 484169 seconds >> Data Read: 167149718723 bytes >> Data Written: 1177141649872 bytes >> >> Interval 43 Stats: >> Block Size: 1b+ 256b+ >> 512b+ >> No. of Reads: 0 6 >> 4 >> No. of Writes: 12 4 >> 252 >> >> Block Size: 1024b+ 2048b+ >> 4096b+ >> No. of Reads: 0 0 >> 5668 >> No. of Writes: 100 34 >> 147357 >> >> Block Size: 8192b+ 16384b+ >> 32768b+ >> No. of Reads: 1178 783 >> 1215 >> No. of Writes: 86014 17318 >> 8687 >> >> Block Size: 65536b+ 131072b+ >> No. of Reads: 264 4109 >> No. of Writes: 8617 36317 >> %-latency Avg-latency Min-Latency Max-Latency No. of calls >> Fop >> --------- ----------- ----------- ----------- ------------ >> ---- >> 0.00 0.00 us 0.00 us 0.00 us 16 >> FORGET >> 0.00 0.00 us 0.00 us 0.00 us 665 >> RELEASE >> 0.00 0.00 us 0.00 us 0.00 us 52 >> RELEASEDIR >> 0.00 866.18 us 849.57 us 882.78 us 2 >> TRUNCATE >> 0.00 1016.14 us 868.35 us 1182.48 us 4 >> RENAME >> 0.00 455.65 us 41.13 us 1679.37 us 20 >> READDIR >> 0.00 373.33 us 173.54 us 538.40 us 28 >> UNLINK >> 0.00 722.01 us 635.91 us 853.71 us 16 >> CREATE >> 0.00 335.52 us 38.15 us 1381.97 us 54 >> READDIRP >> 0.00 39218.92 us 214.34 us 78223.50 us 2 >> STAT >> 0.00 1730.77 us 2.59 us 84964.69 us 52 >> OPENDIR >> 0.00 1304.96 us 393.64 us 29724.09 us 80 >> MKNOD >> 0.01 422.75 us 22.85 us 134336.60 us 635 >> FLUSH >> 0.01 699.21 us 37.54 us 137813.64 us 732 >> STATFS >> 0.01 468.63 us 23.71 us 260961.83 us 1141 >> ENTRYLK >> 0.04 2041.83 us 69.80 us 163743.98 us 649 >> OPEN >> 0.08 1253.65 us 72.52 us 290508.15 us 2354 >> FSTAT >> 0.09 6913.19 us 69.01 us 212479.24 us 472 >> XATTROP >> 0.13 3558.26 us 32.70 us 195896.10 us 1317 >> INODELK >> 0.13 9793.37 us 36.11 us 212755.58 us 499 >> GETXATTR >> 0.34 1615.15 us 55.42 us 711310.28 us 7797 >> LOOKUP >> 4.92 13025.92 us 59.83 us 1061585.06 us 13884 >> READ >> 5.26 955.95 us 16.81 us 1069148.49 us 202174 >> FINODELK >> 23.28 2809.44 us 137.21 us 1134076.13 us 304713 >> WRITE >> 26.46 4124.05 us 43.30 us 1142167.27 us 235954 >> FXATTROP >> 39.23 5195.62 us 65.47 us 1250469.35 us 277632 >> FSYNC >> 0.00 0.00 us 0.00 us 0.00 us 365 >> UPCALL >> >> Duration: 1132 seconds >> Data Read: 668951066 bytes >> Data Written: 7495356076 bytes >> _______________________________________________ >> 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/G3G5HNX3P2Z5E… >> >

5 7

[Call to Action] oVirt 4.5 localization updated in zanata
by Sandro Bonazzola 24 Feb '22

24 Feb '22

Hi, https://zanata.ovirt.org/ has been updated with new text to be translated. If you want to help with this, please follow https://ovirt.org/develop/localization.html The ovirt-web-ui and ovirt-engine-ui-extensions projects lack Italian, Czech and Turkish translation. The oVirt engine project needs some touch on all the translations but especially on Italian, Czech, Russian and Turkish Thanks, -- Sandro Bonazzola MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA sbonazzo(a)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

Migrate Hosted-Engine from one NFS mount to another NFS mount
by Brian Ismay 24 Feb '22

24 Feb '22

Hello, I am currently running Ovirt 4.2.5.3-1.el7 with an Hosted-Engine running on nfs-based storage. I am needing to migrate the backend NFS store for the Hosted-Engine to a new share. Is there specific documentation for this procedure? I see multiple references to a general procedure involving backing-up the existing install and then re-installing and restoring the backup. Is there any way to make a more clean change of the configuration? Thanks, Brian Ismay

2 1

Re: VMs losing network interfaces
by Strahil Nikolov 23 Feb '22

23 Feb '22

That's a good start. Are you building your VMs from template ?Any chance there is another system (outside oVirt ?) with the same MAC ? you can run arping and check if you get response from more than 1 system. Best Regards,Strahil Nikolov On Mon, Feb 21, 2022 at 11:15, jb<jonbae77(a)gmail.com> wrote: Thank you Nikolov, I have descript the problem a bit wrong. In the UI is see the interface, with virsh dumpxml I get: <interface type='bridge'> <mac address='00:1a:4a:16:01:83'/> <source bridge='ovirtmgmt'/> <target dev='vnet9'/> <model type='virtio'/> <driver name='vhost' queues='4'/> <filterref filter='vdsm-no-mac-spoofing'/> <link state='up'/> <mtu size='1500'/> <alias name='ua-c8a50041-2d13-456d-acb6-b57fdaea434b'/> <address type='pci' domain='0x0000' bus='0x01' slot='0x00' function='0x0'/> </interface> lspci on the VM show also the interface and I can also bring the interface up again with: ifup enp1s0. So it only loose the connection, not the interface. When I restart the VM I get this log message: /var/log/syslog:Feb 21 10:11:29 tv-planer sh[391]: ifup: failed to bring up enp1s0 /var/log/syslog:Feb 21 10:11:29 tv-planer systemd[1]: ifup(a)enp1s0.service: Main process exited, code=exited, status=1/FAILURE /var/log/syslog:Feb 21 10:11:29 tv-planer systemd[1]: ifup(a)enp1s0.service: Failed with result 'exit-code'. But the VM got his IP and is reachable. Am 20.02.22 um 14:06 schrieb Strahil Nikolov: Do you see all nic in the UI ? What type are they ? Set this alias on the Hypervisors: alias virsh='virsh -c qemu:///system?authfile=/etc/ovirt-hosted-engine/virsh_auth.conf' and then use 'virsh dumpxml name-of-vm' to identify how many nics the vm has . If gou got the correct settings in ovirt, use 'lspci -vvvvv' . Best Regards, Strahil Nikolov On Sun, Feb 20, 2022 at 11:32, Jonathan Baecker <jonbae77(a)gmail.com> wrote: Hello everybody, I have here a strange behavior: We have a 3 node self hosted cluster with around 20 VMs running on it. Since longer I had the problem with one VM that after some days it lose the network interface. But because this VM was only for testing I was to lazy to dive more in, to figure out what is happen. Now I have a second VM, with the same problem and this VM is more important. Both VMs running debian 10 and use cifs mounts, so maybe that is related? Have some one of you seeing this behavior? And can give me a hint, how I can fix this? At the moment I can't provide a log file, because I didn't know the exact time, when this was happen. And I also don't know, if the problem comes from ovirt or from the operating system inside the VMs. Have a nice day! Jonathan _______________________________________________ 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/DOXZRQ55LFPNK…

2 4

hosted engine deployment (v4.4.10) - TASK Check engine VM health - fatal FAILED
by Charles Stellen 23 Feb '22

23 Feb '22

Dear Ovirt Hackers, sorry: incidently send to devel(a)ovitr.org we are dealing with hosted engine deployment issue on a fresh AMD EPYC servers: and we are ready to donate hardware to Ovirt community after we pass this issue ( :-) ) 0/ base infra: - 3 identical physical servers (produced in 2021-4Q) - fresh, clean and recent version of centos 8 stream installed (@^minimal-environment) - servers are interconnected with cisco switch, each other are network visible, all with nice internet access (NAT) 1/ storage: - all 3 servers/nodes host nice and clean glusterfs (v9.5) and volume "vol-images01" is ready for VM images - ovirt hosted engine deployment procedure: - easily accept mentioned glusterfs storage domain - mount it during "hosted-engine --deploy" with no issue - all permissions are set correctly at all glustrfs nodes ("chown vdsm.kvm vol-images01") - no issue with storage domain at all 2/ ovirt - hosted engine deployment: - all 3 servers successfully deployed recent ovirt version with standart procedure (on top of minimal install of centos 8 stream): dnf -y install ovirt-host virt-host-validate: PASS ALL - at first server we continue with: dnf -y install ovirt-engine-appliance hosted-engine --deploy (pure commandline - so no cockpit is used) DEPLOYMENT ISSUE: - during "hosted-engine --deploy" procedure - hosted engine becomes temporairly accessible at:https://server01:6900/ovirt-engine/ - with request to manualy set "ovirtmgmt" virtual nic - Hosts > server01 > Network Interfaces > [SETUP HOST NETWORKS] "ovirtmgmt" dropped to eno1 - [OK] - than All pass fine - and host "server01" becomes Active - back to commandline to Continue with deployment "Pause execution until /tmp/ansible.jksf4_n2_he_setup_lock is removed" by removing the lock file - deployment than pass all steps_until_ "[ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Check engine VM health]" ISSUE DETAILS: new VM becomes not accessible in the final stage - as it should be reachable at its final IP: [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Fail if Engine IP is different from engine's he_fqdn resolved IP] [ ERROR ] fatal: [localhost]: FAILED! => {"changed": false, "msg": "Engine VM IP address is while the engine's he_fqdn ovirt-engine.mgmt.pss.local resolves to 10.210.1.101. If you are using DHCP, check your DHCP reservation configuration"} - problem is, that even if we go with "Static" IP (provided during answering procedure) or with "DHCP" way (with properly set DHCP and DNS server responding with correct IP for both WE STUCK THERE WE TRYIED: - no success to connect to terminal/vnc of running VM "HostedEngine" to figure out the internal network issue any suggestion howto "connect" into newly deployed UP and RUNNING HostedEngine VM? to figure out eventually manualy fix the internal network issue? Thank You all for your help Charles Stellen PS: we are advanced in Ovirt deployment (from version 4.0), also we are advanced in GNU/Linux KVM based virtualisation for 10+ years, so any suggests or any details requested - WE ARE READY to provide online debuging or direct access to servers is not a problem PPS: after we pass this deployment - and after decomissioning procedure - we are ready to provide older HW to Ovirt community

6 14

how to convert centos 8 to centos 8 Stream
by Adam Xu 23 Feb '22

23 Feb '22

Dear ovirt community, I can't upgrade ovirt to version 4.4.10 because of EOL of centos8. How can we convert centos 8 to centos 8 stream? Thanks.

2 3