- Users - oVirt List Archives

oVirt 4.3 -> 4.4 Upgrade Path Questions
by Andrei Verovski 08 Jul '20

08 Jul '20

Hi ! I have 2-node oVirt 4.3 installation, with engine running as KVM guest on SuSE file server (not hosted engine). Nodes are manually installed on CentOS 7.x (further referred as old node #1 and #2). I’m going to add 1 additional node, and migrate system to CentOS 8.2 / oVirt 4.4. Is this correct roadmap, or something can be done in a better way? Here is my plan. 1) Upgrade oVirt Hosted Engine running under KVM / SuSE file server to CentOS 8.2 / oVirt 4.4. Or its better to install from scratch new CentOS 8.2/oVirt 4.4 and migrate database? 2) Install CentOS 8.2 and oVirt node 4.4 on new server (let’s name it node #3). 3) Migrate virtual machines from old node #1 to the new (#3). 4) Upgrade CentOS on old node #1 to v8.2, and oVirt from web interface. Will that work, or upgrade CentOS 7 -> 8 will render this process unmanageable due to removal of many components? 5) Migrate back virtual machines from node #3 to newly upgraded node #1. 6) Repeat step 4 and 5 for old node #2. I have set of custom shell and python scripts running on engine and nodes, so manual installation was a way to go. Thanks in advance for any suggestion(s) with best regards Andrei

4 4

[ANN] oVirt 4.4.1 is now generally available
by Lev Veyde 08 Jul '20

08 Jul '20

oVirt 4.4.1 is now generally available The oVirt project is excited to announce the general availability of oVirt 4.4.1 , as of July 8th, 2020. 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/NDSVUZSESOXEFJ… ) 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.1 Release? This update is the first in a series of stabilization updates to the 4.4 series. This release introduces a new monitoring solution that provides a user interface to oVirt DWH collected data using Grafana. This allows admins to track inventory, monitor performance and capacity trends, and easily identify and troubleshoot resources issues. Grafana is installed and configured during engine-setup and includes pre-built dashboards that are based on the data collected by the ovirt_engine_history PostgreSQL Data Warehouse database (BZ#1777877 <https://bugzilla.redhat.com/show_bug.cgi?id=1777877>). In oVirt 4.4.1 the maximum memory size for 64-bit x86_64 and ppc64/ppc64le VMs is now 6TB. For x86_64 this limit is applied also to VMs in 4.2 and 4.3 Cluster Levels. You can now use CentOS Stream as an alternative to CentOS Linux on non-production systems. This release is available now on x86_64 architecture for: - Red Hat Enterprise Linux 8.2 - CentOS Linux (or similar) 8.2 - CentOS Stream (tech preview) This release supports Hypervisor Hosts on x86_64 and ppc64le architectures for: - Red Hat Enterprise Linux 8.2 - CentOS Linux (or similar) 8.2 - CentOS Stream (tech preview) - oVirt Node 4.4 based on CentOS Linux 8.2 (available for x86_64 only) oVirt Node and Appliance have been updated, including: - oVirt 4.4.1: http://www.ovirt.org/release/4.4.1/ - CentOS Linux 8.2.2004: https://lists.centos.org/pipermail/centos-announce/2020-June/035756.html - CentOS Virt SIG updates including Advanced Virtualization 8.2 (qemu-kvm 4.2 <https://www.qemu.org/2019/12/13/qemu-4-2-0/>, libvirt 6.0.0 <https://libvirt.org/news.html#v6-0-0-2020-01-15>) - Wildfly 19.1.0: https://wildfly.org/news/2020/05/04/WildFly-1910-Released/ - Ansible 2.9.10: https://github.com/ansible/ansible/blob/stable-2.9/changelogs/CHANGELOG-v2.… - Glusterfs 7.6: https://docs.gluster.org/en/latest/release-notes/7.6/ See the release notes [1] for installation instructions and a list of new features and bugs fixed. Notes: - oVirt Appliance is already available for CentOS Linux 8 - oVirt Node NG is already available for CentOS Linux 8 Additional resources: - Read more about the oVirt 4.4.1 release highlights: http://www.ovirt.org/release/4.4.1/ - 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.1/ [2] http://resources.ovirt.org/pub/ovirt-4.4/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

rhv 4.3.9 - snapshots fail
by Markus Schaufler 08 Jul '20

08 Jul '20

Hi, I think we ran into this bug https://bugzilla.redhat.com/show_bug.cgi?id=1802277 and https://access.redhat.com/solutions/5174961 as we have exactly that problems and log-entries. As there are now several VMs that cannot create (or delete) snapshots accordingly we cannot do backups on that VMs. Are there any suggestions or workarounds in order that we can still backup them up? Thanks very much, Markus

2 1

Hosted engine can't start after changing cluster settings
by Patrick Lomakin 08 Jul '20

08 Jul '20

I changed the BIOS Type settings in the cluster settings section to UEFI BIOS, and hosted-engine does not start after rebooting. Although, before I made the changes, I looked in the engine at the /boot partition, which has the /efi directory. Is there any way to change the engine settings manually, and how can I connect to it (or to its partitions) to perform actions? I can't imagine how you can reinstall the engine without unplugging storage to import all virtual machines later. Losing data in virtual machines is a disaster for me.

2 1

Ovirt 4.3.10 Glusterfs SSD slow performance over 10GE
by jury cat 07 Jul '20

07 Jul '20

Hello all, I am using Ovirt 4.3.10 on Centos 7.8 with glusterfs 6.9 . My Gluster setup is of 3 hosts in replica 3 (2 hosts + 1 arbiter). All the 3 hosts are Dell R720 with Perc Raid Controller H710 mini(that has maximim throughtout 6Gbs) and with 2×1TB samsumg SSD in RAID 0. The volume is partitioned using LVM thin provision and formated XFS. The hosts have separate 10GE network cards for storage traffic. The Gluster Network is connected to this 10GE network cards and is mounted using Fuse Glusterfs(NFS is disabled).Also Migration Network is activated on the same storage network. The problem is that the 10GE network is not used at full potential by the Gluster. If i do live Migration of Vms i can see speeds of 7GB/s ~ 9GB/s. The same network tests using iperf3 reported 9.9GB/s , these exluding the network setup as a bottleneck(i will not paste all the iperf3 tests here for now). I did not enable all the Volume options from "Optimize for Virt Store", because of the bug that cant set volume cluster.granural-heal to enable(this was fixed in vdsm-4 40, but that is working only on Centos 8 with ovirt 4.4 ) . i whould be happy to know what are all these "Optimize for Virt Store" options, so i can set them manually. The speed on the disk inside the host using dd is b etween 1GB/s to 700Mbs. [root@host1 ~]# dd if=/dev/zero of=test bs=100M count=40 cou nt=80 status=progress 8074035200 bytes (8.1 GB) copied, 11.059372 s, 730 MB/s 80+0 records in 80+0 records out 8388608000 bytes (8.4 GB) copied, 11.9928 s, 699 MB/s The dd write test on the gluster volme inside the host is poor only ~ 120MB/s . During the dd test, if i look at Networks->Gluster network ->Hosts at Tx and Rx the network speed barerly reaches over 1Gbs (~1073 Mbs) out of maximum of 10000 Mbs. dd if=/dev/zero of=/rhev/data-center/mnt/glu sterSD/gluster1.domain.local\:_data/test bs=100M count=80 status=progress 8283750400 bytes (8.3 GB) copied, 71.297942 s, 116 MB/s 80+0 records in 80+0 records out 8388608000 bytes (8.4 GB) copied, 71.9545 s, 117 MB/s I have attached my Gluster volume settings and mount options. Thanks, Emy

4 10

Running Self Hosted-Engine on the same iSCSI target as other Storage Domains
by Erez Zarum 07 Jul '20

07 Jul '20

We are using Dell SC (Storage) with iSCSI with oVirt, it is impossible to create a new Target Portal with a specific LUN so it's impossible to isolate the SE LUN from other LUNs that are in use by other Storage Domains. According to the documentations this is not a best practice, while searching i ran into that specific issue but it seems to be solved. Is it still by best practice when using oVirt 4.4 to use a whole different target for the SE? If it is not possible giving the current envrionment restrictions is the only option for us is to attach a few disks to each servers and create a small gluster cluster (volume) just for the SE?

2 1

Re: broker.log not rotating
by Strahil Nikolov 07 Jul '20

07 Jul '20

Yes, ovirt-ha-broker and ovirt-ha-agent take care of HostedEngine to be up and running and in case something goes bad - to be migrated away. Best Regards, Strahil Nikolov На 3 юли 2020 г. 7:53:14 GMT+03:00, Anton Louw via Users <users(a)ovirt.org> написа: >Hi Everybody, > >Thanks for all the responses. So I managed to truncate the log. I just >want to make sure, the ‘ovirt-ha-agent’ service is only for the hosted >engine correct? > >I can still migrate machines between the hosts, so it should then not >impact the VMs? > >Thanks > > >Anton Louw >Cloud Engineer: Storage and Virtualization >______________________________________ >D: 087 805 1572 | M: N/A >A: Rutherford Estate, 1 Scott Street, Waverley, Johannesburg >anton.louw(a)voxtelecom.co.za > >www.vox.co.za > > > >From: Darrell Budic <budic(a)onholyground.com> >Sent: 02 July 2020 19:56 >To: Anton Louw <Anton.Louw(a)voxtelecom.co.za> >Cc: users(a)ovirt.org >Subject: Re: [ovirt-users] broker.log not rotating > >They’re just log files, so generally safe to delete. You may want to >take a look at the huge one though, see what’s up. I had a similar >problem that turned out to be a broken HA agent install, cleaned and >reinstalled and it went back to the same volume of logs as the others. > >Now I need to check if they added logrotate.d config files for it to >clean those up, hum. > > -Darrell > > >On Jul 2, 2020, at 12:00 AM, Anton Louw via Users ><users(a)ovirt.org<mailto:users@ovirt.org>> wrote: > > > >Hi All, > >I had a space alert on one of my nodes this morning, and when I looked >around, I saw that var/log/ovirt-hosted-engine-ha/broker.log was >sitting at around 30GB. Does anybody know if it is safe to delete the >log file? Or is there another process that I should follow? > >I had a look at my other nodes, and the broker.log file does not exceed >4GB. > >Thank you > >Anton Louw >Cloud Engineer: Storage and Virtualization at Vox >________________________________ >T: 087 805 0000 | D: 087 805 1572 >M: N/A >E: anton.louw(a)voxtelecom.co.za<mailto:anton.louw@voxtelecom.co.za> >A: Rutherford Estate, 1 Scott Street, Waverley, Johannesburg >www.vox.co.za<http://www.vox.co.za/> > >[F]<https://www.facebook.com/voxtelecomZA> > >[T]<https://www.twitter.com/voxtelecom> > >[I]<https://www.instagram.com/voxtelecomza/> > >[L]<https://www.linkedin.com/company/voxtelecom> > >[Y]<https://www.youtube.com/user/VoxTelecom> > > >[#VoxBrand]<https://www.vox.co.za/fibre/fibre-to-the-home/?prod=HOME> > >Disclaimer >The contents of this email are confidential to the sender and the >intended recipient. Unless the contents are clearly and entirely of a >personal nature, they are subject to copyright in favour of the holding >company of the Vox group of companies. Any recipient who receives this >email in error should immediately report the error to the sender and >permanently delete this email from all storage devices. > >This email has been scanned for viruses and malware, and may have been >automatically archived by Mimecast Ltd, an innovator in Software as a >Service (SaaS) for business. Providing a safer and more useful place >for your human generated data. Specializing in; Security, archiving and >compliance. To find out more Click >Here<https://www.voxtelecom.co.za/security/mimecast/?prod=Enterprise>. > > >_______________________________________________ >Users mailing list -- users(a)ovirt.org<mailto:users@ovirt.org> >To unsubscribe send an email to >users-leave(a)ovirt.org<mailto:users-leave@ovirt.org> >Privacy Statement: >https://www.ovirt.org/privacy-policy.html<https://www.ovirt.org/privacy-policy.html> >oVirt Code of Conduct: >https://www.ovirt.org/community/about/community-guidelines/<https://www.ovirt.org/community/about/community-guidelines/> >List Archives: >https://lists.ovirt.org/archives/list/users@ovirt.org/message/4L6OOVVW6KOSB…<https://lists.ovirt.org/archives/list/users@ovirt.org/message/4L6OOVVW6KOSB…>

1 0

oVirt 4.4.0, slave interfaces are down after a reboot
by Erez Zarum 07 Jul '20

07 Jul '20

Fresh installation of oVirt 4.4.0 (using the ISO), after restarting an host, the host comes up but the slave interfaces of a bond remains in down state. The only way to bring it up is to login via IPMI and restart the "NetworkManager" service. Weird thing, after this, the host says that it's network is out of sync, this happens on a network that is marked as "migration network", what is out of sync is the gateway. I have restart the host again (this happens on all hosts) and i can see that after a restart the NetworkManager state (nmcli c show bond0.421 as example) does not list the routes, after syncing the routes are there.

2 2

iSCSI array "Storage domain does not exist" error after array reboot
by Kevin Doyle 07 Jul '20

07 Jul '20

I am running a hosted engine using iscsi. I had to reboot the array, I took down all the VM's and put the VM data storage into maintenance mode. I also put the hosted engine "hosted-engine --set-maintenance --mode =global" and shut down the engine "hosted-engine --vm-shutdown" I also stopped the broker and agent systemctl stop ovirt-ha-broker' ; 'systemctl stop ovirt-ha-agent' The array was rebooted. I started the broker and agent systemctl start ovirt-ha-broker' ; 'systemctl start ovirt-ha-agent' However I now see errors in the vdsm log INFO (jsonrpc/4) [storage.TaskManager.Task] (Task='76547cc5-e4f0-454c-ac46-c341e7f6d54c') aborting: Task is aborted: "Storage domain does not exist: (u'5626eba7-ebd8-4578-baf0-ca4f4af5889b',)" - code 358 (task:1181) 2020-07-07 14:01:25,098+0100 ERROR (jsonrpc/4) [storage.Dispatcher] FINISH prepareImage error=Storage domain does not exist: (u'5626eba7-ebd8-4578-baf0-ca4f4af5889b',) (dispatcher:83) 2020-07-07 14:01:25,098+0100 INFO (jsonrpc/4) [jsonrpc.JsonRpcServer] RPC call Image.prepare failed (error 358) in 0.07 seconds (__init__:312) INFO (vmrecovery) [vdsm.api] START getConnectedStoragePoolsList(options=None) from=internal, task_id=93d7e2d6-17ee-4370-b8c4-fb32a3887021 (api:48) 2020-07-07 14:01:25,592+0100 INFO (vmrecovery) [vdsm.api] FINISH getConnectedStoragePoolsList return={'poollist': []} from=internal, task_id=93d7e2d6-17ee-4370-b8c4-fb32a3887021 (api:54) 2020-07-07 14:01:25,592+0100 INFO (vmrecovery) [vds] recovery: waiting for storage pool to go up (clientIF:709) I have 6 hosts. I have tried rebooting them all, I have tried just running 1 host that was originally hosting the engine, but I cannot bring up the hosted engine. Has anyone any ideas ? how to reconnect the storage domain The hosted engine had its own iscsi disk separate from the VM's thanks Kevin

2 1

How to use sysprep to create Windows templates
by wodel youchi 07 Jul '20

07 Jul '20

Hi, I need to create some Windows Templates for my client, and I am not quite familiar with the Windows sysprep installations. I read the "Sealing a Windows Virtual Machine for Deployment as a Template" on the Virtual Machine Management Guide. What I don't understand is the process of sealing a Windows VM. When should I use the /usr/share/ovirt-engine/conf/sysprep/sysprep.* files? at the creation of the VM that will be a template at the end? or at the creation of new VMs based on the template? When should I use the /etc/ovirt-engine/osinfo.conf.d/xx.files.properties? at the creation of the VM that will be a template at the end? or at the creation of new VMs based on the template? What is the difference between : "Use Cloud-Init/Sysprep" in the VM edit window and the RUN Once window? For me it is not clear, could someone help me to understand. Regards.

2 2