oVirt Node 4.4.8.2 Async update
by Sandro Bonazzola
oVirt Node 4.4.8.2 Async update
On September 1st 2021 the oVirt project released an async update for oVirt
Node consuming the following packages:
-
ovirt-release44 4.4.8.2
-
vdsm 4.40.80.6
oVirt Node respin also consumed most recent CentOS Stream and Advanced
Virtualization content.
It also includes fixes for:
-
CVE-2021-31535 <https://access.redhat.com/security/cve/CVE-2021-31535>
libX11: missing request length checks
-
CVE-2021-3564 <https://access.redhat.com/security/cve/CVE-2021-3564>
kernel: double free in bluetooth subsystem when the HCI device
initialization fails
-
CVE-2021-3573 <https://access.redhat.com/security/cve/CVE-2021-3573>
kernel: use-after-free in function hci_sock_bound_ioctl()
-
CVE-2021-29155 <https://access.redhat.com/security/cve/CVE-2021-29155>
kernel: protection for sequences of pointer arithmetic operations against
speculatively out-of-bounds loads can be bypassed to leak content of kernel
memory
-
CVE-2021-31829 <https://access.redhat.com/security/cve/CVE-2021-31829>
kernel: protection of stack pointer against speculative pointer arithmetic
can be bypassed to leak content of kernel memory
-
CVE-2021-33200 <https://access.redhat.com/security/cve/CVE-2021-33200>
kernel: out-of-bounds reads and writes due to enforcing incorrect limits
for pointer arithmetic operations by BPF verifier
-
CVE-2021-3679 <https://access.redhat.com/security/cve/CVE-2021-3679>
kernel: DoS in rb_per_cpu_empty()
-
CVE-2020-26144 <https://access.redhat.com/security/cve/CVE-2020-26144>
kernel: accepting unencrypted A-MSDU frames that start with RFC1042 header
-
CVE-2020-26145 <https://access.redhat.com/security/cve/CVE-2020-26145>
kernel: accepting plaintext broadcast fragments as full frames
-
CVE-2020-24587 <https://access.redhat.com/security/cve/CVE-2020-24587>
kernel: Reassembling fragments encrypted under different keys
-
CVE-2020-26141 <https://access.redhat.com/security/cve/CVE-2020-26141>
kernel: not verifying TKIP MIC of fragmented frames
-
CVE-2020-24586 <https://access.redhat.com/security/cve/CVE-2020-24586>
kernel: Fragmentation cache not cleared on reconnection
-
CVE-2020-26147 <https://access.redhat.com/security/cve/CVE-2020-26147>
kernel: reassembling mixed encrypted/plaintext fragments
-
CVE-2021-3653 <https://access.redhat.com/security/cve/CVE-2021-3653>
kernel: SVM nested virtualization issue in KVM (AVIC support)
-
CVE-2021-3656 <https://access.redhat.com/security/cve/CVE-2021-3656>
kernel: SVM nested virtualization issue in KVM (VMLOAD/VMSAVE)
Here’s the full list of changes:
--- ovirt-node-ng-image-4.4.8.1.manifest-rpm 2021-08-27 08:11:54.863736688
+0200
+++ ovirt-node-ng-image-4.4.8.2.manifest-rpm 2021-09-01 12:59:05.195037688
+0200
@@ -3,6 +3,6 @@
-NetworkManager-1.32.8-1.el8.x86_64
-NetworkManager-config-server-1.32.8-1.el8.noarch
-NetworkManager-libnm-1.32.8-1.el8.x86_64
-NetworkManager-ovs-1.32.8-1.el8.x86_64
-NetworkManager-team-1.32.8-1.el8.x86_64
-NetworkManager-tui-1.32.8-1.el8.x86_64
+NetworkManager-1.32.10-2.el8.x86_64
+NetworkManager-config-server-1.32.10-2.el8.noarch
+NetworkManager-libnm-1.32.10-2.el8.x86_64
+NetworkManager-ovs-1.32.10-2.el8.x86_64
+NetworkManager-team-1.32.10-2.el8.x86_64
+NetworkManager-tui-1.32.10-2.el8.x86_64
@@ -24 +24 @@
-ansible-2.9.24-2.el8.noarch
+ansible-2.9.25-1.el8.noarch
@@ -39,5 +39,5 @@
-bind-export-libs-9.11.26-4.el8_4.x86_64
-bind-libs-9.11.26-4.el8_4.x86_64
-bind-libs-lite-9.11.26-4.el8_4.x86_64
-bind-license-9.11.26-4.el8_4.noarch
-bind-utils-9.11.26-4.el8_4.x86_64
+bind-export-libs-9.11.26-6.el8.x86_64
+bind-libs-9.11.26-6.el8.x86_64
+bind-libs-lite-9.11.26-6.el8.x86_64
+bind-license-9.11.26-6.el8.noarch
+bind-utils-9.11.26-6.el8.x86_64
@@ -46 +46 @@
-blivet-data-3.4.0-4.el8.noarch
+blivet-data-3.4.0-5.el8.noarch
@@ -68,2 +68,2 @@
-cockpit-250-1.el8.x86_64
-cockpit-bridge-250-1.el8.x86_64
+cockpit-251-1.el8.x86_64
+cockpit-bridge-251-1.el8.x86_64
@@ -71,3 +71,3 @@
-cockpit-storaged-250-1.el8.noarch
-cockpit-system-250-1.el8.noarch
-cockpit-ws-250-1.el8.x86_64
+cockpit-storaged-251-1.el8.noarch
+cockpit-system-251-1.el8.noarch
+cockpit-ws-251-1.el8.x86_64
@@ -94 +94 @@
-curl-7.61.1-18.el8_4.1.x86_64
+curl-7.61.1-21.el8.x86_64
@@ -118,2 +118,2 @@
-dnf-4.7.0-2.el8.noarch
-dnf-data-4.7.0-2.el8.noarch
+dnf-4.7.0-3.el8.noarch
+dnf-data-4.7.0-3.el8.noarch
@@ -123,5 +123,5 @@
-dracut-049-188.git20210802.el8.x86_64
-dracut-config-generic-049-188.git20210802.el8.x86_64
-dracut-live-049-188.git20210802.el8.x86_64
-dracut-network-049-188.git20210802.el8.x86_64
-dracut-squash-049-188.git20210802.el8.x86_64
+dracut-049-190.git20210811.el8.x86_64
+dracut-config-generic-049-190.git20210811.el8.x86_64
+dracut-live-049-190.git20210811.el8.x86_64
+dracut-network-049-190.git20210811.el8.x86_64
+dracut-squash-049-190.git20210811.el8.x86_64
@@ -138 +138 @@
-ethtool-5.8-6.el8.x86_64
+ethtool-5.8-7.el8.x86_64
@@ -184 +184 @@
-fontconfig-2.13.1-3.el8.x86_64
+fontconfig-2.13.1-4.el8.x86_64
@@ -188 +188 @@
-fstrm-0.6.0-3.el8.1.x86_64
+fstrm-0.6.1-2.el8.x86_64
@@ -206,3 +206,3 @@
-glibc-2.28-162.el8.x86_64
-glibc-common-2.28-162.el8.x86_64
-glibc-langpack-en-2.28-162.el8.x86_64
+glibc-2.28-164.el8.x86_64
+glibc-common-2.28-164.el8.x86_64
+glibc-langpack-en-2.28-164.el8.x86_64
@@ -240 +240 @@
-grubby-8.40-41.el8.x86_64
+grubby-8.40-42.el8.x86_64
@@ -249 +249 @@
-hivex-1.3.18-21.module_el8.5.0+821+97472045.x86_64
+hivex-1.3.18-22.el8s.x86_64
@@ -251 +251 @@
-hwdata-0.314-8.9.el8.noarch
+hwdata-0.314-8.10.el8.noarch
@@ -265,2 +265,2 @@
-iproute-5.12.0-2.el8.x86_64
-iproute-tc-5.12.0-2.el8.x86_64
+iproute-5.12.0-3.el8.x86_64
+iproute-tc-5.12.0-3.el8.x86_64
@@ -270,3 +270,3 @@
-iptables-1.8.4-19.el8.x86_64
-iptables-ebtables-1.8.4-19.el8.x86_64
-iptables-libs-1.8.4-19.el8.x86_64
+iptables-1.8.4-20.el8.x86_64
+iptables-ebtables-1.8.4-20.el8.x86_64
+iptables-libs-1.8.4-20.el8.x86_64
@@ -301,6 +301,6 @@
-kernel-4.18.0-331.el8.x86_64
-kernel-core-4.18.0-331.el8.x86_64
-kernel-modules-4.18.0-331.el8.x86_64
-kernel-tools-4.18.0-331.el8.x86_64
-kernel-tools-libs-4.18.0-331.el8.x86_64
-kexec-tools-2.0.20-56.el8.x86_64
+kernel-4.18.0-338.el8.x86_64
+kernel-core-4.18.0-338.el8.x86_64
+kernel-modules-4.18.0-338.el8.x86_64
+kernel-tools-4.18.0-338.el8.x86_64
+kernel-tools-libs-4.18.0-338.el8.x86_64
+kexec-tools-2.0.20-57.el8.x86_64
@@ -313,2 +313,2 @@
-krb5-libs-1.18.2-13.el8.x86_64
-krb5-workstation-1.18.2-13.el8.x86_64
+krb5-libs-1.18.2-14.el8.x86_64
+krb5-workstation-1.18.2-14.el8.x86_64
@@ -318,3 +318,3 @@
-libX11-1.6.8-4.el8.x86_64
-libX11-common-1.6.8-4.el8.noarch
-libX11-xcb-1.6.8-4.el8.x86_64
+libX11-1.6.8-5.el8.x86_64
+libX11-common-1.6.8-5.el8.noarch
+libX11-xcb-1.6.8-5.el8.x86_64
@@ -353 +353 @@
-libbpf-0.3.0-1.el8.x86_64
+libbpf-0.4.0-1.el8.x86_64
@@ -363 +363 @@
-libcurl-7.61.1-18.el8_4.1.x86_64
+libcurl-7.61.1-21.el8.x86_64
@@ -407 +407 @@
-libkadm5-1.18.2-13.el8.x86_64
+libkadm5-1.18.2-14.el8.x86_64
@@ -418 +418 @@
-libmodulemd-2.12.1-1.el8.x86_64
+libmodulemd-2.13.0-1.el8.x86_64
@@ -465 +465 @@
-libsepol-2.9-2.el8.x86_64
+libsepol-2.9-3.el8.x86_64
@@ -503,24 +503,24 @@
-libvirt-7.5.0-1.el8s.x86_64
-libvirt-client-7.5.0-1.el8s.x86_64
-libvirt-daemon-7.5.0-1.el8s.x86_64
-libvirt-daemon-config-network-7.5.0-1.el8s.x86_64
-libvirt-daemon-config-nwfilter-7.5.0-1.el8s.x86_64
-libvirt-daemon-driver-interface-7.5.0-1.el8s.x86_64
-libvirt-daemon-driver-network-7.5.0-1.el8s.x86_64
-libvirt-daemon-driver-nodedev-7.5.0-1.el8s.x86_64
-libvirt-daemon-driver-nwfilter-7.5.0-1.el8s.x86_64
-libvirt-daemon-driver-qemu-7.5.0-1.el8s.x86_64
-libvirt-daemon-driver-secret-7.5.0-1.el8s.x86_64
-libvirt-daemon-driver-storage-7.5.0-1.el8s.x86_64
-libvirt-daemon-driver-storage-core-7.5.0-1.el8s.x86_64
-libvirt-daemon-driver-storage-disk-7.5.0-1.el8s.x86_64
-libvirt-daemon-driver-storage-gluster-7.5.0-1.el8s.x86_64
-libvirt-daemon-driver-storage-iscsi-7.5.0-1.el8s.x86_64
-libvirt-daemon-driver-storage-iscsi-direct-7.5.0-1.el8s.x86_64
-libvirt-daemon-driver-storage-logical-7.5.0-1.el8s.x86_64
-libvirt-daemon-driver-storage-mpath-7.5.0-1.el8s.x86_64
-libvirt-daemon-driver-storage-rbd-7.5.0-1.el8s.x86_64
-libvirt-daemon-driver-storage-scsi-7.5.0-1.el8s.x86_64
-libvirt-daemon-kvm-7.5.0-1.el8s.x86_64
-libvirt-libs-7.5.0-1.el8s.x86_64
-libvirt-lock-sanlock-7.5.0-1.el8s.x86_64
+libvirt-7.6.0-2.el8s.x86_64
+libvirt-client-7.6.0-2.el8s.x86_64
+libvirt-daemon-7.6.0-2.el8s.x86_64
+libvirt-daemon-config-network-7.6.0-2.el8s.x86_64
+libvirt-daemon-config-nwfilter-7.6.0-2.el8s.x86_64
+libvirt-daemon-driver-interface-7.6.0-2.el8s.x86_64
+libvirt-daemon-driver-network-7.6.0-2.el8s.x86_64
+libvirt-daemon-driver-nodedev-7.6.0-2.el8s.x86_64
+libvirt-daemon-driver-nwfilter-7.6.0-2.el8s.x86_64
+libvirt-daemon-driver-qemu-7.6.0-2.el8s.x86_64
+libvirt-daemon-driver-secret-7.6.0-2.el8s.x86_64
+libvirt-daemon-driver-storage-7.6.0-2.el8s.x86_64
+libvirt-daemon-driver-storage-core-7.6.0-2.el8s.x86_64
+libvirt-daemon-driver-storage-disk-7.6.0-2.el8s.x86_64
+libvirt-daemon-driver-storage-gluster-7.6.0-2.el8s.x86_64
+libvirt-daemon-driver-storage-iscsi-7.6.0-2.el8s.x86_64
+libvirt-daemon-driver-storage-iscsi-direct-7.6.0-2.el8s.x86_64
+libvirt-daemon-driver-storage-logical-7.6.0-2.el8s.x86_64
+libvirt-daemon-driver-storage-mpath-7.6.0-2.el8s.x86_64
+libvirt-daemon-driver-storage-rbd-7.6.0-2.el8s.x86_64
+libvirt-daemon-driver-storage-scsi-7.6.0-2.el8s.x86_64
+libvirt-daemon-kvm-7.6.0-2.el8s.x86_64
+libvirt-libs-7.6.0-2.el8s.x86_64
+libvirt-lock-sanlock-7.6.0-2.el8s.x86_64
@@ -546,2 +546,2 @@
-lldpad-1.0.1-14.git036e314.el8.x86_64
-llvm-libs-12.0.0-1.module_el8.5.0+840+21214faf.x86_64
+lldpad-1.0.1-16.git036e314.el8.x86_64
+llvm-libs-12.0.1-1.module_el8.5.0+892+54d791e1.x86_64
@@ -553 +553 @@
-lsscsi-0.32-2.el8.x86_64
+lsscsi-0.32-3.el8.x86_64
@@ -555 +555 @@
-lua-libs-5.3.4-11.el8.x86_64
+lua-libs-5.3.4-12.el8.x86_64
@@ -603 +603 @@
-nftables-0.9.3-20.el8.x86_64
+nftables-0.9.3-21.el8.x86_64
@@ -605 +605 @@
-nmap-ncat-7.70-5.el8.x86_64
+nmap-ncat-7.70-6.el8.x86_64
@@ -609 +609 @@
-nspr-4.31.0-1.el8_4.x86_64
+nspr-4.32.0-1.el8_4.x86_64
@@ -636 +636 @@
-os-prober-1.74-6.el8.x86_64
+os-prober-1.74-9.el8.x86_64
@@ -648 +648 @@
-ovirt-node-ng-image-update-placeholder-4.4.8.1-1.el8.noarch
+ovirt-node-ng-image-update-placeholder-4.4.8.2-1.el8.noarch
@@ -656,2 +656,2 @@
-ovirt-release-host-node-4.4.8.1-1.el8.noarch
-ovirt-release44-4.4.8.1-1.el8.noarch
+ovirt-release-host-node-4.4.8.2-1.el8.noarch
+ovirt-release44-4.4.8.2-1.el8.noarch
@@ -664,3 +664,3 @@
-pacemaker-cluster-libs-2.1.0-6.el8.x86_64
-pacemaker-libs-2.1.0-6.el8.x86_64
-pacemaker-schemas-2.1.0-6.el8.noarch
+pacemaker-cluster-libs-2.1.0-8.el8.x86_64
+pacemaker-libs-2.1.0-8.el8.x86_64
+pacemaker-schemas-2.1.0-8.el8.noarch
@@ -715 +715 @@
-platform-python-3.6.8-39.el8.x86_64
+platform-python-3.6.8-40.el8.x86_64
@@ -718,3 +718,3 @@
-plymouth-0.9.4-9.20200615git1e36e30.el8.x86_64
-plymouth-core-libs-0.9.4-9.20200615git1e36e30.el8.x86_64
-plymouth-scripts-0.9.4-9.20200615git1e36e30.el8.x86_64
+plymouth-0.9.4-10.20200615git1e36e30.el8.x86_64
+plymouth-core-libs-0.9.4-10.20200615git1e36e30.el8.x86_64
+plymouth-scripts-0.9.4-10.20200615git1e36e30.el8.x86_64
@@ -744,2 +744,2 @@
-python3-bind-9.11.26-4.el8_4.noarch
-python3-blivet-3.4.0-4.el8.noarch
+python3-bind-9.11.26-6.el8.noarch
+python3-blivet-3.4.0-5.el8.noarch
@@ -753 +753 @@
-python3-cloud-what-1.28.20-1.el8.x86_64
+python3-cloud-what-1.28.21-2.el8.x86_64
@@ -762 +762 @@
-python3-dnf-4.7.0-2.el8.noarch
+python3-dnf-4.7.0-3.el8.noarch
@@ -797 +797 @@
-python3-libs-3.6.8-39.el8.x86_64
+python3-libs-3.6.8-40.el8.x86_64
@@ -800 +800 @@
-python3-libvirt-7.5.0-1.el8s.x86_64
+python3-libvirt-7.6.0-1.el8s.x86_64
@@ -811 +811 @@
-python3-nftables-0.9.3-20.el8.x86_64
+python3-nftables-0.9.3-21.el8.x86_64
@@ -834 +834 @@
-python3-perf-4.18.0-331.el8.x86_64
+python3-perf-4.18.0-338.el8.x86_64
@@ -864 +864 @@
-python3-rpm-4.14.3-15.el8.x86_64
+python3-rpm-4.14.3-18.el8.x86_64
@@ -876 +876 @@
-python3-subscription-manager-rhsm-1.28.20-1.el8.x86_64
+python3-subscription-manager-rhsm-1.28.21-2.el8.x86_64
@@ -878 +878 @@
-python3-syspurpose-1.28.20-1.el8.x86_64
+python3-syspurpose-1.28.21-2.el8.x86_64
@@ -889,15 +889,15 @@
-python36-3.6.8-37.module_el8.5.0+771+e5d9a225.x86_64
-qemu-guest-agent-6.0.0-26.el8s.x86_64
-qemu-img-6.0.0-26.el8s.x86_64
-qemu-kvm-6.0.0-26.el8s.x86_64
-qemu-kvm-block-curl-6.0.0-26.el8s.x86_64
-qemu-kvm-block-gluster-6.0.0-26.el8s.x86_64
-qemu-kvm-block-iscsi-6.0.0-26.el8s.x86_64
-qemu-kvm-block-rbd-6.0.0-26.el8s.x86_64
-qemu-kvm-block-ssh-6.0.0-26.el8s.x86_64
-qemu-kvm-common-6.0.0-26.el8s.x86_64
-qemu-kvm-core-6.0.0-26.el8s.x86_64
-qemu-kvm-docs-6.0.0-26.el8s.x86_64
-qemu-kvm-hw-usbredir-6.0.0-26.el8s.x86_64
-qemu-kvm-ui-opengl-6.0.0-26.el8s.x86_64
-qemu-kvm-ui-spice-6.0.0-26.el8s.x86_64
+python36-3.6.8-38.module_el8.5.0+895+a459eca8.x86_64
+qemu-guest-agent-6.0.0-27.el8s.x86_64
+qemu-img-6.0.0-27.el8s.x86_64
+qemu-kvm-6.0.0-27.el8s.x86_64
+qemu-kvm-block-curl-6.0.0-27.el8s.x86_64
+qemu-kvm-block-gluster-6.0.0-27.el8s.x86_64
+qemu-kvm-block-iscsi-6.0.0-27.el8s.x86_64
+qemu-kvm-block-rbd-6.0.0-27.el8s.x86_64
+qemu-kvm-block-ssh-6.0.0-27.el8s.x86_64
+qemu-kvm-common-6.0.0-27.el8s.x86_64
+qemu-kvm-core-6.0.0-27.el8s.x86_64
+qemu-kvm-docs-6.0.0-27.el8s.x86_64
+qemu-kvm-hw-usbredir-6.0.0-27.el8s.x86_64
+qemu-kvm-ui-opengl-6.0.0-27.el8s.x86_64
+qemu-kvm-ui-spice-6.0.0-27.el8s.x86_64
@@ -912,4 +912,4 @@
-rpm-4.14.3-15.el8.x86_64
-rpm-build-libs-4.14.3-15.el8.x86_64
-rpm-libs-4.14.3-15.el8.x86_64
-rpm-plugin-selinux-4.14.3-15.el8.x86_64
+rpm-4.14.3-18.el8.x86_64
+rpm-build-libs-4.14.3-18.el8.x86_64
+rpm-libs-4.14.3-18.el8.x86_64
+rpm-plugin-selinux-4.14.3-18.el8.x86_64
@@ -928,3 +928,3 @@
-sbd-1.4.2-2.el8.x86_64
-scap-security-guide-0.1.57-1.el8.noarch
-scrub-2.5.2-14.el8.x86_64
+sbd-1.5.0-2.el8.x86_64
+scap-security-guide-0.1.57-4.el8.noarch
+scrub-2.5.2-16.el8.x86_64
@@ -934,2 +934,2 @@
-selinux-policy-3.14.3-76.el8.noarch
-selinux-policy-targeted-3.14.3-76.el8.noarch
+selinux-policy-3.14.3-78.el8.noarch
+selinux-policy-targeted-3.14.3-78.el8.noarch
@@ -961 +961 @@
-subscription-manager-rhsm-certificates-1.28.20-1.el8.x86_64
+subscription-manager-rhsm-certificates-1.28.21-2.el8.x86_64
@@ -973,5 +973,5 @@
-systemd-239-49.el8.x86_64
-systemd-container-239-49.el8.x86_64
-systemd-libs-239-49.el8.x86_64
-systemd-pam-239-49.el8.x86_64
-systemd-udev-239-49.el8.x86_64
+systemd-239-50.el8.x86_64
+systemd-container-239-50.el8.x86_64
+systemd-libs-239-50.el8.x86_64
+systemd-pam-239-50.el8.x86_64
+systemd-udev-239-50.el8.x86_64
@@ -993,11 +993,11 @@
-vdo-6.2.5.65-14.el8.x86_64
-vdsm-4.40.80.5-1.el8.x86_64
-vdsm-api-4.40.80.5-1.el8.noarch
-vdsm-client-4.40.80.5-1.el8.noarch
-vdsm-common-4.40.80.5-1.el8.noarch
-vdsm-gluster-4.40.80.5-1.el8.x86_64
-vdsm-http-4.40.80.5-1.el8.noarch
-vdsm-jsonrpc-4.40.80.5-1.el8.noarch
-vdsm-network-4.40.80.5-1.el8.x86_64
-vdsm-python-4.40.80.5-1.el8.noarch
-vdsm-yajsonrpc-4.40.80.5-1.el8.noarch
+vdo-6.2.5.74-14.el8.x86_64
+vdsm-4.40.80.6-1.el8.x86_64
+vdsm-api-4.40.80.6-1.el8.noarch
+vdsm-client-4.40.80.6-1.el8.noarch
+vdsm-common-4.40.80.6-1.el8.noarch
+vdsm-gluster-4.40.80.6-1.el8.x86_64
+vdsm-http-4.40.80.6-1.el8.noarch
+vdsm-jsonrpc-4.40.80.6-1.el8.noarch
+vdsm-network-4.40.80.6-1.el8.x86_64
+vdsm-python-4.40.80.6-1.el8.noarch
+vdsm-yajsonrpc-4.40.80.6-1.el8.noarch
@@ -1021 +1021 @@
-yum-4.7.0-2.el8.noarch
+yum-4.7.0-3.el8.noarch
--
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.*
11 months, 2 weeks
Re: [ovirt-devel] VM timezone typo
by Arik Hadas
On Wed, Sep 1, 2021 at 5:09 AM luwen.zhang <luwen.zhang(a)vinchin.com> wrote:
>
> Hello team,
>
> We found a minor issue on oVirt 4.4.8 version, it seems like a typo of the
> VM timezone, it should be “GMT+01:00 Central European Standard Time” but on
> 4.4.8 it’s “GMT+01:00 Central European Standard Tim”.
> This lead to Vinchin VM restoration fail at VM creation stage if using VM
> backups from previous oVirt versions.
>
>
> We had adjusted our programing to deal with this specific issue, but hope
> it can be fix soon.
>
Thanks for reporting this issue
We've already merged a fix for that (
https://gerrit.ovirt.org/#/c/ovirt-engine/+/116260/)
A possible way to resolve this before the aforementioned fix is available
is to fix the typo in
/usr/share/ovirt-engine/conf/timezones-defaults.properties (changes will be
overridden when updating ovirt-engine) or adding "Europe/Warsaw=Central
European Standard Time" to a new configuration
in /etc/ovirt-engine/timezones/ (see
https://github.com/oVirt/ovirt-site/pull/2554/files)
> Thanks & regards!
>
>
> *Luwen Zhang* | Product Manager
>
> *Mobile*: +8613880424687 | *Skype*: luwen.zhang_cn
>
> *WhatsApp*: +8613880424687 | *WeChat*: +8613880424687
>
> *Website*: www.vinchin.com
>
> *Address*: F5, Block 8, National Information Security Industry Park,
>
> No.333 Yunhua Road, Hi-tech Zone, Chengdu, China | *Zip*: 610015
>
> *INNOVATIVE VM BACKUP EXPERT*
>
> VMware Backup <https://www.vinchin.com/en/hypervisor/vmware-backup.html>
> | XenServer/Citrix Hypervisor/XCP-ng Backup
> <https://www.vinchin.com/en/hypervisor/xcp-ng-xenserver-backup.html> | Hyper-V
> Backup <https://www.vinchin.com/en/hypervisor/hyper-v-backup.html>
>
> RHEV/oVirt Backup
> <https://www.vinchin.com/en/hypervisor/red-hat-virtualization-ovirt-backup...>
> | OLVM Backup
> <https://www.vinchin.com/en/hypervisor/oracle-linux-virtualization-manager...>
> | Sangfor HCI Backup
> <https://www.vinchin.com/en/hypervisor/sangfor-hci-backup.html> | OpenStack
> Backup <https://www.vinchin.com/en/hypervisor/openstack-backup.html>
>
> _______________________________________________
> Devel mailing list -- devel(a)ovirt.org
> To unsubscribe send an email to devel-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/devel@ovirt.org/message/42KMIMK6CKK...
>
11 months, 2 weeks
Extending iSCSI storage domain
by Répás Péter
Hello,
I have an oVirt 4.1.1 installion with 2 nodes and an ovirt manager on a serpate machine.
I have multiple storage domain on an external storage, one contains the disk images of VMs, and another is a huge storage domain dedicated to store mediafiles. The mediafile storage domain has only one disk image, attached to a linux vm, no other disk image on this mediafile storage domain. The mediafile storage domain is attached and available to both ovirt nodes.
This media storage domain has to be extended. The storage device has the capacity, so it is going to be extended.
What should be done on the oVirt side to extend the media storage domain?
Sorry for the lame question but the docs and tips from the web are ambiguous for me, some say it cannot be extended, just add a new lun to this storage domain. Does this operation need the full cluster to be put maintenance and stop all vms? Or just the linux vm to that is the disk image is attached to?
Thank you for your help!
Regards,
Peter
11 months, 2 weeks
ovirt go sdk
by Nikita Zubarev
Hello.
I need help creating a virtual machine using
https://github.com/oVirt/go-ovirt
I need set cmdline vm , Please help me
my create vm configuration, but cmd not set
[image: image.png]
Vm(
ovirtsdk4.NewVmBuilder().
Name(*name).
Console(
ovirtsdk4.NewConsoleBuilder().
Enabled(true).
MustBuild()).
Memory(ram2 * int64(1<<30)).
MemoryPolicy(
ovirtsdk4.NewMemoryPolicyBuilder().
Guaranteed(int64(ram2) * int64(1<<30)).
Max(int64(ram2) * 2 * int64(1<<30)).
Ballooning(true).
MustBuild()).
// Memory(int64(ram2) * int64(1<<30)).
Os(
ovirtsdk4.NewOperatingSystemBuilder().
CustomKernelCmdline("qemu_cmdline").Cmdline("qemu_cmdline").Boot(
ovirtsdk4.NewBootBuilder().
DevicesOfAny(
ovirtsdk4.BOOTDEVICE_NETWORK,
ovirtsdk4.BOOTDEVICE_HD).
MustBuild()).
MustBuild()).
HighAvailability(
ovirtsdk4.NewHighAvailabilityBuilder().
Enabled(true).
MustBuild()).
Cpu(
ovirtsdk4.NewCpuBuilder().
Topology(
ovirtsdk4.NewCpuTopologyBuilder().
Cores(cpu2).
Sockets(1).
MustBuild()).
MustBuild()).
Cluster(
ovirtsdk4.NewClusterBuilder().
Name(Cluster).
MustBuild()).
Template(
ovirtsdk4.NewTemplateBuilder().
Name("Blank").
MustBuild()).
MustBuild()).
Send()
11 months, 2 weeks
mount options change
by Jiří Sléžka
Hi,
is there any way to change mount options on active storage?
I started using my gluster volume in replica 3, arbiter 1 configuration
with 10.0.4.11:/vms mount point and mount options
backup-volfile-servers=10.0.4.13
I would like to add also 10.0.4.12 as backup volfile as I am on full
replica 3 now.
Yes, I suppose I can shut down all vms, switch domain to maintenance and
then change mount options but is there any other way? For example change
it directly in db and then restart all hosts one by one (while vms are
running)?
Cheers,
Jiri
11 months, 2 weeks
Re: [External] : Re: about the hugepage setting of the KVM server
by Tommy Sway
I use the ovirt-node, and I configured HUGEPAGE on the VM, and does not
configure the HUGEPAGE on the KVM host.
The THP I don't configure anything about it, and after configure the
HUGEPAGE on the vm, there is no report.
I don't know which method is the best.
From: Marcos Sungaila <marcos.sungaila(a)oracle.com>
Sent: Thursday, August 26, 2021 9:13 PM
To: Tommy Sway <sz_cuitao(a)163.com>; users(a)ovirt.org
Subject: RE: [External] : [ovirt-users] Re: about the hugepage setting of
the KVM server
Hi Tommy,
I have no simple answer to your question since I did not need this before,
but some questions may help us understand how it is currently working.
1st- Are you using an ovirt-node or an OS+vdsm as a hypervisor?
2nd- Did you enabled huge pages on the VM OS?
3rd- Did you check on the hypervisor OS if transparent hugepages (THP) is
enabled? And if, after enabling/configuring hugepages in the VM, it is
reporting hugepages are in use in the host?
Marcos
From: Tommy Sway <sz_cuitao(a)163.com <mailto:sz_cuitao@163.com> >
Sent: quinta-feira, 26 de agosto de 2021 04:49
To: users(a)ovirt.org <mailto:users@ovirt.org>
Subject: [External] : [ovirt-users] Re: about the hugepage setting of the
KVM server
Anyone can help me ?
From: users-bounces(a)ovirt.org <mailto:users-bounces@ovirt.org>
<users-bounces(a)ovirt.org <mailto:users-bounces@ovirt.org> > On Behalf Of
Tommy Sway
Sent: Thursday, August 26, 2021 12:27 AM
To: users(a)ovirt.org <mailto:users@ovirt.org>
Subject: [ovirt-users] about the hugepage setting of the KVM server
Hi:
I am running virtual machines on the KVM servers of oVirt env. The virtual
machine is running database, which needs to set the memory huge page on the
OPERATING system of the virtual machine.
If I need to set the huge page on the VIRTUAL machine, do I also need to set
huge page on the KVM physical machine? Or just on the virtual machine?
What best practices do you recommend?
Thank you very much!
11 months, 2 weeks
Unable to export VM from data storage domain.
by Diggy Mc
I'm running oVirt 4.4.4 with two data storage domains. One domain is where the production VMs run. The second domain is where I make backup copies of the VMs in the event of problems with the main production VMs. I make backups using the export option from the GUI's dropdown list.
I just now tried to "restore" a backup copy via the export function and get an error. In fact, I get errors trying to export (import to my original data domain) any of the VMs that were exported to my backup data domain. My backup domain is a DATA domain and not an EXPORT domain.
The exact error is:
Export VM Failed
[Cannot add VM. Cannot find a disk profile defined on storage domain 246c69e9-6f16-489f-8022-8613f6c1c22a.]
Is this a bug or am I doing something wrong? Help is needed urgently. In advance, thank you.
11 months, 2 weeks
