- Users - oVirt List Archives

RFE: HostedEngine to use boom by default
by Strahil Nikolov 12 Jun '19

12 Jun '19

Hello All, I have seen a lot of cases where the HostedEngine gets corrupted/broken and beyond repair. I think that BOOM is a good option for our HostedEngine appliances due to the fact that it supports booting from LVM snapshots and thus being able to easily recover after upgrades or other outstanding situations. Sadly, BOOM has 1 drawback - that everything should be under a single snapshot - thus no separation of /var /log or /audit. Do you think that changing the appliance layout is worth it ? Note: I might have an unsupported layout that could cause my confusion.Is your layout a single root LV ? Best Regards,Strahil Nikolov

2 2

4K Sector Hard drive Support - oVirt 4.3.4
by nico.kruger＠darkmatter.ae 12 Jun '19

12 Jun '19

Hi Guys, Does anyone have any idea if/when 4K Sector drives will be supported? My understanding is that this was one of the features for 4.3.4 Thanks Nico Kruger

2 1

vNUMA question
by Matthias Leopold 12 Jun '19

12 Jun '19

Hi, when I want to use vNUMA for VMs is it necessary that the number of VM virtual sockets corresponds to the number of vNUMA nodes? concrete example: hypervisor host has 2 physical cpus VM has 2 vNUMA nodes and uses CPU pinning which distributes the VCPUs equally over both physical CPUs is it necessary for the VM to have 2 virtual sockets or is it ok for virtual socket count to be powers of 2 (eg. 16)? thanks matthias

2 1

Re: Can't bring upgraded to 4.3 host back to cluster
by Shani Leviim 12 Jun '19

12 Jun '19

Np :) On Tuesday, June 11, 2019, Artem Tambovskiy <artem.tambovskiy(a)gmail.com> wrote: > Actually, this one wasn't stupid. The host was running version 4.3.3 and > was upgraded to 4.3.4 after yum update. > And this solved the issue ... thanks a lot! > > Looing at the bugtracker (https://bugzilla.redhat.com/ > buglist.cgi?classification=oVirt&f1=flagtypes.name&o1= > substring&query_format=advanced&target_milestone=ovirt-4.3.4&v1=blocker) > I don't see a suitable bug for this. perhaps vdsmd reconfiguration + yum > upgrade + host reboot did the trick. > > Thank you very much for spending a time on this! > Regards, > Artem > > On Tue, Jun 11, 2019 at 5:19 PM Shani Leviim <sleviim(a)redhat.com> wrote: > >> A stupid one: did you try to yum update? >> >> >> >> *Regards,* >> >> *Shani Leviim* >> >> >> On Tue, Jun 11, 2019 at 5:11 PM Artem Tambovskiy < >> artem.tambovskiy(a)gmail.com> wrote: >> >>> >>> Just tried this: >>> >>> [root@ovirt1 vdsm]# vdsm-tool configure --force >>> >>> Checking configuration status... >>> >>> abrt is already configured for vdsm >>> Managed volume database is already configured >>> lvm is configured for vdsm >>> libvirt is already configured for vdsm >>> SUCCESS: ssl configured to true. No conflicts >>> Current revision of multipath.conf detected, preserving >>> >>> Running configure... >>> Reconfiguration of abrt is done. >>> Reconfiguration of passwd is done. >>> Reconfiguration of libvirt is done. >>> >>> Done configuring modules to VDSM. >>> >>> And tried to restart vdsmd - it failed again. >>> >>> [root@ovirt1 vdsm]# journalctl -xe >>> Jun 11 17:07:58 ovirt1.telia.ru systemd[1]: ovirt-ha-broker.service >>> failed. >>> Jun 11 17:07:58 ovirt1.telia.ru systemd[1]: ovirt-ha-broker.service >>> holdoff time over, scheduling restart. >>> Jun 11 17:07:58 ovirt1.telia.ru systemd[1]: Cannot add dependency job >>> for unit lvm2-lvmetad.socket, ignoring: Unit is masked. >>> Jun 11 17:07:58 ovirt1.telia.ru systemd[1]: Stopped oVirt Hosted Engine >>> High Availability Communications Broker. >>> -- Subject: Unit ovirt-ha-broker.service has finished shutting down >>> -- Defined-By: systemd >>> -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel >>> -- >>> -- Unit ovirt-ha-broker.service has finished shutting down. >>> Jun 11 17:07:58 ovirt1.telia.ru systemd[1]: Started oVirt Hosted Engine >>> High Availability Communications Broker. >>> -- Subject: Unit ovirt-ha-broker.service has finished start-up >>> -- Defined-By: systemd >>> -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel >>> -- >>> -- Unit ovirt-ha-broker.service has finished starting up. >>> -- >>> -- The start-up result is done. >>> Jun 11 17:07:59 ovirt1.telia.ru systemd[1]: mom-vdsm.service holdoff >>> time over, scheduling restart. >>> Jun 11 17:07:59 ovirt1.telia.ru systemd[1]: Cannot add dependency job >>> for unit lvm2-lvmetad.socket, ignoring: Unit is masked. >>> Jun 11 17:07:59 ovirt1.telia.ru systemd[1]: Stopped MOM instance >>> configured for VDSM purposes. >>> -- Subject: Unit mom-vdsm.service has finished shutting down >>> -- Defined-By: systemd >>> -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel >>> -- >>> -- Unit mom-vdsm.service has finished shutting down. >>> Jun 11 17:07:59 ovirt1.telia.ru systemd[1]: start request repeated too >>> quickly for supervdsmd.service >>> Jun 11 17:07:59 ovirt1.telia.ru systemd[1]: Failed to start Auxiliary >>> vdsm service for running helper functions as root. >>> -- Subject: Unit supervdsmd.service has failed >>> -- Defined-By: systemd >>> -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel >>> -- >>> -- Unit supervdsmd.service has failed. >>> -- >>> -- The result is failed. >>> Jun 11 17:07:59 ovirt1.telia.ru systemd[1]: Dependency failed for >>> Virtual Desktop Server Manager. >>> -- Subject: Unit vdsmd.service has failed >>> -- Defined-By: systemd >>> -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel >>> -- >>> -- Unit vdsmd.service has failed. >>> -- >>> -- The result is dependency. >>> Jun 11 17:07:59 ovirt1.telia.ru systemd[1]: Dependency failed for MOM >>> instance configured for VDSM purposes. >>> -- Subject: Unit mom-vdsm.service has failed >>> -- Defined-By: systemd >>> -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel >>> -- >>> -- Unit mom-vdsm.service has failed. >>> -- >>> -- The result is dependency. >>> Jun 11 17:07:59 ovirt1.telia.ru systemd[1]: Job mom-vdsm.service/start >>> failed with result 'dependency'. >>> Jun 11 17:07:59 ovirt1.telia.ru systemd[1]: Job vdsmd.service/start >>> failed with result 'dependency'. >>> Jun 11 17:07:59 ovirt1.telia.ru systemd[1]: supervdsmd.service failed. >>> >>> I also tried to enable DEBUG level but failed. >>> >>> [root@ovirt1 vdsm]# vdsm-client Host setLogLevel level=DEBUG >>> vdsm-client: Connection to localhost:54321 with use_tls=True, timeout=60 >>> failed: [Errno 111] Connection refused >>> >>> >>> Regards, >>> Artem >>> >>> >>> >>> On Tue, Jun 11, 2019 at 4:45 PM Shani Leviim <sleviim(a)redhat.com> wrote: >>> >>>> Until will get a response from Dan (maybe it's related to a network >>>> issue), I would suggest to re-configure the vdsm: >>>> vdsm-tool configure --force >>>> >>>> some further steps are available here: https://www.ovirt.org/develop/ >>>> developer-guide/vdsm/installing-vdsm-from-rpm.html# >>>> installing--configuring-vdsm >>>> >>>> Let me know if it helped. >>>> >>>> Also, can you please attach a VDSM log with DEBUG level? >>>> To do so: >>>> vdsm-client Host setLogLevel level=DEBUG >>>> >>>> >>>> *Regards,* >>>> >>>> *Shani Leviim* >>>> >>>> >>>> On Tue, Jun 11, 2019 at 3:04 PM Artem Tambovskiy < >>>> artem.tambovskiy(a)gmail.com> wrote: >>>> >>>>> Hi Shani, >>>>> >>>>> yes, you are right - I can do ssh form aby to any hosts in the >>>>> cluster. vdsm.log attached. >>>>> I have tried to restart vdsm manually and even done a host restart >>>>> several times with no success. >>>>> Host activation fails all the time ... >>>>> >>>>> Thank you in advance for your help! >>>>> Regard, >>>>> Artem >>>>> >>>>> On Tue, Jun 11, 2019 at 10:51 AM Shani Leviim <sleviim(a)redhat.com> >>>>> wrote: >>>>> >>>>>> Hi Artem, >>>>>> According to oVirt documentation [1], hosts on the same cluster >>>>>> should be reachable from one to each other. >>>>>> >>>>>> Can you please share your vdsm log? >>>>>> I suppose you do manage to ssh that inactive host (correct me if I'm >>>>>> wrong). >>>>>> While getting the vdsm log, maybe try to restart the network and >>>>>> vdsmd services on the host. >>>>>> >>>>>> Another thing you can try on the UI is putting the host on >>>>>> maintenance and then activate it. >>>>>> >>>>>> [1] https://www.ovirt.org/documentation/admin-guide/ >>>>>> chap-Clusters.html#introduction-to-clusters >>>>>> >>>>>> >>>>>> *Regards,* >>>>>> >>>>>> *Shani Leviim* >>>>>> >>>>>> >>>>>> On Mon, Jun 10, 2019 at 4:42 PM Artem Tambovskiy < >>>>>> artem.tambovskiy(a)gmail.com> wrote: >>>>>> >>>>>>> Hello, >>>>>>> >>>>>>> May I ask you for and advise? >>>>>>> I'm running a small oVirt cluster and couple of months ago I decided >>>>>>> to do an upgrade from oVirt 4.2.8 to 4.3 and having an issues since that >>>>>>> time. I can only guess what I did wrong - probably one of the problems that >>>>>>> I haven't switched the cluster from iptables to firewalld. But this is just >>>>>>> my guess. >>>>>>> >>>>>>> The problem is that I have upgraded the engine and one host, and >>>>>>> then I done an upgrade of second host I can't bring it to active state. >>>>>>> Looks like VDSM can't detect the network and fails to start. I even tried >>>>>>> to reinstall the hosts from UI (I have seen that the packages being >>>>>>> installed) but again, VDSM doesn't startup at the end and reinstallation >>>>>>> fails. >>>>>>> >>>>>>> Looking at hosts process list I see script *wait_for_ipv4s* >>>>>>> hanging forever. >>>>>>> >>>>>>> vdsm 8603 1 6 16:26 ? 00:00:00 /usr/bin/python >>>>>>> /usr/share/ovirt-hosted-engine-ha/ovirt-ha-agent >>>>>>> >>>>>>> *root 8630 1 0 16:26 ? 00:00:00 /bin/sh >>>>>>> /usr/libexec/vdsm/vdsmd_init_common.sh --pre-startroot 8645 8630 6 >>>>>>> 16:26 ? 00:00:00 /usr/bin/python2 /usr/libexec/vdsm/wait_for_ipv4s* >>>>>>> root 8688 1 30 16:27 ? 00:00:00 /usr/bin/python2 >>>>>>> /usr/share/vdsm/supervdsmd --sockfile /var/run/vdsm/svdsm.sock >>>>>>> vdsm 8715 1 0 16:27 ? 00:00:00 /usr/bin/python >>>>>>> /usr/share/ovirt-hosted-engine-ha/ovirt-ha-broker >>>>>>> >>>>>>> The all hosts in cluster are reachable from each other ... That >>>>>>> could be the issue? >>>>>>> >>>>>>> Thank you in advance! >>>>>>> -- >>>>>>> Regards, >>>>>>> Artem >>>>>>> _______________________________________________ >>>>>>> Users mailing list -- users(a)ovirt.org >>>>>>> To unsubscribe send an email to users-leave(a)ovirt.org >>>>>>> Privacy Statement: https://www.ovirt.org/site/privacy-policy/ >>>>>>> oVirt Code of Conduct: https://www.ovirt.org/ >>>>>>> community/about/community-guidelines/ >>>>>>> List Archives: https://lists.ovirt.org/ >>>>>>> archives/list/users(a)ovirt.org/message/TQX3LN2TEM4DECKKUMMRCWXTRM6BGI >>>>>>> AB/ >>>>>>> >>>>>> >>>>> >>>>> -- >>>>> Regards, >>>>> Artem >>>>> >>>> >>> >>> -- >>> Regards, >>> Artem >>> >> > > -- > Regards, > Artem > -- *Regards,* *Shani Leviim*

1 0

VM Disk Performance metrics?
by Wesley Stewart 11 Jun '19

11 Jun '19

Is there any way to get ovirt disk performance metrics into the web interface? It would be nice to see some type of IOPs data, so we can see which VMs are hitting our data stores the most. It seems you can run virt-top on a host to get some of these metrics, but it would be nice to get some sort of data in the gui. Thanks!

3 2

Can't bring upgraded to 4.3 host back to cluster
by Artem Tambovskiy 11 Jun '19

11 Jun '19

Hello, May I ask you for and advise? I'm running a small oVirt cluster and couple of months ago I decided to do an upgrade from oVirt 4.2.8 to 4.3 and having an issues since that time. I can only guess what I did wrong - probably one of the problems that I haven't switched the cluster from iptables to firewalld. But this is just my guess. The problem is that I have upgraded the engine and one host, and then I done an upgrade of second host I can't bring it to active state. Looks like VDSM can't detect the network and fails to start. I even tried to reinstall the hosts from UI (I have seen that the packages being installed) but again, VDSM doesn't startup at the end and reinstallation fails. Looking at hosts process list I see script *wait_for_ipv4s* hanging forever. vdsm 8603 1 6 16:26 ? 00:00:00 /usr/bin/python /usr/share/ovirt-hosted-engine-ha/ovirt-ha-agent *root 8630 1 0 16:26 ? 00:00:00 /bin/sh /usr/libexec/vdsm/vdsmd_init_common.sh --pre-startroot 8645 8630 6 16:26 ? 00:00:00 /usr/bin/python2 /usr/libexec/vdsm/wait_for_ipv4s* root 8688 1 30 16:27 ? 00:00:00 /usr/bin/python2 /usr/share/vdsm/supervdsmd --sockfile /var/run/vdsm/svdsm.sock vdsm 8715 1 0 16:27 ? 00:00:00 /usr/bin/python /usr/share/ovirt-hosted-engine-ha/ovirt-ha-broker The all hosts in cluster are reachable from each other ... That could be the issue? Thank you in advance! -- Regards, Artem

3 5

Failed to activate Storage Domain --- ovirt 4.2
by aminur.rahman＠iongroup.com 11 Jun '19

11 Jun '19

Hi Has anyone experiencing the following issue with Storage Domain - Failed to activate Storage Domain cLUN-R940-DC2-dstore01 -- VDSM command ActivateStorageDomainVDS failed: Storage domain does not exist: (u'1b0ef853-fd71-45ea-8165-cc6047a267bc',) Currently, the storge Domain is Inactive and strangely, the VMs are running as normal. We can't manage or extend the volume size of this storage domain. The pvscan shows as: [root@uk1-ion-ovm-18 pvscan /dev/mapper/36000d310056978000000000000000014: Checksum error at offset 4397954425856 Couldn't read volume group metadata from /dev/mapper/36000d310056978000000000000000014. Metadata location on /dev/mapper/36000d310056978000000000000000014 at 4397954425856 has invalid summary for VG. Failed to read metadata summary from /dev/mapper/36000d310056978000000000000000014 Failed to scan VG from /dev/mapper/36000d310056978000000000000000014 I have tired the following steps: 1. Restarted ovirt-engine.service 2. tried to restore the metadata using vgcfgrestore but it failed with the following error: [root@uk1-ion-ovm-19 backup]# vgcfgrestore 36000d310056978000000000000000014 Volume group 36000d310056978000000000000000014 has active volume: . WARNING: Found 1 active volume(s) in volume group "36000d310056978000000000000000014". Restoring VG with active LVs, may cause mismatch with its metadata. Do you really want to proceed with restore of volume group "36000d310056978000000000000000014", while 1 volume(s) are active? [y/n]: y /dev/mapper/36000d310056978000000000000000014: Checksum error at offset 4397954425856 Couldn't read volume group metadata from /dev/mapper/36000d310056978000000000000000014. Metadata location on /dev/mapper/36000d310056978000000000000000014 at 4397954425856 has invalid summary for VG. Failed to read metadata summary from /dev/mapper/36000d310056978000000000000000014 Failed to scan VG from /dev/mapper/36000d310056978000000000000000014 /etc/lvm/backup/36000d310056978000000000000000014: stat failed: No such file or directory Couldn't read volume group metadata from file. Failed to read VG 36000d310056978000000000000000014 from /etc/lvm/backup/36000d310056978000000000000000014 Restore failed. Please let me know if anyone knows any possible resolution. -AMinur

5 6

[ANN] oVirt 4.3.4 is now generally available
by Sandro Bonazzola 11 Jun '19

11 Jun '19

The oVirt Project is pleased to announce the general availability of oVirt 4.3.4 as of June 11th, 2019. This update is the fourth in a series of stabilization updates to the 4.3 series. This release is available now on x86_64 architecture for: * Red Hat Enterprise Linux 7.6 or later * CentOS Linux (or similar) 7.6 or later This release supports Hypervisor Hosts on x86_64 and ppc64le architectures for: * Red Hat Enterprise Linux 7.6 or later * CentOS Linux (or similar) 7.6 or later * oVirt Node 4.3 (available for x86_64 only) Due to Fedora 28 being now at end of life this release is missing experimental tech preview for x86_64 and s390x architectures for Fedora 28. We are working on Fedora 29 and 30 support and we may re-introduce experimental support for Fedora in next release. See the release notes [1] for installation / upgrade instructions and a list of new features and bugs fixed. Notes: - oVirt Appliance is already available - oVirt Node is already available[2] - oVirt Windows Guest Tools is already available[2] oVirt Guest Tools ISO has been updated including new virtio-win-prewhql drivers collection version 171, providing updated qxl-wddm-dod driver version 0.19 (see https://gitlab.freedesktop.org/spice/win32/qxl-wddm-dod/blob/master/Changel… for more information). oVirt Node and Appliance have been updated including: - oVirt 4.3.4: http://www.ovirt.org/release/4.3.4/ - Latest CentOS updates including: - CEBA-2019:1015 CentOS 7 glibc BugFix Update <https://lists.centos.org/pipermail/centos-announce/2019-May/023302.html> - CESA-2019:0809 Important CentOS 7 ovmf Security Update <https://lists.centos.org/pipermail/centos-announce/2019-April/023280.html> - CEBA-2019:0814 CentOS 7 lvm2 BugFix Update <https://lists.centos.org/pipermail/centos-announce/2019-April/023294.html> - CEBA-2019:0808 CentOS 7 iproute BugFix Update <https://lists.centos.org/pipermail/centos-announce/2019-April/023288.html> - CESA-2019:1168 Important CentOS 7 kernel Security Update <https://lists.centos.org/pipermail/centos-announce/2019-May/023314.html> - CEBA-2019:0807 CentOS 7 gcc BugFix Update <https://lists.centos.org/pipermail/centos-announce/2019-April/023286.html> - CEBA-2019:0820 CentOS 7 systemd BugFix Update <https://lists.centos.org/pipermail/centos-announce/2019-April/023281.html> - CEBA-2019:0816 CentOS 7 sssd BugFix Update <https://lists.centos.org/pipermail/centos-announce/2019-April/023283.html> - CESA-2019:1264 Important CentOS 7 libvirt Security Update <https://lists.centos.org/pipermail/centos-announce/2019-May/023319.html> - CEEA-2019:1210 CentOS 7 microcode_ctl Enhancement Update <https://lists.centos.org/pipermail/centos-announce/2019-May/023311.html> - CESA-2019:1022 Important CentOS 7 python-jinja2 Security Update <https://lists.centos.org/pipermail/centos-announce/2019-May/023303.html> - CEEA-2019:0045 CentOS 7 rsync Enhancement Update <https://lists.centos.org/pipermail/centos-announce/2019-April/023284.html> - CEBA-2019:0826 CentOS 7 scap-security-guide BugFix Update <https://lists.centos.org/pipermail/centos-announce/2019-April/023291.html> - CEBA-2019:0819 CentOS 7 sos BugFix Update <https://lists.centos.org/pipermail/centos-announce/2019-April/023292.html> - latest CentOS Virt and Storage SIG updates: - CESA-2019:1179 CentOS Virt SIG - Errata and Security Advisory 2019:1179 Important Upstream details at : https://access.redhat.com/errata/RHSA-2019:1179 - ansible-2.8.1: https://github.com/ansible/ansible/blob/stable-2.8/changelogs/CHANGELOG-v2.… - glusterfs-5.6: https://docs.gluster.org/en/latest/release-notes/5.6/ - cockpit 193: https://cockpit-project.org/blog/cockpit-193.html Additional Resources: * Read more about the oVirt 4.3.4 release highlights: http://www.ovirt.org/release/4.3.4/ * Get more oVirt Project updates on Twitter: https://twitter.com/ovirt * Check out the latest project news on the oVirt blog: http://www.ovirt.org/blog/ [1] http://www.ovirt.org/release/4.3.4/ [2] http://resources.ovirt.org/pub/ovirt-4.3/iso/ -- Sandro Bonazzola MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://www.redhat.com/>

1 0

Replace bad Host from a 9 Node hyperconverged setup 4.3.3
by adrianquintero＠gmail.com 10 Jun '19

10 Jun '19

Anybody have had to replace a failed host from a 3, 6, or 9 node hyperconverged setup with gluster storage? One of my hosts is completely dead, I need to do a fresh install using ovirt node iso, can anybody point me to the proper steps? thanks,

6 15

Re: run ovirt without firewalld
by Strahil 10 Jun '19

10 Jun '19

Then ... You have no choice , but to enable firewalld via a cron job or systemd service. I think Sahina and/or Sandro can hint you how to proceed . Best Regards, Strahil Nikolov On Jun 10, 2019 20:02, Chris Boon <cpjboon(a)gmail.com> wrote: > > yeah i noticed the same, HostedEngine doesn't want to migrate or start due to disabled firewalld. > But some organizations have a company policy not to run firewalls on servers, only edge firewalls. > So automation tools disable firewalld :( > > best regards, > Chris > _______________________________________________ > Users mailing list -- users(a)ovirt.org > To unsubscribe send an email to users-leave(a)ovirt.org > Privacy Statement: https://www.ovirt.org/site/privacy-policy/ > oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ > List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/JQOROLNXKSQHT…

1 0