- Users - oVirt List Archives

Feedback needed: Admin Portal navigation changes
by Sandro Bonazzola 04 Feb '20

04 Feb '20

Greetings from the Red Hat Virtualization/oVirt UX team! We are conducting a short survey about the placement of some of the navigation items in RHV/oVirt Admin Portal. The answers you provide will have a direct impact on the future of RHV/oVirt user experience. Follow this link to the Survey: Take the Survey Or copy and paste the URL below into your internet browser: https://redhatdg.co1.qualtrics.com/jfe/form/SV_cIlrs1A7D1lK7jL?Avenue=team Thank you for your time and feedback. Privacy policy: https://www.ovirt.org/privacy-policy.html -- 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.*

1 0

ESXi 6.7 as a nested VM on top of oVirt cluster.
by branimirp＠gmail.com 03 Feb '20

03 Feb '20

Hello list I am wondering if anyone has tried this before? I am trying to consolidate my lab to an oVirt cluster which consists of oVirt (4.3.8) and 2 KVM hypervisors (CentOS 7.7.). Among other things, one of my efforts is a small ESXi + vCenter lab. In addition, I have a standalone KVM hypervisor. I can run nested ESXi 6.7 on top of the standalone KVM hypervisor (with nested KVM enabled) without any problem. However, on top of oVirt-controlled KVMs I have some issues. The hypervisors have nested kvm support enabled via vdsm hooks. qemu emulates e1000 for a nested ESXi vm. ESXi installation process goes smooth but as soon as I enable management network and restart it, the nested ESXi cannot communicate with the outside world (DNS ping cannot pass). Also https connection to VMWare ESXi web gui and ping to the ESXi also fail. I noticed on my client machine, that ARP requests are incomplete for ESXI as well. Within oVirt, I see no packet drops in "Network interface" tab for the nested ESXi. In addition, I have a few, ordinary, non-nested VMs running on the same network as the nested vm and I can normally establish connection to those machines. Additionally, as a test, I created a nested KVM vm on top of the oVirt cluster, same network as the nested ESXi and it works as expected - can spin VMs, can connect to it. The network assigned to the nested ESXi has a "No network filter" vNic profile applied. I tried to google for a solution but found only this: https://github.com/mechinn/kvmhidden - not sure if this is the solution at all (also, I wonder if this is still up-to-date after 3+ years)? Could I please ask if anyone tried something similar and experienced this problem? Is there any additional configuration that I should apply to the oVirt cluster? Thank you very much in advance! Regards, Branimir

2 2

Looking for some feedback on navigation within oVirt
by Laura Wright 03 Feb '20

03 Feb '20

Greetings from the Red Hat Virtualization UX team! We are conducting a short survey about the placement of some of the navigation items in RHV(o/Virt) Admin Portal. The answers you provide will have a direct impact on the future of RHV's user experience. Follow this link to the Survey: Take the Survey <https://redhatdg.co1.qualtrics.com/jfe/form/SV_cIlrs1A7D1lK7jL?Avenue=team> Or copy and paste the URL below into your internet browser: https://redhatdg.co1.qualtrics.com/jfe/form/SV_cIlrs1A7D1lK7jL?Avenue=team Thank you for your time and feedback. Please let me know if you have any questions. -- Laura Wright She/Her/Hers UXD Team Red Hat Massachusetts <https://www.redhat.com/> 314 Littleton Rd lwright(a)redhat.com <https://www.redhat.com/>

1 0

Re: Power Management - drac5
by eevans＠digitaldatatechs.com 03 Feb '20

03 Feb '20

I enabled ipmi with administrator and it worked. Thank you so much!!! Eric Evans Digital Data Services LLC. 304.660.9080 -----Original Message----- From: Robert Webb <rwebb(a)ropeguru.com> Sent: Monday, February 03, 2020 1:30 PM To: Jayme <jaymef(a)gmail.com> Cc: users <users(a)ovirt.org> Subject: [ovirt-users] Re: Power Management - drac5 ipmi over lan is allowed, and the user is the root user with admin access. Also the channel privilege level under ipmi is Administrator. Will check via cli to see what I get. ________________________________________ From: Jayme <jaymef(a)gmail.com> Sent: Monday, February 3, 2020 1:23 PM To: Robert Webb Cc: users Subject: Re: [ovirt-users] Power Management - drac5 Also make sure you have "Enable IPMI Over LAN" enabled under idrac settings. On Mon, Feb 3, 2020 at 2:15 PM Jayme <jaymef(a)gmail.com<mailto:jaymef@gmail.com>> wrote: I recall having a problem similar to this before and it was related to the user roles/permissions in iDrac. Check what access rights the user has. If that leads no where you might have some luck testing manually using the fence_idrac5 CLI tool directly on one of the oVirt hosts On Mon, Feb 3, 2020 at 2:09 PM Robert Webb <rwebb(a)ropeguru.com<mailto:rwebb@ropeguru.com>> wrote: I have 3 Dell R410's with iDrac6 Enterprise capability. I am trying to get power management set up but the test will not pass and I am not finding the docs very helpful. I have put in the IP, user name, password, and drac5 as the type. I have tested both with and without secure checked and always get, "Test failed: Internal JSON-RPC error". idrac log shows: 2020 Feb 3 17:41:22 os[19772] root closing session from 192.168.1.12 2020 Feb 3 17:41:17 os[19746] root login from 192.168.1.12 Can someone please guide me in the right direction? _______________________________________________ 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/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/RKFEK2ORWOODC… _______________________________________________ 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/N2EEZKP6REGKM…

1 0

Re: Power Management - drac5
by Jayme 03 Feb '20

03 Feb '20

I recall having a problem similar to this before and it was related to the user roles/permissions in iDrac. Check what access rights the user has. If that leads no where you might have some luck testing manually using the fence_idrac5 CLI tool directly on one of the oVirt hosts On Mon, Feb 3, 2020 at 2:09 PM Robert Webb <rwebb(a)ropeguru.com> wrote: > I have 3 Dell R410's with iDrac6 Enterprise capability. I am trying to get > power management set up but the test will not pass and I am not finding the > docs very helpful. > > I have put in the IP, user name, password, and drac5 as the type. I have > tested both with and without secure checked and always get, "Test failed: > Internal JSON-RPC error". > > idrac log shows: > > 2020 Feb 3 17:41:22 os[19772] root closing session from > 192.168.1.12 > 2020 Feb 3 17:41:17 os[19746] root login from 192.168.1.12 > > Can someone please guide me in the right direction? > > _______________________________________________ > 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/RKFEK2ORWOODC… >

2 2

Power Management - drac5
by Robert Webb 03 Feb '20

03 Feb '20

I have 3 Dell R410's with iDrac6 Enterprise capability. I am trying to get power management set up but the test will not pass and I am not finding the docs very helpful. I have put in the IP, user name, password, and drac5 as the type. I have tested both with and without secure checked and always get, "Test failed: Internal JSON-RPC error". idrac log shows: 2020 Feb 3 17:41:22 os[19772] root closing session from 192.168.1.12 2020 Feb 3 17:41:17 os[19746] root login from 192.168.1.12 Can someone please guide me in the right direction?

1 0

Understanding ovirt memory management which appears incorrect
by divan＠santanas.co.za 03 Feb '20

03 Feb '20

Hi All, A question regarding memory management with ovirt. I know memory can be complicated hence I'm asking the experts. :) Two examples of where it looks - to me - that memory management from ovirt perspective is incorrect. This is resulting in us not getting as much out of a host as we'd expect. ## Example 1: host: dev-cluster-04 I understand the mem on the host to be: 128G total (physical) 68G used 53G available 56G buff/cache I understand therefore 53G should still be available to allocate (approximately, minus a few things). ``` DEV [root@dev-cluster-04:~] # free -m total used free shared buff/cache available Mem: 128741 68295 4429 4078 56016 53422 Swap: 12111 1578 10533 DEV [root@dev-cluster-04:~] # cat /proc/meminfo MemTotal: 131831292 kB MemFree: 4540852 kB MemAvailable: 54709832 kB Buffers: 3104 kB Cached: 5174136 kB SwapCached: 835012 kB Active: 66943552 kB Inactive: 5980340 kB Active(anon): 66236968 kB Inactive(anon): 5713972 kB Active(file): 706584 kB Inactive(file): 266368 kB Unevictable: 50036 kB Mlocked: 54132 kB SwapTotal: 12402684 kB SwapFree: 10786688 kB Dirty: 812 kB Writeback: 0 kB AnonPages: 67068548 kB Mapped: 143880 kB Shmem: 4176328 kB Slab: 52183680 kB SReclaimable: 49822156 kB SUnreclaim: 2361524 kB KernelStack: 20000 kB PageTables: 213628 kB NFS_Unstable: 0 kB Bounce: 0 kB WritebackTmp: 0 kB CommitLimit: 78318328 kB Committed_AS: 110589076 kB VmallocTotal: 34359738367 kB VmallocUsed: 859104 kB VmallocChunk: 34291324976 kB HardwareCorrupted: 0 kB AnonHugePages: 583680 kB CmaTotal: 0 kB CmaFree: 0 kB HugePages_Total: 0 HugePages_Free: 0 HugePages_Rsvd: 0 HugePages_Surp: 0 Hugepagesize: 2048 kB DirectMap4k: 621088 kB DirectMap2M: 44439552 kB DirectMap1G: 91226112 kB ``` The ovirt engine, compute -> hosts view shows s4-dev-cluster-01 as 93% memory utilised. Clicking on the node says: Physical Memory: 128741 MB total, 119729 MB used, 9012 MB free So ovirt engine says 9G free. The OS reports 4G free but 53G available. Surely ovirt should be looking at available memory? This is a problem, for instance, when trying to run a VM, called dev-cassandra-01, with mem size 24576, max mem 24576 and mem guarantee set to 10240 on this host it fails with: ``` Cannot run VM. There is no host that satisfies current scheduling constraints. See below for details: The host dev-cluster-04.fnb.co.za did not satisfy internal filter Memory because its available memory is too low (19884 MB) to run the VM. ``` To me this looks blatantly wrong. The host has 53G available according to free -m. Guessing I'm missing something, unless this is some sort of bug? versions: ``` engine: 4.3.7.2-1.el7 host: OS Version: RHEL - 7 - 6.1810.2.el7.centos OS Description: CentOS Linux 7 (Core) Kernel Version: 3.10.0 - 957.12.1.el7.x86_64 KVM Version: 2.12.0 - 18.el7_6.3.1 LIBVIRT Version: libvirt-4.5.0-10.el7_6.7 VDSM Version: vdsm-4.30.13-1.el7 SPICE Version: 0.14.0 - 6.el7_6.1 GlusterFS Version: [N/A] CEPH Version: librbd1-10.2.5-4.el7 Open vSwitch Version: openvswitch-2.10.1-3.el7 Kernel Features: PTI: 1, IBRS: 0, RETP: 1, SSBD: 3 VNC Encryption: Disabled ``` ## Example 2: A ovirt host with two VMs: According to the host, it has 128G of physical memory of which 56G is used, 69G is buff/cache and 65G is available. As is shown here: ``` LIVE [root@prod-cluster-01:~] # cat /proc/meminfo MemTotal: 131326836 kB MemFree: 2630812 kB MemAvailable: 66573596 kB Buffers: 2376 kB Cached: 5670628 kB SwapCached: 151072 kB Active: 59106140 kB Inactive: 2744176 kB Active(anon): 58099732 kB Inactive(anon): 2327428 kB Active(file): 1006408 kB Inactive(file): 416748 kB Unevictable: 40004 kB Mlocked: 42052 kB SwapTotal: 4194300 kB SwapFree: 3579492 kB Dirty: 0 kB Writeback: 0 kB AnonPages: 56085040 kB Mapped: 121816 kB Shmem: 4231808 kB Slab: 65143868 kB SReclaimable: 63145684 kB SUnreclaim: 1998184 kB KernelStack: 25296 kB PageTables: 148336 kB NFS_Unstable: 0 kB Bounce: 0 kB WritebackTmp: 0 kB CommitLimit: 69857716 kB Committed_AS: 76533164 kB VmallocTotal: 34359738367 kB VmallocUsed: 842296 kB VmallocChunk: 34291404724 kB HardwareCorrupted: 0 kB AnonHugePages: 55296 kB CmaTotal: 0 kB CmaFree: 0 kB HugePages_Total: 0 HugePages_Free: 0 HugePages_Rsvd: 0 HugePages_Surp: 0 Hugepagesize: 2048 kB DirectMap4k: 722208 kB DirectMap2M: 48031744 kB DirectMap1G: 87031808 kB LIVE [root@prod-cluster-01:~] # free -m total used free shared buff/cache available Mem: 128248 56522 2569 4132 69157 65013 Swap: 4095 600 3495 ``` However the compute -> hosts ovirt screen shows this node as 94% memory. Clicking compute -> hosts -> prod-cluster-01 -> general says: Physical Memory: 128248 MB total, 120553 MB used, 7695 MB free Swap Size: 4095 MB total, 600 MB used, 3495 MB free The physical memory in the above makes no sense to me. Unless it includes caches which I would think it shouldn't. This host has just two VMs: LIVE [root@prod-cluster-01:~] # virsh -c qemu:///system?authfile=/etc/ovirt-hosted-engine/virsh_auth.conf list Id Name State ---------------------------------------------------- 35 prod-box-18 running 36 prod-box-11 running Moreover each VM has 32G memory set, in every possible place - from what I can see. ``` LIVE [root@prod-cluster-01:~] # virsh -c qemu:///system?authfile=/etc/ovirt-hosted-engine/virsh_auth.conf dumpxml prod-box-11|grep -i mem <ovirt-vm:memGuaranteedSize type="int">32768</ovirt-vm:memGuaranteedSize> <ovirt-vm:minGuaranteedMemoryMb type="int">32768</ovirt-vm:minGuaranteedMemoryMb> <memory unit='KiB'>33554432</memory> <currentMemory unit='KiB'>33554432</currentMemory> <cell id='0' cpus='0-27' memory='33554432' unit='KiB'/> <suspend-to-mem enabled='no'/> <model type='qxl' ram='65536' vram='32768' vgamem='16384' heads='1' primary='yes'/> <memballoon model='virtio'> </memballoon> ``` prod-box-11 is however set as high performance VM. That could cause a problem. Same for the other VM: ``` LIVE [root@prod-cluster-01:~] # virsh -c qemu:///system?authfile=/etc/ovirt-hosted-engine/virsh_auth.conf dumpxml prod-box-18|grep -i mem <ovirt-vm:memGuaranteedSize type="int">32768</ovirt-vm:memGuaranteedSize> <ovirt-vm:minGuaranteedMemoryMb type="int">32768</ovirt-vm:minGuaranteedMemoryMb> <memory unit='KiB'>33554432</memory> <currentMemory unit='KiB'>33554432</currentMemory> <cell id='0' cpus='0-27' memory='33554432' unit='KiB'/> <suspend-to-mem enabled='no'/> <model type='qxl' ram='65536' vram='32768' vgamem='16384' heads='1' primary='yes'/> <memballoon model='virtio'> </memballoon> ``` So I understand that two VMs each having allocated 32G of ram should consume approx 64G of ram on the host. The host has 128G of ram, so usage should be at approx 50%. However ovirt is reporting 94% usage. Versions: ``` engine: 4.3.5.5-1.el7 host: OS Version: RHEL - 7 - 6.1810.2.el7.centos OS Description: CentOS Linux 7 (Core) Kernel Version: 3.10.0 - 957.10.1.el7.x86_64 KVM Version: 2.12.0 - 18.el7_6.3.1 LIBVIRT Version: libvirt-4.5.0-10.el7_6.6 VDSM Version: vdsm-4.30.11-1.el7 SPICE Version: 0.14.0 - 6.el7_6.1 GlusterFS Version: [N/A] CEPH Version: librbd1-10.2.5-4.el7 Open vSwitch Version: openvswitch-2.10.1-3.el7 Kernel Features: PTI: 1, IBRS: 0, RETP: 1 VNC Encryption: Disabled ``` Thanks for any insights! -- Divan Santana https://divansantana.com

5 7

Spacewalk integration
by eevans＠digitaldatatechs.com 03 Feb '20

03 Feb '20

I know in the past that Spacewalk integration was not possible. Has anyone successfully integrated Spacewalk? It is possible or is it something that's not being put together. I use Spacewalk 2.9 and would like to integrate if it's possible and feasible. Thanks Eric Evans Digital Data Services

3 3

Two host cluster without hyperconverged
by Göker Dalar 02 Feb '20

02 Feb '20

Hello everyone, I want to get an idea in this topic. I have two servers with the same capabilities and 8 same physical disc per node. I want to setup a cluster using a redundant disc.I dont have another server for gluster hyperconverged . How i should build for this structure ? Thanks in advance, Göker

2 1

Can't connect vdsm storage: Command StorageDomain.getInfo with args failed: (code=350, message=Error in storage domain action
by asm＠pioner.kz 02 Feb '20

02 Feb '20

Hi! I trying to upgrade my hosts and have problem with it. After uprgading one host i see that this one NonOperational. All was fine with vdsm-4.30.24-1.el7 but after upgrading with new version vdsm-4.30.40-1.el7.x86_64 and some others i have errors. Firtst of all i see in ovirt Events: Host srv02 cannot access the Storage Domain(s) <UNKNOWN> attached to the Data Center Default. Setting Host state to Non-Operational. My Default storage domain with HE VM data on NFS storage. In messages log of host: srv02 journal: ovirt-ha-agent ovirt_hosted_engine_ha.agent.agent.Agent ERROR Traceback (most recent call last):#012 File "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/agent/a gent.py", line 131, in _run_agent#012 return action(he)#012 File "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/agent/agent.py", line 55, in action_proper#012 return he.start_monitoring ()#012 File "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/agent/hosted_engine.py", line 432, in start_monitoring#012 self._initialize_broker()#012 File "/usr/lib/python2.7/site-packages/ ovirt_hosted_engine_ha/agent/hosted_engine.py", line 556, in _initialize_broker#012 m.get('options', {}))#012 File "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/lib/brokerlink.py", line 8 9, in start_monitor#012 ).format(t=type, o=options, e=e)#012RequestError: brokerlink - failed to start monitor via ovirt-ha-broker: [Errno 2] No such file or directory, [monitor: 'network', options: {'tcp_t_address': None, 'network_test': None, 'tcp_t_port': None, 'addr': '192.168.2.248'}] Feb 1 15:41:42 srv02 journal: ovirt-ha-agent ovirt_hosted_engine_ha.agent.agent.Agent ERROR Trying to restart agent In broker log: MainThread::WARNING::2020-02-01 15:43:35,167::storage_broker::97::ovirt_hosted_engine_ha.broker.storage_broker.StorageBroker::(__init__) Can't connect vdsm storage: Command StorageDomain.getInfo with ar gs {'storagedomainID': 'bbdddea7-9cd6-41e7-ace5-fb9a6795caa8'} failed: (code=350, message=Error in storage domain action: (u'sdUUID=bbdddea7-9cd6-41e7-ace5-fb9a6795caa8',)) In vdsm.lod 2020-02-01 15:44:19,930+0600 INFO (jsonrpc/0) [vdsm.api] FINISH getStorageDomainInfo error=[Errno 1] Operation not permitted from=::1,57528, task_id=40683f67-d7b0-4105-aab8-6338deb54b00 (api:52) 2020-02-01 15:44:19,930+0600 ERROR (jsonrpc/0) [storage.TaskManager.Task] (Task='40683f67-d7b0-4105-aab8-6338deb54b00') Unexpected error (task:875) Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/vdsm/storage/task.py", line 882, in _run return fn(*args, **kargs) File "<string>", line 2, in getStorageDomainInfo File "/usr/lib/python2.7/site-packages/vdsm/common/api.py", line 50, in method ret = func(*args, **kwargs) File "/usr/lib/python2.7/site-packages/vdsm/storage/hsm.py", line 2753, in getStorageDomainInfo dom = self.validateSdUUID(sdUUID) File "/usr/lib/python2.7/site-packages/vdsm/storage/hsm.py", line 305, in validateSdUUID sdDom = sdCache.produce(sdUUID=sdUUID) File "/usr/lib/python2.7/site-packages/vdsm/storage/sdc.py", line 110, in produce domain.getRealDomain() File "/usr/lib/python2.7/site-packages/vdsm/storage/sdc.py", line 51, in getRealDomain return self._cache._realProduce(self._sdUUID) File "/usr/lib/python2.7/site-packages/vdsm/storage/sdc.py", line 134, in _realProduce domain = self._findDomain(sdUUID) File "/usr/lib/python2.7/site-packages/vdsm/storage/sdc.py", line 151, in _findDomain return findMethod(sdUUID) File "/usr/lib/python2.7/site-packages/vdsm/storage/nfsSD.py", line 145, in findDomain return NfsStorageDomain(NfsStorageDomain.findDomainPath(sdUUID)) File "/usr/lib/python2.7/site-packages/vdsm/storage/fileSD.py", line 378, in __init__ manifest.sdUUID, manifest.mountpoint) File "/usr/lib/python2.7/site-packages/vdsm/storage/fileSD.py", line 853, in _detect_block_size block_size = iop.probe_block_size(mountpoint) File "/usr/lib/python2.7/site-packages/vdsm/storage/outOfProcess.py", line 384, in probe_block_size return self._ioproc.probe_block_size(dir_path) File "/usr/lib/python2.7/site-packages/ioprocess/__init__.py", line 602, in probe_block_size "probe_block_size", {"dir": dir_path}, self.timeout) File "/usr/lib/python2.7/site-packages/ioprocess/__init__.py", line 448, in _sendCommand raise OSError(errcode, errstr) OSError: [Errno 1] Operation not permitted 2020-02-01 15:44:19,930+0600 INFO (jsonrpc/0) [storage.TaskManager.Task] (Task='40683f67-d7b0-4105-aab8-6338deb54b00') aborting: Task is aborted: u'[Errno 1] Operation not permitted' - code 100 (task:1 181) 2020-02-01 15:44:19,930+0600 ERROR (jsonrpc/0) [storage.Dispatcher] FINISH getStorageDomainInfo error=[Errno 1] Operation not permitted (dispatcher:87) But i see that this domain is mounted (by mount command): storage:/volume3/ovirt-hosted on /rhev/data-center/mnt/storage:_volume3_ovirt-hosted type nfs4 (rw,relatime,vers=4.1,rsize=131072,wsize=131072,namlen=255,soft,nosharecache,proto=tcp,timeo=600,retrans=6,sec=sys,clientaddr=192.168.2.251,local_lock=none,addr=192.168.2.248) I didnt see storage directory in /var/run/vdsm? I see many differences with another hosts. Here is listing of var/run/vdsm: bonding-defaults.json dhclientmon nets_restored payload svdsm.sock v2v vhostuser bonding-name2numeric.json mom-vdsm.sock ovirt-imageio-daemon.sock supervdsmd.lock trackedInterfaces vdsmd.lock What whe problem? Please help.

5 8

Re: Can't connect vdsm storage: Command StorageDomain.getInfo with args failed: (code=350, message=Error in storage domain action
by Alexandr Mikhailov 02 Feb '20

02 Feb '20

Yes. The problem with permission. But not with permissoin on export directory. Two ways to resolve this: 1) Make 777 permission on directory - dont right solution. 2) anonuid=36,anongid=36 in export - this right solution, very strange that this is not in any documentation, but very important! I has right permission on my export directory, but this is not working before i mke 777 chmod. After i chande parameters in exports file i return chmod to 755 and all working fine now! Thank you and all very much.

1 0

Re: Can't connect vdsm storage: Command StorageDomain.getInfo with args failed: (code=350, message=Error in storage domain action
by asm＠pioner.kz 02 Feb '20

02 Feb '20

First of all i have check permission on my storage. And all permission is right: group kvm (36) and user vdsm (36), chown 36:36 and chmod 0755. After i made 0777 permissions and updating all working fine! My NFS storage on Synology NAS, i now i trying to find a way to make anonuid=36,anongid=36 in the export by right way, not by editing of exports file. After i find it, i will try to use it and 755 permission. Thanks to ALL! BR, Alex

1 0

Device /dev/sdb excluded by a filter.\n
by Steve Watkins 01 Feb '20

01 Feb '20

Since I managed to crash my last attempt at installing by uploading an ISO, I wound up just reloading all the nodes and starting from scratch. Now one node gets "Device /dev/sdb excluded by a filter.\n" and fails when creating the volumes. Can't seem to get passed that -- the other machiens are set up identally and don't fail, and it worked before when installed but now... Any ideas?

2 2

oVirt upgrade problems...
by matteo fedeli 01 Feb '20

01 Feb '20

Hi at all, I have many problems after upgrade ovirt version. I come from 4.3.5.2. When I upgraded to 4.3.7 my three host (hyperconverged emviroment) I passed a few days of instability: HA agent down gluster problem... When I rebooted for the umpteenth time (after reinitialized lockspace, heal, heal full...) all cames up ha agent and broker included. Two days after arrived 4.3.8, so i decided to start the update, america with success, europa after a various problems (as described before) came up. Asia host, after 30 second of updating the engine goes down together with all three nodes ... Are there any known important bugs? This is the state of my nodes: https://pastebin.com/2XsnTyHi https://pastebin.com/ZeKTdaZ7 https://pastebin.com/ZDUBg4vG

2 2

Gluster Heal Issue
by Christian Reiss 01 Feb '20

01 Feb '20

Hey folks, in our production setup with 3 nodes (HCI) we took one host down (maintenance, stop gluster, poweroff via ssh/ovirt engine). Once it was up the gluster hat 2k healing entries that went down in a matter on 10 minutes to 2. Those two give me a headache: [root@node03:~] # gluster vol heal ssd_storage info Brick node01:/gluster_bricks/ssd_storage/ssd_storage <gfid:a121e4fb-0984-4e41-94d7-8f0c4f87f4b6> <gfid:6f8817dc-3d92-46bf-aa65-a5d23f97490e> Status: Connected Number of entries: 2 Brick node02:/gluster_bricks/ssd_storage/ssd_storage Status: Connected Number of entries: 0 Brick node03:/gluster_bricks/ssd_storage/ssd_storage <gfid:a121e4fb-0984-4e41-94d7-8f0c4f87f4b6> <gfid:6f8817dc-3d92-46bf-aa65-a5d23f97490e> Status: Connected Number of entries: 2 No paths, only gfid. We took down node2, so it does not have the file: [root@node01:~] # md5sum /gluster_bricks/ssd_storage/ssd_storage/.glusterfs/a1/21/a121e4fb-0984-4e41-94d7-8f0c4f87f4b6 75c4941683b7eabc223fc9d5f022a77c /gluster_bricks/ssd_storage/ssd_storage/.glusterfs/a1/21/a121e4fb-0984-4e41-94d7-8f0c4f87f4b6 [root@node02:~] # md5sum /gluster_bricks/ssd_storage/ssd_storage/.glusterfs/a1/21/a121e4fb-0984-4e41-94d7-8f0c4f87f4b6 md5sum: /gluster_bricks/ssd_storage/ssd_storage/.glusterfs/a1/21/a121e4fb-0984-4e41-94d7-8f0c4f87f4b6: No such file or directory [root@node03:~] # md5sum /gluster_bricks/ssd_storage/ssd_storage/.glusterfs/a1/21/a121e4fb-0984-4e41-94d7-8f0c4f87f4b6 75c4941683b7eabc223fc9d5f022a77c /gluster_bricks/ssd_storage/ssd_storage/.glusterfs/a1/21/a121e4fb-0984-4e41-94d7-8f0c4f87f4b6 The other two files are md5-identical. These flags are identical, too: [root@node01:~] # getfattr -d -m . -e hex /gluster_bricks/ssd_storage/ssd_storage/.glusterfs/a1/21/a121e4fb-0984-4e41-94d7-8f0c4f87f4b6 getfattr: Removing leading '/' from absolute path names # file: gluster_bricks/ssd_storage/ssd_storage/.glusterfs/a1/21/a121e4fb-0984-4e41-94d7-8f0c4f87f4b6 security.selinux=0x73797374656d5f753a6f626a6563745f723a676c7573746572645f627269636b5f743a733000 trusted.afr.dirty=0x000000000000000000000000 trusted.afr.ssd_storage-client-1=0x0000004f0000000100000000 trusted.gfid=0xa121e4fb09844e4194d78f0c4f87f4b6 trusted.gfid2path.d4cf876a215b173f=0x62653331383633382d653861302d346336642d393737642d3761393337616138343830362f38366461303238392d663734662d343230302d393238342d3637386537626437363139352e31323030 trusted.glusterfs.mdata=0x010000000000000000000000005e349b1e000000001139aa2a000000005e349b1e000000001139aa2a000000005e34994900000000304a5eb2 getfattr: Removing leading '/' from absolute path names # file: gluster_bricks/ssd_storage/ssd_storage/.glusterfs/a1/21/a121e4fb-0984-4e41-94d7-8f0c4f87f4b6 security.selinux=0x73797374656d5f753a6f626a6563745f723a676c7573746572645f627269636b5f743a733000 trusted.afr.dirty=0x000000000000000000000000 trusted.afr.ssd_storage-client-1=0x0000004f0000000100000000 trusted.gfid=0xa121e4fb09844e4194d78f0c4f87f4b6 trusted.gfid2path.d4cf876a215b173f=0x62653331383633382d653861302d346336642d393737642d3761393337616138343830362f38366461303238392d663734662d343230302d393238342d3637386537626437363139352e31323030 trusted.glusterfs.mdata=0x010000000000000000000000005e349b1e000000001139aa2a000000005e349b1e000000001139aa2a000000005e34994900000000304a5eb2 Now, I dont dare simply proceeding withouth some advice. Anyone got a clue on who to resolve this issue? File #2 is identical to this one, from a problem point of view. Have a great weekend! -Chris. -- with kind regards, mit freundlichen Gruessen, Christian Reiss

4 6

Ovirt-engine-ha cannot to see live status of Hosted Engine
by asm＠pioner.kz 01 Feb '20

01 Feb '20

Good day for all. I have some issues with Ovirt 4.2.6. But now the main this of it: I have two Centos 7 Nodes with same config and last Ovirt 4.2.6 with Hostedengine with disk on NFS storage. Also some of virtual machines working good. But, when HostedEngine running on one node (srv02.local) everything is fine. After migrating to another node (srv00.local), i see that agent cannot to check livelinness of HostedEngine. After few minutes HostedEngine going to reboot and after some time i see some situation. After migration to another node (srv00.local) all looks OK. hosted-engine --vm-status commang when HosterEngine on srv00 node: --== Host 1 status ==-- conf_on_shared_storage : True Status up-to-date : True Hostname : srv02.local Host ID : 1 Engine status : {"reason": "vm not running on this host", "health": "bad", "vm": "down_unexpected", "detail": "unknown"} Score : 0 stopped : False Local maintenance : False crc32 : ecc7ad2d local_conf_timestamp : 78328 Host timestamp : 78328 Extra metadata (valid at timestamp): metadata_parse_version=1 metadata_feature_version=1 timestamp=78328 (Tue Sep 18 12:44:18 2018) host-id=1 score=0 vm_conf_refresh_time=78328 (Tue Sep 18 12:44:18 2018) conf_on_shared_storage=True maintenance=False state=EngineUnexpectedlyDown stopped=False timeout=Fri Jan 2 03:49:58 1970 --== Host 2 status ==-- conf_on_shared_storage : True Status up-to-date : True Hostname : srv00.local Host ID : 2 Engine status : {"reason": "failed liveliness check", "health": "bad", "vm": "up", "detail": "Up"} Score : 3400 stopped : False Local maintenance : False crc32 : 1d62b106 local_conf_timestamp : 326288 Host timestamp : 326288 Extra metadata (valid at timestamp): metadata_parse_version=1 metadata_feature_version=1 timestamp=326288 (Tue Sep 18 12:44:21 2018) host-id=2 score=3400 vm_conf_refresh_time=326288 (Tue Sep 18 12:44:21 2018) conf_on_shared_storage=True maintenance=False state=EngineStarting stopped=False Log agent.log from srv00.local: MainThread::INFO::2018-09-18 12:40:51,749::states::779::ovirt_hosted_engine_ha.agent.hosted_engine.HostedE ngine::(consume) VM is powering up.. MainThread::INFO::2018-09-18 12:40:52,052::hosted_engine::491::ovirt_hosted_engine_ha.agent.hosted_engine. HostedEngine::(_monitoring_loop) Current state EngineStarting (score: 3400) MainThread::INFO::2018-09-18 12:41:01,066::states::779::ovirt_hosted_engine_ha.agent.hosted_engine.HostedE ngine::(consume) VM is powering up.. MainThread::INFO::2018-09-18 12:41:01,374::hosted_engine::491::ovirt_hosted_engine_ha.agent.hosted_engine. HostedEngine::(_monitoring_loop) Current state EngineStarting (score: 3400) MainThread::INFO::2018-09-18 12:41:11,393::state_machine::169::ovirt_hosted_engine_ha.agent.hosted_engine. HostedEngine::(refresh) Global metadata: {'maintenance': False} MainThread::INFO::2018-09-18 12:41:11,393::state_machine::174::ovirt_hosted_engine_ha.agent.hosted_engine. HostedEngine::(refresh) Host srv02.local.pioner.kz (id 1): {'conf_on_shared_storage': True, 'extra': 'meta data_parse_version=1\nmetadata_feature_version=1\ntimestamp=78128 (Tue Sep 18 12:40:58 2018)\nhost-id=1\ns core=0\nvm_conf_refresh_time=78128 (Tue Sep 18 12:40:58 2018)\nconf_on_shared_storage=True\nmaintenance=Fa lse\nstate=EngineUnexpectedlyDown\nstopped=False\ntimeout=Fri Jan 2 03:49:58 1970\n', 'hostname': 'srv02. local.pioner.kz', 'alive': True, 'host-id': 1, 'engine-status': {'reason': 'vm not running on this host', 'health': 'bad', 'vm': 'down_unexpected', 'detail': 'unknown'}, 'score': 0, 'stopped': False, 'maintenance ': False, 'crc32': 'e18e3f22', 'local_conf_timestamp': 78128, 'host-ts': 78128} MainThread::INFO::2018-09-18 12:41:11,393::state_machine::177::ovirt_hosted_engine_ha.agent.hosted_engine. HostedEngine::(refresh) Local (id 2): {'engine-health': {'reason': 'failed liveliness check', 'health': 'b ad', 'vm': 'up', 'detail': 'Up'}, 'bridge': True, 'mem-free': 12763.0, 'maintenance': False, 'cpu-load': 0 .0364, 'gateway': 1.0, 'storage-domain': True} MainThread::INFO::2018-09-18 12:41:11,393::states::779::ovirt_hosted_engine_ha.agent.hosted_engine.HostedE ngine::(consume) VM is powering up.. MainThread::INFO::2018-09-18 12:41:11,703::hosted_engine::491::ovirt_hosted_engine_ha.agent.hosted_engine. HostedEngine::(_monitoring_loop) Current state EngineStarting (score: 3400) MainThread::INFO::2018-09-18 12:41:21,716::states::779::ovirt_hosted_engine_ha.agent.hosted_engine.HostedE ngine::(consume) VM is powering up.. MainThread::INFO::2018-09-18 12:41:22,020::hosted_engine::491::ovirt_hosted_engine_ha.agent.hosted_engine. HostedEngine::(_monitoring_loop) Current state EngineStarting (score: 3400) MainThread::INFO::2018-09-18 12:41:31,033::states::779::ovirt_hosted_engine_ha.agent.hosted_engine.HostedE ngine::(consume) VM is powering up.. MainThread::INFO::2018-09-18 12:41:31,344::hosted_engine::491::ovirt_hosted_engine_ha.agent.hosted_engine. HostedEngine::(_monitoring_loop) Current state EngineStarting (score: 3400) As we can see, agent thinking that HostedEngine just in powering up mode. I cannot to do anythink with it. I allready reinstalled many times srv00 node without success. One time i even has to uninstall ovirt* and vdsm* software. Also here one interesting point, after installing just "yum install http://resources.ovirt.org/pub/yum-repo/ovirt-release42.rpm" on this node i try to install this node from engine web interface with "Deploy" action. But, installation was unsuccesfull, before i didnt install ovirt-hosted-engine-ha on this node. I dont see in documentation that its need bofore installation of new hosts. But this is for information and checking. After installing ovirt-hosted-engine-ha node was installed with HostedEngine support. But the main issue not changed. Thanks in advance for help. BR, Alexandr

3 5

Reimport VMs after lost Engine with broken Backup
by Vinícius Ferrão 31 Jan '20

31 Jan '20

Hello, I’m with a scenario with a lost hosted-engine. For reasons unknown the backup is broken and I’ve tried everything: redeploy with backup file, deploy a new one and them restore the backup. Changed the HE storage domain in both cases just be sure. Reinstalled one of the hosts just to be safe but nothing worked. So I just deployed a brand new engine and now I want to import back the VM’s. My scenario right now is: ovirt1 brand new with the new VM in a new storage domain. ovirt2 have production VMs running without any issue. So my questions right now: * What happens if I just add the ovirt2 machine to the new engine? It will reboot or will add everything back: storage, networks etc? My plan right now would be: * Reconfigure the DC and the cluster. * Readd all the networks. * Reattach the storage domains. * Recreate all the VM”s attaching it’s disks. Is there’s something that I can do better to mitigate the work? Thanks,

1 2

Re: High level network advice request
by Richard Nilsson 31 Jan '20

31 Jan '20

Thanks so much for your reply Robert! I like your set-up alot, that's where I'm going too actually. But now I have only one node, I'm trying to learn very basic setup with just the one for the moment (Because I have it running after years of trying! It will take a few weeks and another motherboard / rebuild before I have the second node, I'll get there soon). I've just learned (I think) that I can't sync new logical networks with the host, because I can't put the only host in maintenance mode...I thought that there might be a way with cli and restarts and all that but lo, there no point, I will have another node in a few weeks or months :) That's okay, I'm trying to work out why I can't access my new test server from WAN. I use split dns with pfsense and haproxy reverse redirects. I can get to the server test pages from LAN via the pfSense dns resolution (LAN) but the reverse redirects are not working from WAN. I don't know what next step to take to debug the problem. The engine is accessible from WAN, so I think it should work for the vm server, which is also on the default ovirt management network and uses all defaults like the hosted engine. I suspect that there is a security setting on the engine, logical network or maybe the server? What should I check next? My singe node, is also in the same condition, which may be instructive to a noob like me...the node I can reach from the LAN but not the WAN. So the engine is a special case. Do I need to create certificates on the vm webserver? I'd like to see if I can set-up a NextCloud server after trying a SuiteCRM server. But I started with fedora 31 server and a very basic lamp stack to limit variables... Thanks in advance. Let me know if I can ever help you with anything! I'm an Architect, but a real one; not IT but bricks and all that :) These are the links: engine.metrodesignoffice.com mdowebserver.metrodesignoffice.com

2 1

0virt VMs status down after host reboot
by Eugène Ngontang 31 Jan '20

31 Jan '20

Hi all, I've set up an infrastructure with OVirt, using self-hosted engine. I use some ansible scripts from my Virtualization Host (the physical machine), to bootstrap the hosted engine, and create a set of virtual machines on which I deploy a k8s cluster. The deployment goes well, and everything is OK. Now I'm doing some reboot tests, and when I reboot the physical server, only the hosted-engine vm is up after the reboot, the rest of VMs and thus the k8s cluster are down. Had someone here ever experienced this issue? What can cause it and how to automate the virtual machines startup in RHVE/Ovirt? Thanks. Regards, Eugene -- LesCDN <http://lescdn.com> engontang(a)lescdn.com ------------------------------------------------------------ *Aux hommes il faut un chef, et au* * chef il faut des hommes!L'habit ne fait pas le moine, mais lorsqu'on te voit on te juge!*

4 6

Update 4.4
by Dirk Streubel 31 Jan '20

31 Jan '20

Hello, i use for testing Version 4.4 and i wanted to make a update. This is the result: LANG=C engine-setup ... [ INFO ] Checking for product updates... [ ERROR ] Yum [u'ovirt-engine-backend-4.4.0-0.0.master.20200122090542.git5f0a359.el7.noarch requires java-client-kubevirt >= 0.1.0'] [ INFO ] Yum Performing yum transaction rollback [ ERROR ] Failed to execute stage 'Environment customization': [u'ovirt-engine-backend-4.4.0-0.0.master.20200122090542.git5f0a359.el7.noarch requires java-client-kubevirt >= 0.1.0'] [ INFO ] Stage: Clean up Log file is located at /var/log/ovirt-engine/setup/ovirt-engine-setup-20200127193352-x6p04t.log [ INFO ] Generating answer file '/var/lib/ovirt-engine/setup/answers/20200127193405-setup.conf' [ ERROR ] Failed to execute stage 'Clean up': must be unicode, not str [ INFO ] Stage: Pre-termination [ INFO ] Stage: Termination [ ERROR ] Execution of setup failed So, i found this: https://repo1.maven.org/maven2/org/ovirt/java-client-kubevirt/java-client-k… So, do i have to install a.jar to make the engine update or what is the best way to do the update? Dirk

2 1

High level network advice request
by Richard Nilsson 31 Jan '20

31 Jan '20

High level network advice request :) I have a self-hosted engine deployed on a node, Ovirt v. 4.3. I am testing, but I don't understand the big idea of how to set-up Ovirt networking for hosted / engine-managed virtual servers. I would like to host a few virtual servers for things like Next/OwnCloud, SuiteCRM, NethServer or others. For example, I know exactly how set-up a virtual machine with a centos / lamp stack on a fedora host, I can make a network bridge for the vm with fedora cli, then use haproxy (or squid) as a reverse-redirect server to allow WAN access to the vm server using FQDNs. What is a good strategy for Ovirt hosting a webserver? To use the default ovirt management network for the virtual server machines doesn't seem like a best practice? Should I make a new logical network for the virtual servers? Do I need to configure bridges for the machines? It looks like bridges and virtual NICs are automatically configured when I make the network and virtual machines, is that right? Is it the usual or typical practice that one ovirt logical network uses only one network bridge to a one physical NIC? Would all of the kVMs on the logical network share the same / single bridge of the particular network? I'm not sure what the big idea should be, what is a best practice? I wonder, should I bond several physical NICs, then point the bridge, for a new / dedicated logical network for webservers, to the the bonded NICs? There is more than a little new vocabulary for me to onboard for Ovirt / virtual / logical networks...I will greatly appreciate, and I thank you in advance for any top level / best practice advice!

3 4

Remembering Lars Kurth at FOSDEM
by Tal Nisan 31 Jan '20

31 Jan '20

The Virtualization community that is gathering at FOSDEM would like to share its plans to remember the life and accomplishments of our valued friend and colleague, Lars Kurth, who has recently passed away. The remembrance will be at 09:45 Sunday Feb. 2 in the Virtualization Devroom (H.1309). We invite all to attend who would like to share in their memories of Lars and celebrate his life.

1 0

Assign permissions from within the VM portal?
by nicolas＠devels.es 31 Jan '20

31 Jan '20

Hi, We're testing version 4.3.8, we're planning to upgrade to this version in production as currently we're still using 4.1.9. In 4.1.9, users could grant permissions on their created VMs to other users from within the VM portal, however I can't find this option on version 4.3.8. Permissions granted to users so they can create and handle their VMs are VmCreator and DiskProfileUser on the DataCenter. Is there a way to allow users grant permissions on their VMs to other users in the VM portal? Thanks

1 0

FOSDEM 2020 - AMENDMENT In Memory of our Friend, Lars Kurth
by Doron Fediuck 31 Jan '20

31 Jan '20

Hi all, For those of you who are unaware of this, Lars Kurth from the Xen project has passed away [1]. Lars was one of the people who truly practiced open source and worked with the oVirt project on running FOSDEM's Virtualization and IaaS room in the past years. In Lars' memory there will be a special session [2] on Sunday morning, which will be broadcasted live. You're all welcomed to join physically or via the live stream. Thanks, Doron [1] https://lists.xenproject.org/archives/html/xen-announce/2020-01/msg00004.ht… [2] https://fosdem.org/2020/schedule/event/vai_memory_of_lars_kurth/

1 0

problem with qemu / dynamic_ownership
by Christoph Köhler 31 Jan '20

31 Jan '20

Hey, is the problem back with qemu/dynamic_ownership? We have one DC with two clusters: one: vdsm-4.30.38 / libvirt-4.5.0-23, two: vdsm-4.30.40 / libvirt-4.5.0-23, LibgfApi enabled, Gluster-Server 6.5.1, Gluster-Client 6.7, opVersion 60000 It went well for a log time but now, with getting vdsm like above, we are getting old problems: °setting disk files to root:root when VM went down °cannot create snapshot etc. Do we have to set dynamic_ownership=0 in qemu.conf? We were testing anything but nothing other worked. Is there any idea? Christoph

1 0

Re: [ANN] oVirt 4.3.7 Third Release Candidate is now available for testing
by Strahil 31 Jan '20

31 Jan '20

I got upgraded to RC3 and now cannot power any VM . Constantly getting I/O error, but checking at gluster level - I can dd from each disk or even create a new one. Removing the HighAvailability doesn't help. I guess I should restore the engine from the gluster snapshot and rollback via 'yum history undo last'. Does anyone else have my issues ? Best Regards, Strahil NikolovOn Nov 13, 2019 15:31, Sandro Bonazzola <sbonazzo(a)redhat.com> wrote: > > > > Il giorno mer 13 nov 2019 alle ore 14:25 Sandro Bonazzola <sbonazzo(a)redhat.com> ha scritto: >> >> >> >> Il giorno mer 13 nov 2019 alle ore 13:56 Florian Schmid <fschmid(a)ubimet.com> ha scritto: >>> >>> Hello, >>> >>> I have a question about bugs, which are flagged as [downstream clone - 4.3.7], but are not yet released. >>> >>> I'm talking about this bug: >>> https://bugzilla.redhat.com/show_bug.cgi?id=1749202 >>> >>> I can't see it in 4.3.7 release notes. Will it be included in a further release candidate? This fix is very important I think and I can't upgrade yet because of this bug. >> >> >> >> Looking at the bug, the fix was done with $ git tag --contains 12bd5cb1fe7c95e29b4065fca968913722fe9eaa >> ovirt-engine-4.3.6.6 >> ovirt-engine-4.3.6.7 >> ovirt-engine-4.3.7.0 >> ovirt-engine-4.3.7.1 >> >> So the fix is already included in release oVirt 4.3.6. > > > Sent a fix to 4.3.6 release notes: https://github.com/oVirt/ovirt-site/pull/2143. @Ryan Barry can you please review? > > >> >> >> >> >> >> >>> >>> >>> BR Florian Schmid >>> >>> ________________________________ >>> Von: "Sandro Bonazzola" <sbonazzo(a)redhat.com> >>> An: "users" <users(a)ovirt.org> >>> Gesendet: Mittwoch, 13. November 2019 13:34:59 >>> Betreff: [ovirt-users] [ANN] oVirt 4.3.7 Third Release Candidate is now available for testing >>> >>> The oVirt Project is pleased to announce the availability of the oVirt 4.3.7 Third Release Candidate for testing, as of November 13th, 2019. >>> >>> This update is a release candidate of the seventh in a series of stabilization updates to the 4.3 series. >>> This is pre-release software. This pre-release should not to be used in production. >>> >>> This release is available now on x86_64 architecture for: >>> * Red Hat Enterprise Linux 7.7 or later (but <8) >>> * CentOS Linux (or similar) 7.7 or later (but <8) >>> >>> This release supports Hypervisor Hosts on x86_64 and ppc64le architectures for: >>> * Red Hat Enterprise Linux 7.7 or later (but <8) >>> * CentOS Linux (or similar) 7.7 or later (but <8) >>> * oVirt Node 4.3 (available for x86_64 only) has been built consuming CentOS 7.7 Release >>> >>> See the release notes [1] for known issues, new features and bugs fixed. >>> >>> While testing this release candidate please note that oVirt node now includes: >>> - ansible 2.9.0 >>> - GlusterFS 6.6 >>> >>> Notes: >>> - oVirt Appliance is already available >>> - oVirt Node is already available >>> >>> Additional Resources: >>> * Read more about the oVirt 4.3.7 release highlights: http://www.ovirt.org/release/4.3.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.3.7/ >>> [2] http://resources.ovirt.org/pub/ovirt-4.3-pre/iso/ >>> >>> -- >>> >>> Sandro Bonazzola >>> >>> MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV >>> >>> Red Hat EMEA >>> >>> sbonazzo(a)redhat.com >>> >>> Red Hat respects your work life balance. Therefore there is no need to answer this email out of your office hours. >>> >>> _______________________________________________ >>> 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/24QUREJPZHTSM… >> >> >> >> -- >> >> Sandro Bonazzola >> >> MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV >> >> Red Hat EMEA >> >> sbonazzo(a)redhat.com >> >> Red Hat respects your work life balance. Therefore there is no need to answer this email out of your office hours. > > > > -- > > Sandro Bonazzola > > MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV > > Red Hat EMEA > > sbonazzo(a)redhat.com > > Red Hat respects your work life balance. Therefore there is no need to answer this email out of your office hours.

7 20

Re: Problems in new oVirt install
by Steve Watkins 30 Jan '20

30 Jan '20

> Yes that's what usually happens the VM will be paused when the backing storage starts > running out of space, try deleting the ISO from where you uploaded it to. > > Regards, > > Paul S. > > ________________________________ > From: Steve Watkins <watkinssr(a)gmail.com> > Sent: 29 January 2020 00:13 > To: users(a)ovirt.org <users(a)ovirt.org> > Subject: [ovirt-users] Problems in new oVirt install > > Caution External Mail: Do not click any links or open any attachments unless you trust the > sender and know that the content is safe. > > Got everything installed and was uploding an ISO when the system just stopped responding. > Went to the host and saw the hostedengine was paused. Looked online and found the > following instructions for unpausing it > > virsh -c qemu:///system?authfile=/etc/ovirt-hosted-engine/virsh_auth.conf > resume HostedEngine > > And get the following error > Failed to acquire lock: No space left on device > > any ideas? > _______________________________________________ > Users mailing list -- users(a)ovirt.org > To unsubscribe send an email to users-leave(a)ovirt.org > Privacy Statement: > https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ovi... > oVirt Code of Conduct: > https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ovi... > List Archives: > https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.o... > To view the terms under which this email is distributed, please go to:- > http://leedsbeckett.ac.uk/disclaimer/email/ Since the hostedengine won't start, I don't see any way to delete it.

2 2

[ANN] oVirt 4.3.8 is now generally available
by Sandro Bonazzola 30 Jan '20

30 Jan '20

The oVirt Project is pleased to announce the general availability of oVirt 4.3.8 as of January 27th, 2020. This update is the eighth 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.7 or later (but < 8) * CentOS Linux (or similar) 7.7 or later (but < 8) This release supports Hypervisor Hosts on x86_64 and ppc64le architectures for: * Red Hat Enterprise Linux 7.7 or later (but < 8) * CentOS Linux (or similar) 7.7 or later (but < 8) * oVirt Node 4.3 (available for x86_64 only) 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 Node and Appliance have been updated including: - oVirt 4.3.8: http://www.ovirt.org/release/4.3.8/ - Including fixes for CVE-2019-19336 oVirt Engine Cross Site Scripting Vulnerability <https://www.symantec.com/security-center/vulnerabilities/writeup/111466> - Latest CentOS 7.7 updates including: - CEBA-2019:3970 CentOS 7 ca-certificates BugFix Update <https://lists.centos.org/pipermail/centos-announce/2019-December/035571.html> - CEBA-2019:3971 CentOS 7 curl BugFix Update <https://lists.centos.org/pipermail/centos-announce/2019-December/035558.html> - CEBA-2019:3985 CentOS 7 iproute BugFix Update <https://lists.centos.org/pipermail/centos-announce/2019-December/035568.html> - CESA-2019:3979 Important CentOS 7 kernel Security Update <https://lists.centos.org/pipermail/centos-announce/2019-December/035574.html> - CEBA-2019:4106 CentOS 7 kernel BugFix Update <https://lists.centos.org/pipermail/centos-announce/2019-December/035575.html> - CEBA-2019:3983 CentOS 7 util-linux BugFix Update <https://lists.centos.org/pipermail/centos-announce/2019-December/035567.html> - CEBA-2019:3972 CentOS 7 sssd BugFix Update <https://lists.centos.org/pipermail/centos-announce/2019-December/035565.html> - CEBA-2019:3969 CentOS 7 samba BugFix Update <https://lists.centos.org/pipermail/centos-announce/2019-December/035561.html> - CEBA-2019:3975 CentOS 7 libvirt BugFix Update <https://lists.centos.org/pipermail/centos-announce/2019-December/035562.html> - CEEA-2019:4161 CentOS 7 microcode_ctl Enhancement Update <https://lists.centos.org/pipermail/centos-announce/2019-December/035586.html> - CESA-2019:4190 Important CentOS 7 nss Security Update <https://lists.centos.org/pipermail/centos-announce/2019-December/035590.html> - CESA-2019:4190 Important CentOS 7 nss-softokn Security Update <https://lists.centos.org/pipermail/centos-announce/2019-December/035589.html> - CESA-2019:4190 Important CentOS 7 nss-util Security Update <https://lists.centos.org/pipermail/centos-announce/2019-December/035587.html> - CEBA-2019:3977 CentOS 7 numactl BugFix Update <https://lists.centos.org/pipermail/centos-announce/2019-December/035573.html> - CEBA-2019:3982 CentOS 7 selinux-policy BugFix Update <https://lists.centos.org/pipermail/centos-announce/2019-December/035559.html> - CEBA-2019:3973 CentOS 7 sos BugFix Update <https://lists.centos.org/pipermail/centos-announce/2019-December/035572.html> - CESA-2019:3976 Low CentOS 7 tcpdump Security Update <https://lists.centos.org/pipermail/centos-announce/2019-December/035570.html> - latest CentOS Virt and Storage SIG updates: - Ansible 2.9.4: https://github.com/ansible/ansible/blob/stable-2.9/changelogs/CHANGELOG-v2.… - Glusterfs 6.7: https://docs.gluster.org/en/latest/release-notes/6.7/ Given the amount of security fixes provided by this release, upgrade is recommended as soon as practical. Additional Resources: * Read more about the oVirt 4.3.8 release highlights: http://www.ovirt.org/release/4.3.8/ * 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.8/ [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/>*Red Hat respects your work life balance. Therefore there is no need to answer this email out of your office hours.*

4 5

Async release for ovirt-engine-metrics is now available for oVirt 4.3.8
by Sandro Bonazzola 30 Jan '20

30 Jan '20

The oVirt Team has just released a new version of ovirt-engine-metrics package that fixes the deployment of the metrics solution when using foreman/satellite. The deployment was previously failing on missing rhsub_orgid in vars.yaml.template. We recommend to update ovirt-engine-metrics if you're planning to use it with foreman/satellite. Thanks, -- 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.*

1 0

Virtual disk attached to VM showing in the Webui but not identified by the system
by Eugène Ngontang 30 Jan '20

30 Jan '20

Hi, I'm facing a virtual disk behavior I don't understand. Currently my VMs are spun up with a Boot disk of 25GB and an additional disk of 215/45/65 GB depending. When logged to the webui I see the two disks, but when I ssh to VM we only see the primary boot disk, the other one can't get a *UUID* and then cannot and is not mounted I also noticed in the webui the second disk doesn't have a logical name as you can see in the screenshot. Pleas can someone explain this behavior please? Here is my disk management commands outputs [root@fp-gpu-node3 centos]# fdisk -l > > > Disque /dev/vda : 26.8 Go, 26843545600 octets, 52428800 secteurs > > Unités = secteur de 1 × 512 = 512 octets > > Taille de secteur (logique / physique) : 512 octets / 512 octets > > taille d'E/S (minimale / optimale) : 512 octets / 512 octets > > Type d'étiquette de disque : dos > > Identifiant de disque : 0x000b6061 > > > Périphérique Amorçage Début Fin Blocs Id. Système > > /dev/vda1 * 2048 52428766 26213359+ 83 Linux > > > Disque /dev/vdb : 48.3 Go, 48318382080 octets, 94371840 secteurs > > Unités = secteur de 1 × 512 = 512 octets > > Taille de secteur (logique / physique) : 512 octets / 512 octets > > taille d'E/S (minimale / optimale) : 512 octets / 512 octets > > > [root@fp-gpu-node3 centos]# blkid > > /dev/vda1: UUID="3ef2b806-efd7-4eef-aaa2-2584909365ff" TYPE="xfs" > > [root@fp-gpu-node3 centos]# lsblk -f > > NAME FSTYPE LABEL UUID MOUNTPOINT > > sr0 > > vda > > └─vda1 xfs 3ef2b806-efd7-4eef-aaa2-2584909365ff / > > vdb > Thanks for your help. -- LesCDN <http://lescdn.com> engontang(a)lescdn.com ------------------------------------------------------------ *Aux hommes il faut un chef, et au* * chef il faut des hommes!L'habit ne fait pas le moine, mais lorsqu'on te voit on te juge!*

2 4

Re: Problems in new oVirt install
by Steve Watkins 30 Jan '20

30 Jan '20

Since the hostedengine won't start, I don't see anyway to get to it to delete it.

1 0

Details about bios and custom emulated machine values
by Gianluca Cecchi 29 Jan '20

29 Jan '20

Hello, in oVirt 4.3.7 in "Edit VM" -> System -> Advanced parameters I can choose Bios Type: Default Q35 Chipset with Legacy BIOS Q35 Chipset with UEFI BIOS Q35 Chipset with SecureBoot and Custom Emulated Machine: Use cluster default (pc-i440fx-rhel7.6.0) ... q35 pc-q35-rhel7.3.0 pc-q35-rhel7.4.0 pc-q35-rhel7.5.0 pc-q35-rhel7.6.0 and I can apparently mix all possible values. Any deeper information about implications? What is the "Default" value for Bios Type? Did anything change in 4.3.8 (eg official support for q35)? I search also through official docs for RHV 4.3 (virtual mgmt guide, appendix A), but for example I don't find any reference to the "Bios Type" parameter and a vague reference to the "Custom Emulated Machine". Is there any more detailed link? Thanks, Gianluca

2 1

Problems in new oVirt install
by Steve Watkins 29 Jan '20

29 Jan '20

Got everything installed and was uploding an ISO when the system just stopped responding. Went to the host and saw the hostedengine was paused. Looked online and found the following instructions for unpausing it virsh -c qemu:///system?authfile=/etc/ovirt-hosted-engine/virsh_auth.conf resume HostedEngine And get the following error Failed to acquire lock: No space left on device any ideas?

2 1

new install issues
by Steve Watkins 29 Jan '20

29 Jan '20

Very new to this, trying to work my way through it. Got everything up and running, was uploading an ISO to try and start a vm and then everything just disconnected. On the host it shows the hostedengine as paused. Did some digging and found the suggestion to do the following: virsh -c qemu:///system?authfile=/etc/ovirt-hosted-engine/virsh_auth.conf resume HostedEngine which gives me the message Failed to acquire lock: No space left on device. Ideas?

2 1

Cannot put host in maintenance mode
by Vinícius Ferrão 28 Jan '20

28 Jan '20

Hello, I’m with an issue on one of my oVirt installs and I wasn’t able to solve it. When trying to put a node in maintenance it complains about image transfers: Error while executing action: Cannot switch Host ovirt2 to Maintenance mode. Image transfer is in progress for the following (3) disks: 8f4c712e-66bb-4bfc-9afb-78407b8b726c, eb0ef249-284d-4d77-b1f1-ee8b70718f3d, 73245a4c-8f56-4508-a5c5-2d7697f87654 Please wait for the operations to complete and try again. I wasn’t able to find this image transfers. There’s nothing on the engine showing any transfer. How can I debug this? Thanks,

3 5

Re: Windows Server Migration from Proxmox
by Staniforth, Paul 28 Jan '20

28 Jan '20

Hello, it may be a driver problem, try changing the disk interface to IDE, if that boots install the virtio drivers and remove any Proxmox drivers, Regards, Paul S. ________________________________ From: Robert Webb <rwebb(a)ropeguru.com> Sent: 27 January 2020 20:33 To: users <users(a)ovirt.org> Subject: [ovirt-users] Windows Server Migration from Proxmox Caution External Mail: Do not click any links or open any attachments unless you trust the sender and know that the content is safe. I have several Windows systems I am trying to migrate from Proxmox. In each VM under Proxmox, I have removed all guest utilities and completed a clean shutdown. I have successfully imported the disk image into oVirt and attached to a new VM with the same specs. When I power on, though, they all give me a "kmode exception not handled". Has anyone else run into this and successfully migrated a WIndows VM? These are primarily Server 2019 systems.. _______________________________________________ Users mailing list -- users(a)ovirt.org To unsubscribe send an email to users-leave(a)ovirt.org Privacy Statement: https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ovirt… oVirt Code of Conduct: https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ovirt… List Archives: https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.ovi… To view the terms under which this email is distributed, please go to:- http://leedsbeckett.ac.uk/disclaimer/email/

1 0

Windows Server Migration from Proxmox
by Robert Webb 27 Jan '20

27 Jan '20

I have several Windows systems I am trying to migrate from Proxmox. In each VM under Proxmox, I have removed all guest utilities and completed a clean shutdown. I have successfully imported the disk image into oVirt and attached to a new VM with the same specs. When I power on, though, they all give me a "kmode exception not handled". Has anyone else run into this and successfully migrated a WIndows VM? These are primarily Server 2019 systems..

1 0

command line vm start/stop
by uran987＠gmail.com 27 Jan '20

27 Jan '20

Hello Experts. In version 3.5.2.1-1.el6, we used an "ovirt-shell -E action..." command to start/stop virtual machines from command line. In version 4.3.7.2-1.el7 ovirt-shell is deprecated. Please advise how to start/stop them from command line. vdsm-client provides only destroy/shutdown/reset/cont, nothing about startvm or poweron. Regards.

3 2

Re: [ANN] oVirt 4.3.8 is now generally available
by Sandro Bonazzola 27 Jan '20

27 Jan '20

Il giorno lun 27 gen 2020 alle ore 15:59 Robert Webb <rwebb(a)ropeguru.com> ha scritto: > Have the repositories been updated yet? > > Running oVIrt Node 4.3.7 with hosted engine in a cluster. > > Was able to successfully update the engine, bit when following the online > upgrade instructions, running "Installation --> Check" on the host does not > come back with any updates. Manually running an update check with 'yum > update" yields the same result. > > > Link used for updating instructions: > https://www.ovirt.org/documentation/upgrade-guide/chap-Updates_between_Mino… mirrors are still syncing, maybe you just hit a mirror which wasn't updated yet. Can you "yum clean metadata" and retry? > > > ________________________________________ > From: Sandro Bonazzola <sbonazzo(a)redhat.com> > Sent: Monday, January 27, 2020 7:50 AM > To: users > Subject: [ovirt-users] [ANN] oVirt 4.3.8 is now generally available > > The oVirt Project is pleased to announce the general availability of oVirt > 4.3.8 as of January 27th, 2020. > > > > This update is the eighth 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.7 or later (but < 8) > > * CentOS Linux (or similar) 7.7 or later (but < 8) > > > > This release supports Hypervisor Hosts on x86_64 and ppc64le architectures > for: > > * Red Hat Enterprise Linux 7.7 or later (but < 8) > > * CentOS Linux (or similar) 7.7 or later (but < 8) > > * oVirt Node 4.3 (available for x86_64 only) > > > > 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 Node and Appliance have been updated including: > > - oVirt 4.3.8: http://www.ovirt.org/release/4.3.8/ > > * Including fixes for CVE-2019-19336 oVirt Engine Cross Site Scripting > Vulnerability< > https://www.symantec.com/security-center/vulnerabilities/writeup/111466> > > - Latest CentOS 7.7 updates including: > > * CEBA-2019:3970 CentOS 7 ca-certificates BugFix Update< > https://lists.centos.org/pipermail/centos-announce/2019-December/035571.html > > > > * CEBA-2019:3971 CentOS 7 curl BugFix Update< > https://lists.centos.org/pipermail/centos-announce/2019-December/035558.html > > > > * CEBA-2019:3985 CentOS 7 iproute BugFix Update< > https://lists.centos.org/pipermail/centos-announce/2019-December/035568.html > > > > * CESA-2019:3979 Important CentOS 7 kernel Security Update< > https://lists.centos.org/pipermail/centos-announce/2019-December/035574.html > > > > * CEBA-2019:4106 CentOS 7 kernel BugFix Update< > https://lists.centos.org/pipermail/centos-announce/2019-December/035575.html > > > > * CEBA-2019:3983 CentOS 7 util-linux BugFix Update< > https://lists.centos.org/pipermail/centos-announce/2019-December/035567.html > > > > * CEBA-2019:3972 CentOS 7 sssd BugFix Update< > https://lists.centos.org/pipermail/centos-announce/2019-December/035565.html > > > > * CEBA-2019:3969 CentOS 7 samba BugFix Update< > https://lists.centos.org/pipermail/centos-announce/2019-December/035561.html > > > > * CEBA-2019:3975 CentOS 7 libvirt BugFix Update< > https://lists.centos.org/pipermail/centos-announce/2019-December/035562.html > > > > * CEEA-2019:4161 CentOS 7 microcode_ctl Enhancement Update< > https://lists.centos.org/pipermail/centos-announce/2019-December/035586.html > > > > * CESA-2019:4190 Important CentOS 7 nss Security Update< > https://lists.centos.org/pipermail/centos-announce/2019-December/035590.html > > > > * CESA-2019:4190 Important CentOS 7 nss-softokn Security Update< > https://lists.centos.org/pipermail/centos-announce/2019-December/035589.html > > > > * CESA-2019:4190 Important CentOS 7 nss-util Security Update< > https://lists.centos.org/pipermail/centos-announce/2019-December/035587.html > > > > * CEBA-2019:3977 CentOS 7 numactl BugFix Update< > https://lists.centos.org/pipermail/centos-announce/2019-December/035573.html > > > > * CEBA-2019:3982 CentOS 7 selinux-policy BugFix Update< > https://lists.centos.org/pipermail/centos-announce/2019-December/035559.html > > > > * CEBA-2019:3973 CentOS 7 sos BugFix Update< > https://lists.centos.org/pipermail/centos-announce/2019-December/035572.html > > > > * CESA-2019:3976 Low CentOS 7 tcpdump Security Update< > https://lists.centos.org/pipermail/centos-announce/2019-December/035570.html > > > > - latest CentOS Virt and Storage SIG updates: > > * Ansible 2.9.4: > https://github.com/ansible/ansible/blob/stable-2.9/changelogs/CHANGELOG-v2.… > > * Glusterfs 6.7: https://docs.gluster.org/en/latest/release-notes/6.7/ > > > > Given the amount of security fixes provided by this release, upgrade is > recommended as soon as practical. > > > Additional Resources: > > * Read more about the oVirt 4.3.8 release highlights: > http://www.ovirt.org/release/4.3.8/ > > * 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.8/ > > [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<mailto:sbonazzo@redhat.com> > > [ > https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9d… > ]<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. > > -- 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. <https://mojo.redhat.com/docs/DOC-1199578>*

2 1

feature policy='require' name='md-clear'
by thomas.c.albrecht＠lmco.com 27 Jan '20

27 Jan '20

I had oVirt 4.3 running on CentOS just fine for months. I did a yum update, and now the hosted engine isn't starting up. [root@nazgul qemu]# hosted-engine --vm-status --== Host nazgul.glamdring.offline (id: 1) status ==-- conf_on_shared_storage : True Status up-to-date : True Hostname : nazgul.glamdring.offline Host ID : 1 Engine status : {"reason": "bad vm status", "health": "bad", "vm": "down_unexpected", "detail": "Down"} Score : 0 stopped : False Local maintenance : False crc32 : fdab6d19 local_conf_timestamp : 2357 Host timestamp : 2357 Extra metadata (valid at timestamp): metadata_parse_version=1 metadata_feature_version=1 timestamp=2357 (Sat Jan 25 22:14:55 2020) host-id=1 score=0 vm_conf_refresh_time=2357 (Sat Jan 25 22:14:55 2020) conf_on_shared_storage=True maintenance=False state=EngineUnexpectedlyDown stopped=False timeout=Wed Dec 31 19:47:06 1969 Digging through the logs, I'm seeing an error that seems to be caused by an updated version of libvirt. Jan 25 22:13:05 nazgul libvirtd: 2020-01-26 03:13:05.879+0000: 4307: error : virCPUx86Compare:1785 : the CPU is incompatible with host CPU: Host CPU does not provide required features: md-clear In my /etc/libvirt/qemu/HostedEngine.xml, I'm thinking this line is the problem: <feature policy='require' name='md-clear'/> Looking at my cpu flags, md-clear ain't one of them: model name : Intel(R) Xeon(R) CPU E5-2670 0 @ 2.60GHz stepping : 7 microcode : 0x714 cpu MHz : 3000.061 cache size : 20480 KB physical id : 1 siblings : 16 core id : 7 cpu cores : 8 apicid : 47 initial apicid : 47 fpu : yes fpu_exception : yes cpuid level : 13 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm pcid dca sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer aes xsave avx lahf_lm epb ssbd ibrs ibpb stibp tpr_shadow vnmi flexpriority ept vpid xsaveopt dtherm ida arat pln pts spec_ctrl intel_stibp flush_l1d Any idea of how to remove that from the required CPU flags? Why is that needed?

3 3

ovirt_vm ansible module -- how to wait for ova export to finish
by Jayme 27 Jan '20

27 Jan '20

I wrote a simple task that is using the ovirt_vm module https://docs.ansible.com/ansible/latest/modules/ovirt_vm_module.html -- it essentially loops over a list of vms and exports them to OVA. The problem I have is the task is deemed changed once it successfully submits the export task to oVirt. This means that if I gave it a list of 100 Vms I believe it would start an export task on all of them. I want to prevent this and have it only export one VM at a time. In order to do this I believe I will need to find a way for the task to wait and somehow verify that the export was completed before submitting a task for the next VM export. Any ideas? - name: Export the VM ovirt_vm: auth: "{{ ovirt_auth }}" name: "{{ item }}" state: exported cluster: default export_ova: host: Host0 filename: "{{ item }}" directory: /backup/ with_items: "{{ vms }}"

3 6

upgrading ovirt host from 4.1 to 4.2
by Crazy Ayansh 25 Jan '20

25 Jan '20

Hi Team, I need a quick help from you. I need to upgrade ovirt host server from 4.1 to 4.2 version but i am getting below errors :- --> Finished Dependency Resolution Error: Package: nfs-ganesha-nullfs-2.3.3-1.el7.x86_64 (@ovirt-4.1-centos-gluster38) Requires: nfs-ganesha = 2.3.3-1.el7 Removing: nfs-ganesha-2.3.3-1.el7.x86_64 (@ovirt-4.1-centos-gluster38) nfs-ganesha = 2.3.3-1.el7 Updated By: nfs-ganesha-2.5.5-1.el7.x86_64 (ovirt-4.2-centos-gluster312) nfs-ganesha = 2.5.5-1.el7 Available: nfs-ganesha-2.5.2-1.el7.x86_64 (ovirt-4.2-centos-gluster312) nfs-ganesha = 2.5.2-1.el7 Available: nfs-ganesha-2.5.3-1.el6.x86_64 (ovirt-4.2-centos-gluster312) nfs-ganesha = 2.5.3-1.el6 Available: nfs-ganesha-2.5.3-1.el7.x86_64 (ovirt-4.2-centos-gluster312) nfs-ganesha = 2.5.3-1.el7 You could try using --skip-broken to work around the problem You could try running: rpm -Va --nofiles --nodigest This host server also have hosted engine running on it. I am using local storage for hosted engine. Can any one help on above. Thanks Shashank

2 4

gluster shard size
by Alex McWhirter 24 Jan '20

24 Jan '20

building a new gluster volume this weekend, trying to optimize it fully for virt. RHGS states that it supports only a 512mb shard size, so i ask why is the default for ovirt 64mb?

1 0

Re: KVM (libvirt) VM Import
by jorgevisentini＠gmail.com 24 Jan '20

24 Jan '20

Hi Paul, thanks for your reply. I imported the VM with the command below, but I had that create a Export Domain on oVirt for this task. Only problem this task is that is in two parts, first part is export to Export Domain, on NFS, and second part is import on oVirt through of the Export Domain. This was the only way I managed to import. virt-v2v -ic qemu+ssh://root@10.255.255.23/system TEMPLATE-WINDOWS2019 -o rhev -os 10.255.255.22:/export --network TEMPLATE-WINDOWS2019 Thanks again.

1 0

API OVA export - getting job id/job status
by lars.stolpe＠bvg.de 24 Jan '20

24 Jan '20

hi, I tryed this with API 4.2 and 4.3. purpose of the following script is, to export a given list of vm as OVA one after another. To reach that i need to monitor the job status and pause the script till the actual export is done. The script works fine, but not the restriction of the returned jobs to the one spcificaly job i need to monitor. Therefor the script pauses on *any* running job. the working script: #!/usr/bin/python import logging import time import ovirtsdk4 as sdk import ovirtsdk4.types as types connection = sdk.Connection( url='https://ovirtman12/ovirt-engine/api', username='admin@internal', password='***', ca_file='/etc/pki/ovirt-engine/ca-ovirtman12.pem', ) hosts_service = connection.system_service().hosts_service() hosts = hosts_service.list()[0] vms_service = connection.system_service().vms_service() vms = vms_service.list(search='name=blxlic954') for vm in vms: # print("%s (%s)" % (vm.name, vm.id)) vm_service = vms_service.vm_service(vm.id) start_time = (time.strftime('%Y%m%d_%H%M%S', time.localtime(int(time.time())))) vm_service.export_to_path_on_host( host=types.Host(id=hosts.id), directory='/nfs_c3/export', filename=('%s_backup_%s.ova' % (vm.name, start_time)), wait=True, ) # time.sleep(5) jobs_service = connection.system_service().jobs_service() jobs = jobs_service.list(search='') for job in jobs: print(job.id, job.description) # job = jobs_service.job_service(job.id).get() while job.status == types.JobStatus.STARTED: time.sleep(10) job = jobs_service.job_service(job.id).get() print('job-status: %s' % (job.status)) connection.close() The line jobs = jobs_service.list(search='') works fine as long as the search pattern is empty. if i try to restrict the results returned like this: jobs = jobs_service.list(search='description=*blxlic954*') i get an error: bad sql grammar [select * from (select * from job where ( job id in (select distinct job.job id from job where ( ) )) order by start time asc) as t1 offset (1 -1) limit 2147483647]; nested exception is org.postgresql.util.psqlexception: error: syntax error at or near ")" looks like the 'where' clause is not filled correctly. Am i wrong with my syntax or ist that a bug? Is there another way to get the correct job id/status?

4 6

Hyperconverged solution
by Benedetto Vassallo 24 Jan '20

24 Jan '20

Hello Guys, Here at University of Palermo (Italy) we are planning to switch from vmware to ovirt using the hyperconverged solution. Our design is a 6 nodes cluster, each node with this configuration: - 1x Dell PowerEdge R7425 server; - 2x AMD EPYC 7301 Processor; - 512GB of RAM (8x 64GB LRDIMM, 2666MT/s, Quad Rank); - 2x Broadcom 57412 Dual Port 10Gb SFP+ ethernet card; - 3x 600GB 10K RPM SAS for the OS (Raid1 + hotspare); - 5x 1.2TB 10K RPM SAS for the hosted storage domain (Raid5 + hotspare); - 11x 2.4TB 10KRPM SAS for the vm data domain (Raid6 + hotspare); - 4x 960GB SSD SAS for an additional SSD storage domain (Raid5 + hotspare); Is this configuration supported or I have to change something? Thank you and Best Regards. -- Benedetto Vassallo Responsabile U.O. Sviluppo e manutenzione dei sistemi Sistema Informativo di Ateneo Università degli studi di Palermo Phone: +3909123860056 Fax: +3909123860880

5 9

ovirt upgrade
by David David 24 Jan '20

24 Jan '20

hi all how do upgrade from 4.2.5 to 4.3.7 ? what steps are necessary, are the same as when upgrading from 4.1 to 4.2? # engine-upgrade-check # yum update ovirt*setup* # engine-setup thanks

3 3

Ovirt 4.3
by eevans＠digitaldatatechs.com 24 Jan '20

24 Jan '20

I set up the repository as per Ovirt instructions on Centos 7 x64, but when I yum install ovirt-engine I get missing dependencies. Here are the errors: Error: Package: ovirt-engine-backend-4.3.7.2-1.el7.noarch (ovirt-4.3) Requires: ebay-cors-filter Error: Package: ovirt-engine-setup-plugin-ovirt-engine-4.3.7.2-1.el7.noarch (ovirt-4.3) Requires: rh-postgresql10-postgresql-contrib Error: Package: ovirt-provider-ovn-1.2.27-1.el7.noarch (ovirt-4.3) Requires: python-ovsdbapp Error: Package: ovirt-engine-4.3.7.2-1.el7.noarch (ovirt-4.3) Requires: openstack-java-keystone-client >= 3.2.7 Error: Package: ovirt-engine-metrics-1.3.5.1-1.el7.noarch (ovirt-4.3) Requires: ansible >= 2.8.3 Available: ansible-2.4.2.0-2.el7.noarch (extras) ansible = 2.4.2.0-2.el7 Error: Package: ovirt-provider-ovn-1.2.27-1.el7.noarch (ovirt-4.3) Requires: openvswitch >= 2.7 Error: Package: ovirt-engine-4.3.7.2-1.el7.noarch (ovirt-4.3) Requires: openstack-java-cinder-model >= 3.2.7 Error: Package: ovirt-ansible-manageiq-1.1.14-1.el7.noarch (ovirt-4.3) Requires: ansible >= 2.7.2 Installing: ansible-2.4.2.0-2.el7.noarch (extras) ansible = 2.4.2.0-2.el7 Error: Package: ovirt-ansible-vm-infra-1.1.22-1.el7.noarch (ovirt-4.3) Requires: ansible >= 2.7.2 Available: ansible-2.4.2.0-2.el7.noarch (extras) ansible = 2.4.2.0-2.el7 Error: Package: ovirt-provider-ovn-1.2.27-1.el7.noarch (ovirt-4.3) Requires: openvswitch-ovn-common >= 2.7 Error: Package: ovirt-engine-backend-4.3.7.2-1.el7.noarch (ovirt-4.3) Requires: novnc >= 0.5.0 Error: Package: ovirt-engine-4.3.7.2-1.el7.noarch (ovirt-4.3) Requires: collectd-write_http Error: Package: ovirt-ansible-repositories-1.1.5-1.el7.noarch (ovirt-4.3) Requires: ansible >= 2.7.2 Available: ansible-2.4.2.0-2.el7.noarch (extras) ansible = 2.4.2.0-2.el7 Error: Package: ovirt-ansible-infra-1.1.13-1.el7.noarch (ovirt-4.3) Requires: ansible >= 2.7.2 Installing: ansible-2.4.2.0-2.el7.noarch (extras) ansible = 2.4.2.0-2.el7 Error: Package: ovirt-engine-4.3.7.2-1.el7.noarch (ovirt-4.3) Requires: openstack-java-glance-model >= 3.2.7 Error: Package: ovirt-provider-ovn-1.2.27-1.el7.noarch (ovirt-4.3) Requires: python-openvswitch >= 2.7 Error: Package: ovirt-engine-4.3.7.2-1.el7.noarch (ovirt-4.3) Requires: openstack-java-keystone-model >= 3.2.7 Error: Package: ovirt-engine-4.3.7.2-1.el7.noarch (ovirt-4.3) Requires: collectd-write_syslog Error: Package: ovirt-ansible-image-template-1.1.12-1.el7.noarch (ovirt-4.3) Requires: ansible >= 2.7.2 Available: ansible-2.4.2.0-2.el7.noarch (extras) ansible = 2.4.2.0-2.el7 Error: Package: ovirt-engine-dwh-setup-4.3.6-1.el7.noarch (ovirt-4.3) Requires: rh-postgresql10-postgresql-server Error: Package: ovirt-engine-websocket-proxy-4.3.7.2-1.el7.noarch (ovirt-4.3) Requires: python-websockify >= 0.6.0 Error: Package: ovirt-engine-4.3.7.2-1.el7.noarch (ovirt-4.3) Requires: nimbus-jose-jwt >= 5.12 Error: Package: ovirt-engine-4.3.7.2-1.el7.noarch (ovirt-4.3) Requires: openstack-java-glance-client >= 3.2.7 Error: Package: ovirt-engine-dwh-4.3.6-1.el7.noarch (ovirt-4.3) Requires: rh-postgresql10-postgresql-server Error: Package: ovirt-engine-4.3.7.2-1.el7.noarch (ovirt-4.3) Requires: openstack-java-resteasy-connector >= 3.2.7 Error: Package: ovirt-ansible-engine-setup-1.1.9-1.el7.noarch (ovirt-4.3) Requires: ansible >= 2.7.2 Available: ansible-2.4.2.0-2.el7.noarch (extras) ansible = 2.4.2.0-2.el7 Error: Package: ovirt-ansible-hosted-engine-setup-1.0.32-1.el7.noarch (ovirt-4.3) Requires: ansible >= 2.7 Available: ansible-2.4.2.0-2.el7.noarch (extras) ansible = 2.4.2.0-2.el7 Error: Package: ovirt-ansible-disaster-recovery-1.2.0-1.el7.noarch (ovirt-4.3) Requires: ansible >= 2.7.2 Available: ansible-2.4.2.0-2.el7.noarch (extras) ansible = 2.4.2.0-2.el7 Error: Package: ovirt-engine-4.3.7.2-1.el7.noarch (ovirt-4.3) Requires: rh-postgresql10-postgresql-server Error: Package: ovirt-ansible-hosted-engine-setup-1.0.32-1.el7.noarch (ovirt-4.3) Requires: ansible >= 2.7 Installing: ansible-2.4.2.0-2.el7.noarch (extras) ansible = 2.4.2.0-2.el7 Error: Package: python2-ovirt-engine-lib-4.3.7.2-1.el7.noarch (ovirt-4.3) Requires: python-daemon Error: Package: ovirt-engine-tools-backup-4.3.7.2-1.el7.noarch (ovirt-4.3) Requires: rh-postgresql10-postgresql Error: Package: ovirt-engine-4.3.7.2-1.el7.noarch (ovirt-4.3) Requires: ansible >= 2.7.2 Available: ansible-2.4.2.0-2.el7.noarch (extras) ansible = 2.4.2.0-2.el7 Error: Package: ovirt-ansible-shutdown-env-1.0.3-1.el7.noarch (ovirt-4.3) Requires: ansible >= 2.7 Available: ansible-2.4.2.0-2.el7.noarch (extras) ansible = 2.4.2.0-2.el7 Error: Package: ovirt-ansible-vm-infra-1.1.22-1.el7.noarch (ovirt-4.3) Requires: ansible >= 2.7.2 Installing: ansible-2.4.2.0-2.el7.noarch (extras) ansible = 2.4.2.0-2.el7 Error: Package: ovirt-engine-4.3.7.2-1.el7.noarch (ovirt-4.3) Requires: openstack-java-cinder-client >= 3.2.7 Error: Package: ovirt-imageio-common-1.5.2-0.el7.x86_64 (ovirt-4.3) Requires: qemu-img-rhev Error: Package: ovirt-engine-4.3.7.2-1.el7.noarch (ovirt-4.3) Requires: json-smart >= 2.2 Error: Package: ovirt-engine-setup-plugin-ovirt-engine-4.3.7.2-1.el7.noarch (ovirt-4.3) Requires: openvswitch-ovn-central >= 2.7 Error: Package: ovirt-ansible-infra-1.1.13-1.el7.noarch (ovirt-4.3) Requires: ansible >= 2.7.2 Available: ansible-2.4.2.0-2.el7.noarch (extras) ansible = 2.4.2.0-2.el7 Error: Package: ovirt-engine-4.3.7.2-1.el7.noarch (ovirt-4.3) Requires: ansible >= 2.7.2 Installing: ansible-2.4.2.0-2.el7.noarch (extras) ansible = 2.4.2.0-2.el7 Error: Package: ovirt-ansible-disaster-recovery-1.2.0-1.el7.noarch (ovirt-4.3) Requires: ansible >= 2.7.2 Installing: ansible-2.4.2.0-2.el7.noarch (extras) ansible = 2.4.2.0-2.el7 Error: Package: ovirt-ansible-engine-setup-1.1.9-1.el7.noarch (ovirt-4.3) Requires: ansible >= 2.7.2 Installing: ansible-2.4.2.0-2.el7.noarch (extras) ansible = 2.4.2.0-2.el7 Error: Package: ovirt-engine-dwh-4.3.6-1.el7.noarch (ovirt-4.3) Requires: rh-postgresql10-postgresql-contrib Error: Package: ovirt-ansible-manageiq-1.1.14-1.el7.noarch (ovirt-4.3) Requires: ansible >= 2.7.2 Available: ansible-2.4.2.0-2.el7.noarch (extras) ansible = 2.4.2.0-2.el7 Error: Package: ovirt-engine-4.3.7.2-1.el7.noarch (ovirt-4.3) Requires: archaius-core Error: Package: ovirt-engine-4.3.7.2-1.el7.noarch (ovirt-4.3) Requires: rxjava Error: Package: ovirt-ansible-roles-1.1.7-1.el7.noarch (ovirt-4.3) Requires: ansible >= 2.7.2 Available: ansible-2.4.2.0-2.el7.noarch (extras) ansible = 2.4.2.0-2.el7 Error: Package: ovirt-ansible-roles-1.1.7-1.el7.noarch (ovirt-4.3) Requires: ansible >= 2.7.2 Installing: ansible-2.4.2.0-2.el7.noarch (extras) ansible = 2.4.2.0-2.el7 Error: Package: ovirt-engine-dwh-setup-4.3.6-1.el7.noarch (ovirt-4.3) Requires: rh-postgresql10-postgresql-contrib Error: Package: ovirt-provider-ovn-1.2.27-1.el7.noarch (ovirt-4.3) Requires: openvswitch-ovn-central >= 2.7 Error: Package: ovirt-engine-4.3.7.2-1.el7.noarch (ovirt-4.3) Requires: hystrix-core Error: Package: ovirt-engine-backend-4.3.7.2-1.el7.noarch (ovirt-4.3) Requires: novnc < 0.6.0 Error: Package: ovirt-engine-4.3.7.2-1.el7.noarch (ovirt-4.3) Requires: collectd-postgresql Error: Package: ovirt-engine-4.3.7.2-1.el7.noarch (ovirt-4.3) Requires: rh-postgresql10-postgresql-contrib Error: Package: ovirt-engine-4.3.7.2-1.el7.noarch (ovirt-4.3) Requires: openstack-java-client >= 3.2.7 Error: Package: ovirt-engine-4.3.7.2-1.el7.noarch (ovirt-4.3) Requires: collectd-disk Error: Package: ovirt-engine-4.3.7.2-1.el7.noarch (ovirt-4.3) Requires: collectd Error: Package: ovirt-ansible-image-template-1.1.12-1.el7.noarch (ovirt-4.3) Requires: ansible >= 2.7.2 Installing: ansible-2.4.2.0-2.el7.noarch (extras) ansible = 2.4.2.0-2.el7 Error: Package: ovirt-engine-4.3.7.2-1.el7.noarch (ovirt-4.3) Requires: openstack-java-quantum-client >= 3.2.7 Error: Package: ovirt-engine-4.3.7.2-1.el7.noarch (ovirt-4.3) Requires: openstack-java-quantum-model >= 3.2.7 Error: Package: ovirt-ansible-cluster-upgrade-1.1.14-1.el7.noarch (ovirt-4.3) Requires: ansible >= 2.7.2 Available: ansible-2.4.2.0-2.el7.noarch (extras) ansible = 2.4.2.0-2.el7 Error: Package: ovirt-engine-4.3.7.2-1.el7.noarch (ovirt-4.3) Requires: hystrix-metrics-event-stream Error: Package: ovirt-ansible-repositories-1.1.5-1.el7.noarch (ovirt-4.3) Requires: ansible >= 2.7.2 Installing: ansible-2.4.2.0-2.el7.noarch (extras) ansible = 2.4.2.0-2.el7 Error: Package: ovirt-ansible-cluster-upgrade-1.1.14-1.el7.noarch (ovirt-4.3) Requires: ansible >= 2.7.2 Installing: ansible-2.4.2.0-2.el7.noarch (extras) ansible = 2.4.2.0-2.el7 Error: Package: ovirt-ansible-shutdown-env-1.0.3-1.el7.noarch (ovirt-4.3) Requires: ansible >= 2.7 Installing: ansible-2.4.2.0-2.el7.noarch (extras) ansible = 2.4.2.0-2.el7 Error: Package: ovirt-engine-setup-plugin-ovirt-engine-4.3.7.2-1.el7.noarch (ovirt-4.3) Requires: rh-postgresql10-postgresql-server Error: Package: ovirt-engine-metrics-1.3.5.1-1.el7.noarch (ovirt-4.3) Requires: ansible >= 2.8.3 Installing: ansible-2.4.2.0-2.el7.noarch (extras) ansible = 2.4.2.0-2.el7 You could try using --skip-broken to work around the problem You could try running: rpm -Va --nofiles --nodigest My understanding is all the dependencies should be in the ovirt repository. Also, the repos point to fc$release server. I change the fc to el$releaseserver before it even works. What did I miss? Eric Evans Digital Data Services LLC. 304.660.9080

2 3

Re: OVA export to NFS share slow
by Jürgen Walch 23 Jan '20

23 Jan '20

➢ I have a very similar setup as you and have just very recently started testing OVA exports for backup purposes to NFS attached storage. ➢ I have a three node HCI on GlusterFS (SSD backed) with 10Gbit and my ovirt management network is 10Gbit as well. My NFS storage server is an 8 x 8Tb 7200 RPM drives in RAID10 running CentOS 8x with 10Gbit link. Our setups are indeed similar, the main difference being, that my management network including the connection to the NFS server is only 1Gbit. Only GlusterFS has 10Gbit here. ➢ I haven't done specific measurement yet as I just setup the storage today but a test export of a 50Gb VM took just about ~10 minutes start to finish. Doing the maths this is ~80MiB/s and 20 times faster than in my setup. Lucky you 😊 Much less than your 10Gbit link between NFS Server and nodes could provide, but maybe close to the limit of the drives in your NFS server. The interesting thing is, that when setting up an export domain, stopping the VM and doing an export to the *same* NFS server, I'm getting write speeds as expected. Only the OVA export is terribly slow. The main difference I can see is the use of a loop device when exporting to OVA. The export to the export domain does something like /usr/bin/qemu-img convert -p -t none -T none -f raw {source disk on GlusterFS} {target disk on NFS server} whereas the OVA export will do /usr/bin/qemu-img convert -T none -O qcow2 {source snapshot on GlusterFS} /dev/loopX with /dev/loopX pointing to the NFS OVA target image. If you have the time and are willing to test, I would be interested in how fast your exports to an export domain are -- juergen

2 1

KVM (libvirt) VM Import
by jorgevisentini＠gmail.com 23 Jan '20

23 Jan '20

Hi all! I have a Suse KVM and I would like to import all VMs to oVirt. There is a easy mode to make it? I am try to import with Compute -> Virtual Machine -> Import. I can visualize the VMs but its show me the error when I try import: "libvirtError: Storage volume not found: no storage vol with matching path '/VMs01/VM/disk.qcow2" Anyone can help-me please?

2 1