oVirt 4.4.10 is now generally available
by Sandro Bonazzola
oVirt 4.4.10 is now generally available
The oVirt project is excited to announce the general availability of oVirt
4.4.10 , as of January 18th, 2022.
This release unleashes an altogether more powerful and flexible open source
virtualization solution that encompasses hundreds of individual changes and
a wide range of enhancements across the engine, storage, network, user
interface, and analytics, as compared to oVirt 4.3.
Important notes before you install / upgrade
Please note that oVirt 4.4 only supports clusters and data centers with
compatibility version 4.2 and above. If clusters or data centers are
running with an older compatibility version, you need to upgrade them to at
least 4.2 (4.3 is recommended).
Please note that in RHEL 8 / CentOS 8 several devices that worked on EL7
are no longer supported.
For example, the megaraid_sas driver is removed. If you use Enterprise
Linux 8 hosts you can try to provide the necessary drivers for the
deprecated hardware using the DUD method (See the users’ mailing list
thread on this at
https://lists.ovirt.org/archives/list/users@ovirt.org/thread/NDSVUZSESOXE...
)
Documentation
-
If you want to try oVirt as quickly as possible, follow the instructions
on the Download <https://ovirt.org/download/> page.
-
For complete installation, administration, and usage instructions, see
the oVirt Documentation <https://ovirt.org/documentation/>.
-
For upgrading from a previous version, see the oVirt Upgrade Guide
<https://ovirt.org/documentation/upgrade_guide/>.
-
For a general overview of oVirt, see About oVirt
<https://ovirt.org/community/about.html>.
What’s new in oVirt 4.4.10 Release?
This update is the ninth in a series of stabilization updates to the 4.4
series.
This release is available now on x86_64 architecture for:
-
Red Hat Enterprise Linux 8.5 (or similar)
-
CentOS Stream 8
This release supports Hypervisor Hosts on x86_64 and ppc64le architectures
for:
-
Red Hat Enterprise Linux 8.5 (or similar)
-
oVirt Node NG (based on CentOS Stream 8)
-
CentOS Stream 8
Some of the RFEs with high user impact are listed below:
-
Bug 2012135 <https://bugzilla.redhat.com/show_bug.cgi?id=2012135> -
[RFE] Provide option to unmap multiple LUNs using ovirt_remove_stale_lun
ansible role
Some of the Bugs with high user impact are listed below:
-
Bug 1710323 <https://bugzilla.redhat.com/show_bug.cgi?id=1710323> -
Microsoft failover cluster is not working with FC direct LUN on Windows
2016 server and Windows 2019
-
Bug 2023224 <https://bugzilla.redhat.com/show_bug.cgi?id=2023224> -
multipath -f fails with "map in use" error while removing the LUNs using
"ovirt_remove_stale_lun"
-
Bug 2027260 <https://bugzilla.redhat.com/show_bug.cgi?id=2027260> - Cold
backup fail in various ways - backup is reported ready before add_bitmap
jobs complete
-
Bug 1897114 <https://bugzilla.redhat.com/show_bug.cgi?id=1897114> - Add
additional logging information to be able to understand why host is stuck
in Unassigned state
-
Bug 1978655 <https://bugzilla.redhat.com/show_bug.cgi?id=1978655> - ELK
integration fails due to missing configuration parameters
-
Bug 2032919 <https://bugzilla.redhat.com/show_bug.cgi?id=2032919> -
Unable to add EL 7 host into oVirt Engine in clusters 4.2/4.3
oVirt Node has been updated, including:
-
oVirt 4.4.10: https://www.ovirt.org/release/4.4.10/
-
CentOS Stream 8 latest updates
-
Full list of changes:
--- ovirt-node-ng-image-4.4.9.3.manifest-rpm 2021-12-15 15:40:13.501764699
+0100
+++ ovirt-node-ng-image-4.4.10.manifest-rpm 2022-01-19 08:09:36.668868583
+0100
@@ -2,7 +2,6 @@
-ModemManager-glib-1.18.2-1.el8.x86_64
-NetworkManager-1.36.0-0.2.el8.x86_64
-NetworkManager-config-server-1.36.0-0.2.el8.noarch
-NetworkManager-libnm-1.36.0-0.2.el8.x86_64
-NetworkManager-ovs-1.36.0-0.2.el8.x86_64
-NetworkManager-team-1.36.0-0.2.el8.x86_64
-NetworkManager-tui-1.36.0-0.2.el8.x86_64
+NetworkManager-1.36.0-0.3.el8.x86_64
+NetworkManager-config-server-1.36.0-0.3.el8.noarch
+NetworkManager-libnm-1.36.0-0.3.el8.x86_64
+NetworkManager-ovs-1.36.0-0.3.el8.x86_64
+NetworkManager-team-1.36.0-0.3.el8.x86_64
+NetworkManager-tui-1.36.0-0.3.el8.x86_64
@@ -23 +22 @@
-alsa-lib-1.2.5-4.el8.x86_64
+alsa-lib-1.2.6.1-1.el8.x86_64
@@ -29,2 +28,2 @@
-augeas-1.12.0-6.el8.x86_64
-augeas-libs-1.12.0-6.el8.x86_64
+augeas-1.12.0-7.el8.x86_64
+augeas-libs-1.12.0-7.el8.x86_64
@@ -34 +33 @@
-autofs-5.1.4-74.el8.x86_64
+autofs-5.1.4-77.el8.x86_64
@@ -44 +43 @@
-binutils-2.30-111.el8.x86_64
+binutils-2.30-112.el8.x86_64
@@ -46 +45 @@
-blivet-data-3.4.0-7.el8.noarch
+blivet-data-3.4.0-8.el8.noarch
@@ -58 +57 @@
-ceph-common-16.2.6-1.el8s.x86_64
+ceph-common-16.2.7-1.el8s.x86_64
@@ -63,6 +62,6 @@
-clevis-15-4.el8.x86_64
-clevis-dracut-15-4.el8.x86_64
-clevis-luks-15-4.el8.x86_64
-clevis-systemd-15-4.el8.x86_64
-cockpit-258-1.el8.x86_64
-cockpit-bridge-258-1.el8.x86_64
+clevis-15-6.el8.x86_64
+clevis-dracut-15-6.el8.x86_64
+clevis-luks-15-6.el8.x86_64
+clevis-systemd-15-6.el8.x86_64
+cockpit-260-1.el8.x86_64
+cockpit-bridge-260-1.el8.x86_64
@@ -70,3 +69,3 @@
-cockpit-storaged-255-1.el8.noarch
-cockpit-system-258-1.el8.noarch
-cockpit-ws-258-1.el8.x86_64
+cockpit-storaged-259-1.el8.noarch
+cockpit-system-260-1.el8.noarch
+cockpit-ws-260-1.el8.x86_64
@@ -116 +115 @@
-dmidecode-3.2-10.el8.x86_64
+dmidecode-3.3-1.el8.x86_64
@@ -193 +192 @@
-fwupd-1.5.9-1.el8_4.x86_64
+fwupd-1.7.1-1.el8.x86_64
@@ -196 +195 @@
-gdb-headless-8.2-17.el8.x86_64
+gdb-headless-8.2-18.el8.x86_64
@@ -206,4 +205,3 @@
-glibc-2.28-174.el8.x86_64
-glibc-common-2.28-174.el8.x86_64
-glibc-gconv-extra-2.28-174.el8.x86_64
-glibc-langpack-en-2.28-174.el8.x86_64
+glibc-2.28-181.el8.x86_64
+glibc-common-2.28-181.el8.x86_64
+glibc-langpack-en-2.28-181.el8.x86_64
@@ -244 +242 @@
-gssproxy-0.8.0-19.el8.x86_64
+gssproxy-0.8.0-20.el8.x86_64
@@ -253 +251 @@
-hwdata-0.314-8.10.el8.noarch
+hwdata-0.314-8.11.el8.noarch
@@ -260,4 +258,4 @@
-ipa-client-4.9.6-6.module_el8.5.0+947+fabc681e.x86_64
-ipa-client-common-4.9.6-6.module_el8.5.0+947+fabc681e.noarch
-ipa-common-4.9.6-6.module_el8.5.0+947+fabc681e.noarch
-ipa-selinux-4.9.6-6.module_el8.5.0+947+fabc681e.noarch
+ipa-client-4.9.8-2.module_el8.6.0+1054+cdb51b28.x86_64
+ipa-client-common-4.9.8-2.module_el8.6.0+1054+cdb51b28.noarch
+ipa-common-4.9.8-2.module_el8.6.0+1054+cdb51b28.noarch
+ipa-selinux-4.9.8-2.module_el8.6.0+1054+cdb51b28.noarch
@@ -275 +273 @@
-iputils-20180629-7.el8.x86_64
+iputils-20180629-8.el8.x86_64
@@ -303,6 +301,6 @@
-kernel-4.18.0-348.2.1.el8_5.x86_64
-kernel-core-4.18.0-348.2.1.el8_5.x86_64
-kernel-modules-4.18.0-348.2.1.el8_5.x86_64
-kernel-tools-4.18.0-348.2.1.el8_5.x86_64
-kernel-tools-libs-4.18.0-348.2.1.el8_5.x86_64
-kexec-tools-2.0.20-63.el8.x86_64
+kernel-4.18.0-358.el8.x86_64
+kernel-core-4.18.0-358.el8.x86_64
+kernel-modules-4.18.0-358.el8.x86_64
+kernel-tools-4.18.0-358.el8.x86_64
+kernel-tools-libs-4.18.0-358.el8.x86_64
+kexec-tools-2.0.20-67.el8.x86_64
@@ -312 +310 @@
-kmod-kvdo-6.2.5.72-81.el8.x86_64
+kmod-kvdo-6.2.6.3-82.el8.x86_64
@@ -359 +357 @@
-libcephfs2-16.2.6-1.el8s.x86_64
+libcephfs2-16.2.7-1.el8s.x86_64
@@ -381 +379 @@
-libgcc-8.5.0-6.el8.x86_64
+libgcc-8.5.0-7.el8.x86_64
@@ -393 +391 @@
-libgomp-8.5.0-6.el8.x86_64
+libgomp-8.5.0-7.el8.x86_64
@@ -401 +399 @@
-libibverbs-37.1-1.el8.x86_64
+libibverbs-37.2-1.el8.x86_64
@@ -405 +403 @@
-libipa_hbac-2.5.2-2.el8_5.1.x86_64
+libipa_hbac-2.6.1-2.el8.x86_64
@@ -418 +415,0 @@
-libmbim-1.26.0-2.el8.x86_64
@@ -434 +431 @@
-libosinfo-1.9.0-1.el8.x86_64
+libosinfo-1.9.0-2.el8.x86_64
@@ -441 +437,0 @@
-libpmemobj-1.6.1-1.el8.x86_64
@@ -447 +442,0 @@
-libqmi-1.30.2-1.el8.x86_64
@@ -449,3 +444,3 @@
-librados2-16.2.6-1.el8s.x86_64
-libradosstriper1-16.2.6-1.el8s.x86_64
-librbd1-16.2.6-1.el8s.x86_64
+librados2-16.2.7-1.el8s.x86_64
+libradosstriper1-16.2.7-1.el8s.x86_64
+librbd1-16.2.7-1.el8s.x86_64
@@ -453 +448 @@
-librdmacm-37.1-1.el8.x86_64
+librdmacm-37.2-1.el8.x86_64
@@ -463 +458 @@
-librgw2-16.2.6-1.el8s.x86_64
+librgw2-16.2.7-1.el8s.x86_64
@@ -477,7 +472,7 @@
-libsss_autofs-2.5.2-2.el8_5.1.x86_64
-libsss_certmap-2.5.2-2.el8_5.1.x86_64
-libsss_idmap-2.5.2-2.el8_5.1.x86_64
-libsss_nss_idmap-2.5.2-2.el8_5.1.x86_64
-libsss_simpleifp-2.5.2-2.el8_5.1.x86_64
-libsss_sudo-2.5.2-2.el8_5.1.x86_64
-libstdc++-8.5.0-6.el8.x86_64
+libsss_autofs-2.6.1-2.el8.x86_64
+libsss_certmap-2.6.1-2.el8.x86_64
+libsss_idmap-2.6.1-2.el8.x86_64
+libsss_nss_idmap-2.6.1-2.el8.x86_64
+libsss_simpleifp-2.6.1-2.el8.x86_64
+libsss_sudo-2.6.1-2.el8.x86_64
+libstdc++-8.5.0-7.el8.x86_64
@@ -536 +531 @@
-libwbclient-4.14.5-2.el8.x86_64
+libwbclient-4.15.3-0.el8.x86_64
@@ -570 +565 @@
-mdadm-4.2-rc2.el8.x86_64
+mdadm-4.2-rc3.el8.x86_64
@@ -598,4 +593,4 @@
-net-snmp-5.8-23.el8.x86_64
-net-snmp-agent-libs-5.8-23.el8.x86_64
-net-snmp-libs-5.8-23.el8.x86_64
-net-snmp-utils-5.8-23.el8.x86_64
+net-snmp-5.8-24.el8.x86_64
+net-snmp-agent-libs-5.8-24.el8.x86_64
+net-snmp-libs-5.8-24.el8.x86_64
+net-snmp-utils-5.8-24.el8.x86_64
@@ -609,2 +604,2 @@
-nmstate-1.2.0-0.1.alpha2.el8.x86_64
-nmstate-plugin-ovsdb-1.2.0-0.1.alpha2.el8.noarch
+nmstate-1.2.0-1.el8.x86_64
+nmstate-plugin-ovsdb-1.2.0-1.el8.noarch
@@ -640 +635 @@
-osinfo-db-20210903-1.el8.noarch
+osinfo-db-20211216-1.el8.noarch
@@ -643 +638 @@
-ovirt-ansible-collection-1.6.5-1.el8.noarch
+ovirt-ansible-collection-1.6.6-1.el8.noarch
@@ -646 +641 @@
-ovirt-hosted-engine-ha-2.4.9-1.el8.noarch
+ovirt-hosted-engine-ha-2.4.10-1.el8.noarch
@@ -651 +646 @@
-ovirt-node-ng-image-update-placeholder-4.4.9.3-1.el8.noarch
+ovirt-node-ng-image-update-placeholder-4.4.10-1.el8.noarch
@@ -659,2 +654,2 @@
-ovirt-release-host-node-4.4.9.3-1.el8.noarch
-ovirt-release44-4.4.9.3-1.el8.noarch
+ovirt-release-host-node-4.4.10-1.el8.noarch
+ovirt-release44-4.4.10-1.el8.noarch
@@ -667,3 +662,3 @@
-pacemaker-cluster-libs-2.1.2-1.el8.x86_64
-pacemaker-libs-2.1.2-1.el8.x86_64
-pacemaker-schemas-2.1.2-1.el8.noarch
+pacemaker-cluster-libs-2.1.2-2.el8.x86_64
+pacemaker-libs-2.1.2-2.el8.x86_64
+pacemaker-schemas-2.1.2-2.el8.noarch
@@ -677 +672 @@
-pcsc-lite-1.8.23-4.1.el8_4.x86_64
+pcsc-lite-1.9.5-1.el8.x86_64
@@ -679 +674 @@
-pcsc-lite-libs-1.8.23-4.1.el8_4.x86_64
+pcsc-lite-libs-1.9.5-1.el8.x86_64
@@ -747 +742 @@
-python3-blivet-3.4.0-7.el8.noarch
+python3-blivet-3.4.0-8.el8.noarch
@@ -750,3 +745,3 @@
-python3-ceph-argparse-16.2.6-1.el8s.x86_64
-python3-ceph-common-16.2.6-1.el8s.x86_64
-python3-cephfs-16.2.6-1.el8s.x86_64
+python3-ceph-argparse-16.2.7-1.el8s.x86_64
+python3-ceph-common-16.2.7-1.el8s.x86_64
+python3-cephfs-16.2.7-1.el8s.x86_64
@@ -755 +750,2 @@
-python3-cloud-what-1.28.21-3.el8.x86_64
+python3-click-6.7-8.el8.noarch
+python3-cloud-what-1.28.24-1.el8.x86_64
@@ -787,2 +783,2 @@
-python3-ipaclient-4.9.6-6.module_el8.5.0+947+fabc681e.noarch
-python3-ipalib-4.9.6-6.module_el8.5.0+947+fabc681e.noarch
+python3-ipaclient-4.9.8-2.module_el8.6.0+1054+cdb51b28.noarch
+python3-ipalib-4.9.8-2.module_el8.6.0+1054+cdb51b28.noarch
@@ -797,2 +793,2 @@
-python3-libipa_hbac-2.5.2-2.el8_5.1.x86_64
-python3-libnmstate-1.2.0-0.1.alpha2.el8.noarch
+python3-libipa_hbac-2.6.1-2.el8.x86_64
+python3-libnmstate-1.2.0-1.el8.noarch
@@ -805 +801 @@
-python3-linux-procfs-0.6.3-4.el8.noarch
+python3-linux-procfs-0.7.0-1.el8.noarch
@@ -837 +833 @@
-python3-perf-4.18.0-348.2.1.el8_5.x86_64
+python3-perf-4.18.0-358.el8.x86_64
@@ -860,2 +856,2 @@
-python3-rados-16.2.6-1.el8s.x86_64
-python3-rbd-16.2.6-1.el8s.x86_64
+python3-rados-16.2.7-1.el8s.x86_64
+python3-rbd-16.2.7-1.el8s.x86_64
@@ -865 +861 @@
-python3-rgw-16.2.6-1.el8s.x86_64
+python3-rgw-16.2.7-1.el8s.x86_64
@@ -867 +863 @@
-python3-rpm-4.14.3-19.el8.x86_64
+python3-rpm-4.14.3-21.el8.x86_64
@@ -875,3 +871,3 @@
-python3-sss-2.5.2-2.el8_5.1.x86_64
-python3-sss-murmur-2.5.2-2.el8_5.1.x86_64
-python3-sssdconfig-2.5.2-2.el8_5.1.noarch
+python3-sss-2.6.1-2.el8.x86_64
+python3-sss-murmur-2.6.1-2.el8.x86_64
+python3-sssdconfig-2.6.1-2.el8.noarch
@@ -879 +875 @@
-python3-subscription-manager-rhsm-1.28.21-3.el8.x86_64
+python3-subscription-manager-rhsm-1.28.24-1.el8.x86_64
@@ -881 +877 @@
-python3-syspurpose-1.28.21-3.el8.x86_64
+python3-syspurpose-1.28.24-1.el8.x86_64
@@ -914,4 +910,4 @@
-rpm-4.14.3-19.el8.x86_64
-rpm-build-libs-4.14.3-19.el8.x86_64
-rpm-libs-4.14.3-19.el8.x86_64
-rpm-plugin-selinux-4.14.3-19.el8.x86_64
+rpm-4.14.3-21.el8.x86_64
+rpm-build-libs-4.14.3-21.el8.x86_64
+rpm-libs-4.14.3-21.el8.x86_64
+rpm-plugin-selinux-4.14.3-21.el8.x86_64
@@ -925,3 +921,3 @@
-samba-client-libs-4.14.5-2.el8.x86_64
-samba-common-4.14.5-2.el8.noarch
-samba-common-libs-4.14.5-2.el8.x86_64
+samba-client-libs-4.15.3-0.el8.x86_64
+samba-common-4.15.3-0.el8.noarch
+samba-common-libs-4.15.3-0.el8.x86_64
@@ -931,2 +927,2 @@
-sbd-1.5.0-2.el8.x86_64
-scap-security-guide-0.1.57-5.el8.noarch
+sbd-1.5.1-1.el8.x86_64
+scap-security-guide-0.1.59-1.el8.noarch
@@ -937,2 +933,2 @@
-selinux-policy-3.14.3-85.el8.noarch
-selinux-policy-targeted-3.14.3-85.el8.noarch
+selinux-policy-3.14.3-86.el8.noarch
+selinux-policy-targeted-3.14.3-86.el8.noarch
@@ -950 +946 @@
-sos-4.2-7.el8.noarch
+sos-4.2-11.el8.noarch
@@ -956,9 +952,9 @@
-sssd-client-2.5.2-2.el8_5.1.x86_64
-sssd-common-2.5.2-2.el8_5.1.x86_64
-sssd-common-pac-2.5.2-2.el8_5.1.x86_64
-sssd-dbus-2.5.2-2.el8_5.1.x86_64
-sssd-ipa-2.5.2-2.el8_5.1.x86_64
-sssd-kcm-2.5.2-2.el8_5.1.x86_64
-sssd-krb5-common-2.5.2-2.el8_5.1.x86_64
-sssd-tools-2.5.2-2.el8_5.1.x86_64
-subscription-manager-rhsm-certificates-1.28.21-3.el8.x86_64
+sssd-client-2.6.1-2.el8.x86_64
+sssd-common-2.6.1-2.el8.x86_64
+sssd-common-pac-2.6.1-2.el8.x86_64
+sssd-dbus-2.6.1-2.el8.x86_64
+sssd-ipa-2.6.1-2.el8.x86_64
+sssd-kcm-2.6.1-2.el8.x86_64
+sssd-krb5-common-2.6.1-2.el8.x86_64
+sssd-tools-2.6.1-2.el8.x86_64
+subscription-manager-rhsm-certificates-1.28.24-1.el8.x86_64
@@ -976,5 +972,5 @@
-systemd-239-51.el8.x86_64
-systemd-container-239-51.el8.x86_64
-systemd-libs-239-51.el8.x86_64
-systemd-pam-239-51.el8.x86_64
-systemd-udev-239-51.el8.x86_64
+systemd-239-51.el8_5.2.x86_64
+systemd-container-239-51.el8_5.2.x86_64
+systemd-libs-239-51.el8_5.2.x86_64
+systemd-pam-239-51.el8_5.2.x86_64
+systemd-udev-239-51.el8_5.2.x86_64
@@ -982 +978 @@
-tcpdump-4.9.3-2.el8.x86_64
+tcpdump-4.9.3-3.el8.x86_64
@@ -993 +989 @@
-usbredir-0.8.0-1.el8.x86_64
+usbredir-0.12.0-1.el8.x86_64
@@ -997,11 +993,11 @@
-vdsm-4.40.90.4-1.el8.x86_64
-vdsm-api-4.40.90.4-1.el8.noarch
-vdsm-client-4.40.90.4-1.el8.noarch
-vdsm-common-4.40.90.4-1.el8.noarch
-vdsm-gluster-4.40.90.4-1.el8.x86_64
-vdsm-http-4.40.90.4-1.el8.noarch
-vdsm-jsonrpc-4.40.90.4-1.el8.noarch
-vdsm-network-4.40.90.4-1.el8.x86_64
-vdsm-python-4.40.90.4-1.el8.noarch
-vdsm-yajsonrpc-4.40.90.4-1.el8.noarch
-vim-minimal-8.0.1763-16.el8_5.2.x86_64
+vdsm-4.40.100.2-1.el8.x86_64
+vdsm-api-4.40.100.2-1.el8.noarch
+vdsm-client-4.40.100.2-1.el8.noarch
+vdsm-common-4.40.100.2-1.el8.noarch
+vdsm-gluster-4.40.100.2-1.el8.x86_64
+vdsm-http-4.40.100.2-1.el8.noarch
+vdsm-jsonrpc-4.40.100.2-1.el8.noarch
+vdsm-network-4.40.100.2-1.el8.x86_64
+vdsm-python-4.40.100.2-1.el8.noarch
+vdsm-yajsonrpc-4.40.100.2-1.el8.noarch
+vim-minimal-8.0.1763-16.el8_5.3.x86_64
@@ -1011 +1007 @@
-virt-what-1.18-12.el8.x86_64
+virt-what-1.18-13.el8.x86_64
See the release notes [1] for installation instructions and a list of new
features and bugs fixed.
Additional resources:
-
Read more about the oVirt 4.4.10 release highlights:
https://www.ovirt.org/release/4.4.10/
-
Get more oVirt project updates on Twitter: https://twitter.com/ovirt
-
Check out the latest project news on the oVirt blog:
https://blogs.ovirt.org/
[1] https://www.ovirt.org/release/4.4.10/
--
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.*
3 years
Re: support of AMD EPYC 3rd Genneration Milan
by Sandro Bonazzola
Il giorno sab 8 gen 2022 alle ore 18:47 samuel.xhu(a)horebdata.cn <
samuel.xhu(a)horebdata.cn> ha scritto:
> Helllo, Ovirt experts,
>
> Does Ovirt now support the use of AMD EPYC 3rd Genneration Milan CPU? and
> if yes, from which version?
>
>
AMD EPYC Milan CPU should be supported by Advanced Virtualization since
June 2021, included in oVirt Node 4.4.6.1 and newer.
Within oVirt I think it's recognized as "EPYC" without real distinction
between Milan, Rome or others.
+Arik Hadas <ahadas(a)redhat.com> ?
--
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.*
3 years
oVirt nodes keeps updating and rebooting
by Harry O
Hi,
After HE deployment my oVirt nodes keeps updating and rebooting, even though I disabled node update in the beginning of deployment wizard.
Why is this and how can I stop it form happening?
3 years
Passwordless SPICE console login?
by cen
Hi,
we have all VMs set up with passwordless users, using only keys for
remote ssh login.
When connecting through SPICE console, it prompts for login. Using
something like root/ubuntu with empty password does not work.
Is there a way to do this with keys or is it essental to have a local
user with password (perhaps with restricted SSH) to perform a console login?
Best regards, cen
3 years
give cloud-init the VM name
by Luca Contessa
Hi list,
I have an oVirt node 4.4.9 installation with hyperconverged structure, on which i've created a pool of Linux VM (CentOS Stream 8).
I would like set as hostname the name of the VM + a static suffix appended at the end of the name (EXAMPLE: <VM name>.static.suffix ), is there a way to pass to cloud-init the name of the VM and do this via cloud-init?
I've tried to look for something in oVirt and cloud-init documentation and found nothing.
Thanks a lot to everybody for the help and have a nice day.
3 years
CentOS Stream Guest OS 9 support
by Gangi Reddy
Can we create CentOS Stream 9 guest OS VM in Ovirt? Do you have any link that i refer?
Ovirt:
Software Version:4.4.7.6-1.el8
Host:
OS Version: RHEL - 8.4.2105.0 - 3.el8
OS Description: oVirt Node 4.4.8
3 years
Existing Qemu/KVM Host as a node
by atkinson.unt@gmail.com
Is there any information on possibility of using an existing Qemu/KVM host as a node? I like the look and feel of oVirt, and want to use it on my main hypervisor, but I don't want to have to rebuild or import 20 VMs, one of which happens to also be my router. If I were to set up a management unit, and add my existing host as a node, would it be able to import or recognize and use existing VMs?
3 years
Linux VMs cannot boot from software raid0
by Strahil Nikolov
Hi All,
I recently migrated from 4.3.10 to 4.4.9 and it seems that booting from software raid0 (I have multiple gluster volumes) is not possible with Cluster compatibility 4.6 .
I've tested creating a fresh VM and it also suffers the problem. Changing various options (virtio-scsi to virtio, chipset, VM type) did not help .
Booting from rescue media shows that the data is still there, but grub always drops to rescue.
Any hints are welcome.
Host: CentOS Stream 8 with qemu-6.0.0oVirt 4.4.9 (latest)VM OS: RHEL7.9/RHEL8.5
Best Regards,Strahil Nikolov
3 years
how to debug sanlock issue
by Jiří Sléžka
Hello,
I have 3 node HCI cluster with glusterfs. oVirt 4.4.9.5-1. In last 2
weeks I experience 2 outages where HE and all/some vms were restarted.
While digging in logs I can see that sanlock cannot renew leases and it
leads to killing vms as is very good described in [1].
It looks to me like some hw issue with one of the hosts but cannot find
which one.
for example today's outage restarted vms on hosts 1 and 2 but not 3.
Sanlock logs
there are these lines in /var/log/messages on host 2 (ovirt-hci02)
Jan 13 08:27:25 ovirt-hci02 sanlock[1263]: 2022-01-13 08:27:25 1416706
[341378]: s7 delta_renew read timeout 10 sec offset 0
/rhev/data-center/mnt/glusterSD/10.0.4.11:_vms/6de5ae6d-c7cc-4292-bdbf-10495a38837b/dom_md/ids
Jan 13 08:28:59 ovirt-hci02 sanlock[1263]: 2022-01-13 08:28:59 1416800
[341257]: write_sectors delta_leader offset 1024 rv -202
/rhev/data-center/mnt/glusterSD/10.0.4.11:_engine/816a3d0b-2e10-4900-b3cb-4a9b5cd0dd5d/dom_md/ids
Jan 13 08:29:27 ovirt-hci02 sanlock[1263]: 2022-01-13 08:29:27 1416828
[4189968]: write_sectors delta_leader offset 1024 rv -202
/rhev/data-center/mnt/glusterSD/10.0.4.11:_engine/816a3d0b-2e10-4900-b3cb-4a9b5cd0dd5d/dom_md/ids
but not on hosts 1 and 3. Could it indicate that there could be storage
related problem on host 1?
could you please suggest further/better debugging approach?
Thanx a lot,
Jiri
[1] https://www.ovirt.org/develop/developer-guide/vdsm/sanlock.html
3 years, 1 month