- Users - oVirt List Archives

Re: oVirt and ARM
by Sandro Bonazzola 25 Jun '21

25 Jun '21

Il giorno gio 24 giu 2021 alle ore 16:34 Marko Vrgotic < M.Vrgotic(a)activevideo.com> ha scritto: > Hi oVirt, > > > > Where can I find if there are any information about oVirt supporting arm64 > CPU architecture? > Right now oVirt is not supporting arm64. There was an initiative about supporting it started some time ago from openEuler ovirt SIG. I didn't got any further updates on this topic, looping in those who I remember being looking into it. I think that if someone contributes arm64 support it would also be a feature worth a 4.5 release :-) > > > ----- > > kind regards/met vriendelijke groeten > > > > Marko Vrgotic > Sr. System Engineer @ System Administration > > > ActiveVideo > > *o: *+31 (35) 6774131 > > *m: +*31 (65) 5734174 > > *e:* m.vrgotic(a)activevideo.com > *w: *www.activevideo.com > > > > ActiveVideo Networks BV. Mediacentrum 3745 Joop van den Endeplein 1.1217 > WJ Hilversum, The Netherlands. The information contained in this message > may be legally privileged and confidential. It is intended to be read only > by the individual or entity to whom it is addressed or by their designee. > If the reader of this message is not the intended recipient, you are on > notice that any distribution of this message, in any form, is strictly > prohibited. If you have received this message in error, please immediately > notify the sender and/or ActiveVideo Networks, LLC by telephone at +1 > 408.931.9200 and delete or destroy any copy of this message. > > > > > _______________________________________________ > 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/MQ3XND2NKIL7V… > -- 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.*

2 1

Mount Export Domain only temporary
by jb 25 Jun '21

25 Jun '21

Hello community, We use a NFS export domain for full backups. Sometimes I have to restart the NFS file server, but when I just restart that server, without doing anything in oVirt (I guess normally I should put the domain in maintenance mode), it can happen that hosts and VMs a crashing. I had one time even the issue, that after a crash one XFS file system on one host got damage and I had to fix that. My though was now, because I make only one time a week a VM full backup, I only mount the export domain in this time. Is there an easy way to do this, with the API? Or would you have a other hint, how to solve this issue? Have a good day! Jonathan

4 5

oVirt 4.4.6 Gluster heal pending
by dlotarev＠yahoo.com 25 Jun '21

25 Jun '21

Hi there! I want to know what can i do with this trouble [root@ovirt-h2-new ~]# gluster volume heal data info Brick ovirt-h1-new.local:/gluster/ovirt_new/data / Status: Connected Number of entries: 1 Brick ovirt-h2-new.local:/gluster/ovirt_new/data / Status: Connected Number of entries: 1 [root@ovirt-h2-new ~]# [root@ovirt-h2-new ~]# [root@ovirt-h2-new ~]# [root@ovirt-h2-new ~]# gluster volume heal data info summary Brick ovirt-h1-new.local:/gluster/ovirt_new/data Status: Connected Total Number of entries: 2 Number of entries in heal pending: 2 Number of entries in split-brain: 0 Number of entries possibly healing: 0 Brick ovirt-h2-new.local:/gluster/ovirt_new/data Status: Connected Total Number of entries: 2 Number of entries in heal pending: 2 Number of entries in split-brain: 0 Number of entries possibly healing: 0 Entries not decreasing... Any help

2 1

Re: oVirt 4.2 how to upgrade
by Strahil Nikolov 24 Jun '21

24 Jun '21

Theoretically you most probably can, but you take the risk of being vulnerable to split-brain. Keep in mind that you can:- update gluster to the same version that is used on oVirt 4.4- update oVirt to 4.3.10 as this is the most tested migration scenario- reduce the volume and remove that 3rd node (don't forget to peer detach)- reinstall with EL8 and install gluster (same version) again. Add the brick and qait for the heal- create a new volume for the new HE- Stop the old HE and deploy the new one from the backup- Add the hosts to the new HE and migrate some of the VMs to free one of the old hosts- Reinstall the remaining hosts (one by one) to EL8 Best Regards,Strahil Nikolov On Thu, Jun 24, 2021 at 14:28, Fedele Stabile<fedele.stabile(a)fis.unical.it> wrote: I have a 3 node oVirt 4.2.1 cluster, i'm using a self-hosted engine architecture and storage-engine is on a glusterfs replica 3 of the cluster. The oldest CPU is SandyBridge family (E5-2609) and incidentally it has connectivity problems with IPMI NIC, but Hosted Engine HA is enabled and working. May I reduce the glusterfs replica to 2 and use one of the 3 nodes to begin the installation of ovirt 4.4 on that node? Fedele _______________________________________________ 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/6JWMAUPJQ5GLN…

1 1

[ANN] oVirt 4.4.7 Fifth Release Candidate is now available for testing
by Lev Veyde 24 Jun '21

24 Jun '21

oVirt 4.4.7 Fifth Release Candidate is now available for testing The oVirt Project is pleased to announce the availability of oVirt 4.4.7 Fifth Release Candidate for testing, as of June 24th, 2021. This update is the seventh in a series of stabilization updates to the 4.4 series. How to prevent hosts entering emergency mode after upgrade from oVirt 4.4.1 Note: Upgrading from 4.4.2 GA or later should not require re-doing these steps, if already performed while upgrading from 4.4.1 to 4.4.2 GA. These are only required to be done once. Due to Bug 1837864 <https://bugzilla.redhat.com/show_bug.cgi?id=1837864> - Host enter emergency mode after upgrading to latest build If you have your root file system on a multipath device on your hosts you should be aware that after upgrading from 4.4.1 to 4.4.7 you may get your host entering emergency mode. In order to prevent this be sure to upgrade oVirt Engine first, then on your hosts: 1. Remove the current lvm filter while still on 4.4.1, or in emergency mode (if rebooted). 2. Reboot. 3. Upgrade to 4.4.7 (redeploy in case of already being on 4.4.7). 4. Run vdsm-tool config-lvm-filter to confirm there is a new filter in place. 5. Only if not using oVirt Node: - run "dracut --force --add multipath” to rebuild initramfs with the correct filter configuration 6. Reboot. 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>. Important notes before you try it Please note this is a pre-release build. The oVirt Project makes no guarantees as to its suitability or usefulness. This pre-release must not be used in production. Installation instructions For installation instructions and additional information please refer to: https://ovirt.org/documentation/ This release is available now on x86_64 architecture for: * Red Hat Enterprise Linux 8.4 or similar * CentOS Stream 8 This release supports Hypervisor Hosts on x86_64 and ppc64le architectures for: * Red Hat Enterprise Linux 8.4 or similar will need the upcoming next batch update, providing an updated sanlock package. * CentOS Stream 8 * oVirt Node 4.4 based on CentOS Stream 8 (available for x86_64 only) See the release notes [1] for installation instructions and a list of new features and bugs fixed. Notes: - oVirt Appliance is already available based on CentOS Stream 8 - oVirt Node NG is already available based on CentOS Stream 8 Additional Resources: * Read more about the oVirt 4.4.7 release highlights: http://www.ovirt.org/release/4.4.7/ * 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.4.7/ [2] http://resources.ovirt.org/pub/ovirt-4.4-pre/iso/ -- Lev Veyde Senior Software Engineer, RHCE | RHCVA | MCITP Red Hat Israel <https://www.redhat.com> lev(a)redhat.com | lveyde(a)redhat.com <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>

1 0

oVirt and ARM
by Marko Vrgotic 24 Jun '21

24 Jun '21

Hi oVirt, Where can I find if there are any information about oVirt supporting arm64 CPU architecture? ----- kind regards/met vriendelijke groeten Marko Vrgotic Sr. System Engineer @ System Administration ActiveVideo o: +31 (35) 6774131 m: +31 (65) 5734174 e: m.vrgotic(a)activevideo.com<mailto:m.vrgotic@activevideo.com> w: www.activevideo.com<http://www.activevideo.com> ActiveVideo Networks BV. Mediacentrum 3745 Joop van den Endeplein 1.1217 WJ Hilversum, The Netherlands. The information contained in this message may be legally privileged and confidential. It is intended to be read only by the individual or entity to whom it is addressed or by their designee. If the reader of this message is not the intended recipient, you are on notice that any distribution of this message, in any form, is strictly prohibited. If you have received this message in error, please immediately notify the sender and/or ActiveVideo Networks, LLC by telephone at +1 408.931.9200 and delete or destroy any copy of this message.

1 0

Expected behavior when link of required VM networks down
by Gianluca Cecchi 24 Jun '21

24 Jun '21

Hello, suppose I have a cluster with required VM logical network setup. Suppose on hosts I have configured a bonding device with this logical network mapped on it. Suppose an active host for any reason loses the physical connectivity on this bond (both links down or problems with new network config impacting the bond, ecc) So from the VMs point of view, those having a vnic on this logical network will lose the connectivity, but I think they will not detect link down, correct? Is there any expected default action oVirt will take in respect of this scenario or not? Of course I expect to see events with messages about link down. But any automatic action such as live migration of impacted VMs for example? Any configurable one at oVirt level? Thanks, Gianluca

1 0

oVirt 4.2 how to upgrade
by Fedele Stabile 24 Jun '21

24 Jun '21

I have a 3 node oVirt 4.2.1 cluster, i'm using a self-hosted engine architecture and storage-engine is on a glusterfs replica 3 of the cluster. The oldest CPU is SandyBridge family (E5-2609) and incidentally it has connectivity problems with IPMI NIC, but Hosted Engine HA is enabled and working. May I reduce the glusterfs replica to 2 and use one of the 3 nodes to begin the installation of ovirt 4.4 on that node? Fedele

1 0

global ha maintenance status via rest api
by Markus Schaufler 24 Jun '21

24 Jun '21

Hello, I'd like to check the status of "global ha maintenance" via rest api. Can't find any hint on this in the api docs - only for enable/disable... any ideas? thanks!

1 0

[ANN] oVirt 4.4.7 Fourth Release Candidate is now available for testing
by Lev Veyde 24 Jun '21

24 Jun '21

oVirt 4.4.7 Fourth Release Candidate is now available for testing The oVirt Project is pleased to announce the availability of oVirt 4.4.7 Fourth Release Candidate for testing, as of June 18th, 2021. This update is the seventh in a series of stabilization updates to the 4.4 series. How to prevent hosts entering emergency mode after upgrade from oVirt 4.4.1 Note: Upgrading from 4.4.2 GA or later should not require re-doing these steps, if already performed while upgrading from 4.4.1 to 4.4.2 GA. These are only required to be done once. Due to Bug 1837864 <https://bugzilla.redhat.com/show_bug.cgi?id=1837864> - Host enter emergency mode after upgrading to latest build If you have your root file system on a multipath device on your hosts you should be aware that after upgrading from 4.4.1 to 4.4.7 you may get your host entering emergency mode. In order to prevent this be sure to upgrade oVirt Engine first, then on your hosts: 1. Remove the current lvm filter while still on 4.4.1, or in emergency mode (if rebooted). 2. Reboot. 3. Upgrade to 4.4.7 (redeploy in case of already being on 4.4.7). 4. Run vdsm-tool config-lvm-filter to confirm there is a new filter in place. 5. Only if not using oVirt Node: - run "dracut --force --add multipath” to rebuild initramfs with the correct filter configuration 6. Reboot. 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>. Important notes before you try it Please note this is a pre-release build. The oVirt Project makes no guarantees as to its suitability or usefulness. This pre-release must not be used in production. Installation instructions For installation instructions and additional information please refer to: https://ovirt.org/documentation/ This release is available now on x86_64 architecture for: * Red Hat Enterprise Linux 8.4 or similar * CentOS Stream 8 This release supports Hypervisor Hosts on x86_64 and ppc64le architectures for: * Red Hat Enterprise Linux 8.4 or similar * CentOS Stream 8 * oVirt Node 4.4 based on CentOS Stream 8 (available for x86_64 only) See the release notes [1] for installation instructions and a list of new features and bugs fixed. Notes: - oVirt Appliance is already available based on CentOS Stream 8 - oVirt Node NG is already available based on CentOS Stream 8 Additional Resources: * Read more about the oVirt 4.4.7 release highlights: http://www.ovirt.org/release/4.4.7/ * 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.4.7/ [2] http://resources.ovirt.org/pub/ovirt-4.4-pre/iso/ -- Lev Veyde Senior Software Engineer, RHCE | RHCVA | MCITP Red Hat Israel <https://www.redhat.com> lev(a)redhat.com | lveyde(a)redhat.com <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>

3 4