- Users - oVirt List Archives

How do you manage OVN?
by Alex McWhirter 20 Nov '20

20 Nov '20

I'm not sure if I' missing something, but it seems there is no way built in to oVirt to manage OVN outside of network / subnet creation. In particular routing both between networks and to external networks. Of course you have the OVN utilities, but it seems that the provider API is the preffered method of interaction? As far as i can tell, the only utility that can use this API as intended is ManageIQ, which is a bit a behemoth if you only need the OVN portion of things. So is that it then? Interface with the API directly or use ManageIQ? Just curious what others are doing in regards to OVN.

2 1

Need documentation on how to use grafana with ovirt
by wodel youchi 20 Nov '20

20 Nov '20

Hi, Is there any documentation explaining how to use grafana portal to extract metrics data from ovirt ? Regards.

2 1

Re: ovirt 4.3 - locked image vm - unable to remove a failed deploy of a guest dom
by 3c Monitor 20 Nov '20

20 Nov '20

Hi, anyone with an idea on what else I can do? Thanks a lot.

1 0

EPYC CPU not being detected correctly on cluster
by Vinícius Ferrão 19 Nov '20

19 Nov '20

Hi I've an strange issue with two hosts (not using the hypervisor image) with EPYC CPUs, on the engine I got this message: The host CPU does not match the Cluster CPU Type and is running in a degraded mode. It is missing the following CPU flags: model_EPYC. Please update the host CPU microcode or change the Cluster CPU Type. But it is an EPYC CPU, the firmware is updated to the latest versions, but for some reason oVirt does not like it. Here's the relevant output from VDSM: "cpuCores": "128", "cpuFlags": "ibs,vme,abm,sep,ssse3,perfctr_core,sse4_2,skip-l1dfl-vmentry,cx16,pae,misalignsse,avx2,smap,movbe,vgif,rdctl-no,extapic,clflushopt,de,sse4_1,xsaveerptr,perfctr_llc,fma,mca,sse,rdtscp,monitor,umip,mwaitx,cr8_legacy,mtrr,stibp,bmi2,pclmulqdq,amd-ssbd,lbrv,pdpe1gb,constant_tsc,vmmcall,f16c,ibrs,fsgsbase,invtsc,nopl,lm,3dnowprefetch,smca,ht,tsc_adjust,popcnt,cpb,bmi1,mmx,arat,aperfmperf,bpext,cqm_occup_llc,virt-ssbd,tce,pse,xsave,xgetbv1,topoext,sha_ni,amd_ppin,rdrand,cpuid,tsc_scale,extd_apicid,cqm,rep_good,tsc,sse4a,flushbyasid,pschange-mc-no,mds-no,ibpb,smep,clflush,tsc-deadline,fxsr,pat,avx,pfthreshold,v_vmsave_vmload,osvw,xsavec,cdp_l3,clzero,svm_lock,nonstop_tsc,adx,hw_pstate,spec-ctrl,arch-capabilities,xsaveopt,skinit,rdt_a,svm,rdpid,lahf_lm,fpu,rdseed,fxsr_opt,sse2,nrip_save,vmcb_clean,sme,cat_l3,cqm_mbm_local,irperf,overflow_recov,avic,mce,mmxext,msr,cx8,hypervisor,wdt,mba,nx,decodeassists,cmp_legacy,x2apic,perfctr_nb,succor,pni,xsaves,clwb,cqm_llc,syscall,apic,pge,npt,pse36,cmov,ssbd,pausefilter,sev,aes,wbnoinvd,cqm_mbm_total,spec_ctrl,model_qemu32,model_Opteron_G3,model_Nehalem-IBRS,model_qemu64,model_Conroe,model_kvm64,model_Penryn,model_SandyBridge,model_pentium,model_pentium2,model_kvm32,model_Nehalem,model_Opteron_G2,model_pentium3,model_Opteron_G1,model_SandyBridge-IBRS,model_486,model_Westmere-IBRS,model_Westmere", "cpuModel": "AMD EPYC 7H12 64-Core Processor", "cpuSockets": "2", "cpuSpeed": "3293.405", "cpuThreads": "256", Any ideia on why ou what to do to fix it? Thanks,

1 0

[ANN] oVirt 4.4.4 Second Release Candidate is now available for testing
by Lev Veyde 19 Nov '20

19 Nov '20

oVirt 4.4.4 Second Release Candidate is now available for testing The oVirt Project is pleased to announce the availability of oVirt 4.4.4 Second Release Candidate for testing, as of November 19th, 2020. This update is the fourth 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.4 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.4 (redeploy in case of already being on 4.4.4). 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.2 or newer * CentOS Linux (or similar) 8.2 or newer This release supports Hypervisor Hosts on x86_64 and ppc64le architectures for: * Red Hat Enterprise Linux 8.2 or newer * CentOS Linux (or similar) 8.2 or newer * oVirt Node 4.4 based on CentOS Linux 8.2 (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 for CentOS Linux 8 - oVirt Node NG is already available for CentOS Linux 8 Additional Resources: * Read more about the oVirt 4.4.4 release highlights: http://www.ovirt.org/release/4.4.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.4.4/ [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 KUBEVIRT
by Andre Meyer Pflug 19 Nov '20

19 Nov '20

Is there someone who has done an NON PERSISTANT VDI over oVirt using kubevirt (on OKD) as the infraestructure for vm's? We plan to do a 1.000.000 concurrent users deployment... Any help is welcome! Kind regards, Andre Meyer Pflug DDESK LLC

3 2

Self Hosted Engine a single Bare Metal Server
by LS CHENG 19 Nov '20

19 Nov '20

Hi We are planning to set up a single ovirt node for testing. It is a single Bare Metal Server. I wonder if there is any problem setting up a Self Hosted Engine in this Bare Metal (there is no HA but we don't need it in this case)? I know it is probably not the best practice but it is for training and testing purposes. Thank you

1 0

Fix corrupt self-hosted engine
by Alex K 19 Nov '20

19 Nov '20

Hi all, I have a corrupt self-hosted engine (with several file system errors, postgres not able to start) and thus it does not give access to the web UI. This happened following an unlucky split brain resolution (I am running 2 nodes). The two hosts are running VMs also which I would like to keep running as they are needed. When trying to boot into rescue mode (using systemd.unit=emergency.target boot parameter) I get a cursor and nothing else. I have backups of engine files with scope all (using the engine-backup tool). What is the best approach to try and fix the engine or redeploy. Thanks for any help. Alex

2 2

Re: oVirt Node Crash
by Anton Louw 19 Nov '20

19 Nov '20

Hi Sandro, Have you perhaps seen anything in the SOS report that could shed some light on the issues? 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: Anton Louw Sent: 16 November 2020 07:30 To: Sandro Bonazzola <sbonazzo(a)redhat.com>; Arik Hadas <ahadas(a)redhat.com>; Dominik Holler <dholler(a)redhat.com> Cc: users(a)ovirt.org; Johan Koen <Johan.Koen(a)voxtelecom.co.za> Subject: RE: [ovirt-users] oVirt Node Crash I have also attached the SOS report as requested From: Anton Louw Sent: 16 November 2020 06:54 To: Sandro Bonazzola <sbonazzo(a)redhat.com<mailto:sbonazzo@redhat.com>>; Arik Hadas <ahadas(a)redhat.com<mailto:ahadas@redhat.com>>; Dominik Holler <dholler(a)redhat.com<mailto:dholler@redhat.com>> Cc: users(a)ovirt.org<mailto:users@ovirt.org>; Johan Koen <Johan.Koen(a)voxtelecom.co.za<mailto:Johan.Koen@voxtelecom.co.za>> Subject: RE: [ovirt-users] oVirt Node Crash Hi Sandro, Thanks for the response. I logged onto oVirt this morning, and I see the node is in a “Unassigned” state. I can ping it, but cannot SSH, so there is something that is causing the host to be unresponsive. On Saturday after I sent the mail, I opened a console to the node, and I saw the below entries before logging in: audit:backlog limit exceeded I the tried the solution of increasing the buffer size in the audit.rules file in /etc/audit/rules.d/ , as per below, but it did not resolve the issue. ## First rule - delete all -D ## Increase the buffers to survive stress events. ## Make this bigger for busy systems -b 8192 ## Set failure mode to syslog -f 1 Is it possible to upgrade the node to 4.4 while the engine is still on 4.3? Thanks From: Sandro Bonazzola <sbonazzo(a)redhat.com<mailto:sbonazzo@redhat.com>> Sent: 13 November 2020 18:39 To: Anton Louw <Anton.Louw(a)voxtelecom.co.za<mailto:Anton.Louw@voxtelecom.co.za>>; Arik Hadas <ahadas(a)redhat.com<mailto:ahadas@redhat.com>>; Dominik Holler <dholler(a)redhat.com<mailto:dholler@redhat.com>> Cc: users(a)ovirt.org<mailto:users@ovirt.org>; Johan Koen <Johan.Koen(a)voxtelecom.co.za<mailto:Johan.Koen@voxtelecom.co.za>> Subject: Re: [ovirt-users] oVirt Node Crash Il giorno ven 13 nov 2020 alle ore 17:37 Sandro Bonazzola <sbonazzo(a)redhat.com<mailto:sbonazzo@redhat.com>> ha scritto: Il giorno ven 13 nov 2020 alle ore 13:38 Anton Louw via Users <users(a)ovirt.org<mailto:users@ovirt.org>> ha scritto: Hi Everybody, I have built a new host which has been running fine for the last couple of days. I noticed today that the host crashed, but it is not giving me a reason as to why. It happened at 13:45 today, but I have given time before that on the logs as well. Is there something I am missing here? Not related to the crash, but I see in the logs that 5 out of 20 guests have qemu guest agent not responding. Also you seem to have some issues with some firewalld rules. (Maybe +Dominik Holler<mailto:dholler@redhat.com> would like to have a look) I don't see anything explaining why the host got rebooted. Still related to guest agent I find a bit alarming the following lines: Nov 13 13:29:34 jb2-node03 libvirtd: 2020-11-13 11:29:34.294+0000: 12603: error : qemuDomainAgentAvailable:9144 : Guest agent is not responding: QEMU guest agent is not connected Nov 13 13:29:34 jb2-node03 vdsm[13843]: ERROR Shutdown by QEMU Guest Agent failed#012Traceback (most recent call last):#012 File "/usr/lib/python2.7/site-packages/vdsm/virt/vm.py", line 5304, in qemuGuestAgentShutdown#012 self._dom.shutdownFlags(libvirt.VIR_DOMAIN_SHUTDOWN_GUEST_AGENT)#012 File "/usr/lib/python2.7/site-packages/vdsm/virt/virdomain.py", line 100, in f#012 ret = attr(*args, **kwargs)#012 File "/usr/lib/python2.7/site-packages/vdsm/common/libvirtconnection.py", line 131, in wrapper#012 ret = f(*args, **kwargs)#012 File "/usr/lib/python2.7/site-packages/vdsm/common/function.py", line 94, in wrapper#012 return func(inst, *args, **kwargs)#012 File "/usr/lib64/python2.7/site-packages/libvirt.py", line 2517, in shutdownFlags#012 if ret == -1: raise libvirtError ('virDomainShutdownFlags() failed', dom=self)#012libvirtError: Guest agent is not responding: QEMU guest agent is not connected Nov 13 13:29:42 jb2-node03 kernel: vlan0077: port 11(vnet15) entered disabled state Nov 13 13:29:42 jb2-node03 kernel: device vnet15 left promiscuous mode Nov 13 13:29:42 jb2-node03 kernel: vlan0077: port 11(vnet15) entered disabled state Nov 13 13:29:42 jb2-node03 NetworkManager[6027]: <info> [1605266982.6539] device (vnet15): state change: disconnected -> unmanaged (reason 'unmanaged', sys-iface-state: 'removed') Nov 13 13:29:42 jb2-node03 NetworkManager[6027]: <info> [1605266982.6550] device (vnet15): released from master device vlan0077 Nov 13 13:29:42 jb2-node03 libvirtd: 2020-11-13 11:29:42.669+0000: 12557: error : qemuMonitorIO:718 : internal error: End of file from qemu monitor +Arik Hadas<mailto:ahadas@redhat.com> any clue? About the crash, can you please provide full sos report from the host? the log you provided is not enough to understand what caused the reported crash Also, given python2 is used here, I assume you're on 4.3 or older. I would recommend to upgrade to 4.4 as soon as practical. Thanks 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/XMRUDMRBYZKUJ…<https://lists.ovirt.org/archives/list/users@ovirt.org/message/XMRUDMRBYZKUJ…> -- Sandro Bonazzola MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA<https://www.redhat.com/> sbonazzo(a)redhat.com<mailto:sbonazzo@redhat.com> [https://static.redhat.com/libs/redhat/brand-assets/2/corp/logo--200.png]<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. <https://mojo.redhat.com/docs/DOC-1199578> -- Sandro Bonazzola MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA<https://www.redhat.com/> sbonazzo(a)redhat.com<mailto:sbonazzo@redhat.com> [https://static.redhat.com/libs/redhat/brand-assets/2/corp/logo--200.png]<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. <https://mojo.redhat.com/docs/DOC-1199578>

2 3

How to create a backup in event of hardware failure of a single hosted engine?
by ernestclydeachua＠gmail.com 18 Nov '20

18 Nov '20

Hello everyone, Currently we have a single bare metal that hosts oVirt and glusterFS which later on to be converted to a 3 nodes for HCI, currently another bare metal is coming this week and was planning to initially create it as a backup. is it possible to deploy a new hosted engine then create a gluster volume for 1st one as a backup domain then attach it to the new one if hardware failure occurred, or there is another kind of setup that can be done?

3 4