- Users - oVirt List Archives

Problems creating bricks for new Gluster storage 4.4
by Jaret Garcia 02 Jun '20

02 Jun '20

Hi guys I'm trying to deploy a new ovirt environmet based in version 4.4 so I set up the following: 1 engine sever (stand alone) Version : 4.4.0.3 3 host servers (32 GB RAM, 2CPUs 8 core Xeon 5160, 500GB OS drive, 1 storage 8TB drive and 1 SSD 256GB (I'm trying to create a brick with SSD cache with no success) Detail of versions running on servers [ OS Version: RHEL - 8 - 1.1911.0.9.el8 OS Description: oVirt Node 4.4.0 Kernel Version: 4.18.0 - 147.8.1.el8_1.x86_64 KVM Version: 4.1.0 - 23.el8.1 LIBVIRT Version: libvirt-5.6.0-10.el8 VDSM Version: vdsm-4.40.16-1.el8 SPICE Version: 0.14.2 - 1.el8 GlusterFS Version: glusterfs-7.5-1.el8 CEPH Version: librbd1-12.2.7-9.el8 Open vSwitch Version: openvswitch-2.11.1-5.el8 Nmstate Version: nmstate-0.2.10-1.el8 ] Engine server working fine, all 3 host servers already part of the default cluster as hypervisors, then when I try to create a brick in any of the servers, using the 8TB HHDD and SSD as cache the process fails, in the GUI it just says "failed to creat brick on host" However in engine log as well as in brick-setup log I see: "err" : " Physical volume \"/dev/sdc\" still in use\n" "failed" : true,, (sdc in this case is the 8TB HHDD) Attached files of both logs. Thanks in advance, Jaret Garcia PACKET Next Generation IT & Telecom Tel. [ callto:+52%20%2855%29%2059898707 | +52 (55) 59898707 ] Of. [ callto:+52%20%2855%29%2047441200 | +52 (55) 47441200 ] Ext. 1210 email: [ mailto:jaret.garcia@packet.mx | jaret.garcia(a)packet.mx ] [ http://www.packet.mx/ | www.packet.mx ]

2 1

Mixing OS versions
by Stack Korora 01 Jun '20

01 Jun '20

Greetings, We've been using Scientific Linux 7 quite successfully with oVirt for years now. However, since there will not be a SL7 we are transitioning new servers to CentOS8. I would like to add a new oVirt hypervisor node. How bad of an idea is it to have a 8 system when the rest are 7 even though the version of oVirt will be the same? Thanks!

2 2

ovirt imageio problem...
by matteo fedeli 01 Jun '20

01 Jun '20

Hi! I' installed CentOS 8 and ovirt package following this step: systemctl enable --now cockpit.socket yum install https://resources.ovirt.org/pub/yum-repo/ovirt-release44.rpm yum module -y enable javapackages-tools yum module -y enable pki-deps yum module -y enable postgresql:12 yum -y install glibc-locale-source glibc-langpack-en localedef -v -c -i en_US -f UTF-8 en_US.UTF-8 yum update yum install ovirt-engine engine-setup (by keeping all default) It's possible ovirt-imageio-proxy service is not installed? (service ovirt-imageio-proxy status --> not found, yum install ovirt-imageio-proxy --> not found) I'm not able to upload iso... I also installed CA cert in firefox...

5 7

Mount options
by Tommaso - Shellrent 01 Jun '20

01 Jun '20

Hi to all. there is a way to change the mount options of a running storage domain with gluster, without set all to maintenance and shoutdown the vm on it!? Regards, -- -- Shellrent - Il primo hosting italiano Security First *Tommaso De Marchi* /COO - Chief Operating Officer/ Shellrent Srl Via dell'Edilizia, 19 - 36100 Vicenza Tel. 0444321155 <tel:+390444321155> | Fax 04441492177

2 1

Issues deploying 4.4 with HE on new EPYC hosts
by Mark R 01 Jun '20

01 Jun '20

Hello all, I have some EPYC servers that are not yet in production, so I wanted to go ahead and move them off of 4.3 (which was working) to 4.4. I flattened and reinstalled the hosts with CentOS 8.1 Minimal and installed all updates. Some very simple networking, just a bond and two iSCSI interfaces. After adding the oVirt 4.4 repo and installing the requirements, I run 'hosted-engine --deploy' and proceed through the setup. Everything looks as though it is going nicely and the local HE starts and runs perfectly. After copying the HE disks out to storage, the system tries to start it there but is using a different CPU definition and it's impossible to start it. At this point I'm stuck but hoping someone knows the fix, because this is as vanilla a deployment as I could attempt and it appears EPYC CPUs are a no-go right now with 4.4. When the HostedEngineLocal VM is running, the CPU definition is: <cpu mode='custom' match='exact' check='full'> <model fallback='forbid'>EPYC-IBPB</model> <vendor>AMD</vendor> <feature policy='require' name='x2apic'/> <feature policy='require' name='tsc-deadline'/> <feature policy='require' name='hypervisor'/> <feature policy='require' name='tsc_adjust'/> <feature policy='require' name='clwb'/> <feature policy='require' name='umip'/> <feature policy='require' name='arch-capabilities'/> <feature policy='require' name='cmp_legacy'/> <feature policy='require' name='perfctr_core'/> <feature policy='require' name='wbnoinvd'/> <feature policy='require' name='amd-ssbd'/> <feature policy='require' name='skip-l1dfl-vmentry'/> <feature policy='disable' name='monitor'/> <feature policy='disable' name='svm'/> <feature policy='require' name='topoext'/> </cpu> Once the HostedEngine VM is defined and trying to start, the CPU definition is simply: <cpu mode='custom' match='exact' check='partial'> <model fallback='allow'>EPYC</model> <topology sockets='16' cores='4' threads='1'/> <feature policy='require' name='ibpb'/> <feature policy='require' name='virt-ssbd'/> <numa> <cell id='0' cpus='0-63' memory='16777216' unit='KiB'/> </numa> </cpu> On attempts to start it, the host is logging this error: "CPU is incompatible with host CPU: Host CPU does not provide required features: virt-ssbd". So, the HostedEngineLocal VM works because it has a requirement set for 'amd-ssbd' instead of 'virt-ssbd', and a VM requiring 'virt-ssbd' can't run on EPYC CPUs with CentOS 8.1. As mentioned, the HostedEngine ran fine on oVirt 4.3 with CentOS 7.8, and on 4.3 the cpu definition also required 'virt-ssbd', so I can only imagine that perhaps this is due to the more recent 4.x kernel that I now need HE to require 'amd-ssbd' instead? Any clues to help with this? I can completely wipe/reconfigure the hosts as needed so I'm willing to try whatever so that I can move forward with a 4.4 deployment. Thanks! Mark

7 26

tun: unexpected GSO type: 0x0, gso_size 1368, hdr_len 66
by lejeczek 01 Jun '20

01 Jun '20

hi everyone, With 4.4 I get: ... tun: unexpected GSO type ... It happens to a "third-party" kernel, namely: 5.6.15-1.el8.elrepo.x86_64 on Centos 8. I wonder if anybody sees the same or similar and I also wonder if I should report it somewhere in Bugzilla as "heads-up" towards new kernels? [Fri May 29 08:00:02 2020] tun: unexpected GSO type: 0x0, gso_size 1368, hdr_len 66 [Fri May 29 08:00:02 2020] tun: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ [Fri May 29 08:00:02 2020] tun: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ [Fri May 29 08:00:02 2020] tun: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ [Fri May 29 08:00:02 2020] tun: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ [Fri May 29 08:00:02 2020] ------------[ cut here ]------------ [Fri May 29 08:00:02 2020] WARNING: CPU: 2 PID: 3605 at drivers/net/tun.c:2123 tun_do_read+0x524/0x6c0 [tun] [Fri May 29 08:00:02 2020] Modules linked in: sd_mod sg vhost_net vhost tap xt_CHECKSUM xt_MASQUERADE xt_conntrack nf_nat_tftp nf_conntrack_tftp tun nft_nat ipt_REJECT bridge nft_counter nft_objref nf_conntrack_netbios_ns nf_conntrack_broadcast nft_masq nft_fib_inet nft_fib_ipv4 nft_fib_ipv6 nft_fib nft_reject_inet nf_reject_ipv4 nf_reject_ipv6 nft_reject nft_ct nf_tables_set nft_chain_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 qedf qed ip6_tables crc8 nft_compat bnx2fc ip_set cnic uio libfcoe 8021q garp mrp stp llc libfc scsi_transport_fc nf_tables nfnetlink sunrpc vfat fat ext4 mbcache jbd2 snd_hda_codec_hdmi snd_hda_intel snd_intel_dspcfg snd_hda_codec snd_hda_core snd_hwdep snd_seq snd_seq_device edac_mce_amd snd_pcm kvm_amd kvm eeepc_wmi asus_wmi sp5100_tco sparse_keymap irqbypass rfkill wmi_bmof pcspkr joydev i2c_piix4 k10temp snd_timer snd soundcore gpio_amdpt gpio_generic acpi_cpufreq ip_tables xfs libcrc32c dm_crypt ax88179_178a usbnet mii hid_lenovo nouveau video mxm_wmi i2c_algo_bit [Fri May 29 08:00:02 2020] drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops crct10dif_pclmul ttm crc32_pclmul crc32c_intel ahci libahci drm ghash_clmulni_intel libata nvme ccp r8169 nvme_core realtek wmi t10_pi pinctrl_amd dm_mirror dm_region_hash dm_log dm_mod [Fri May 29 08:00:02 2020] CPU: 2 PID: 3605 Comm: vhost-3578 Not tainted 5.6.15-1.el8.elrepo.x86_64 #1 [Fri May 29 08:00:02 2020] Hardware name: System manufacturer System Product Name/PRIME B450M-A, BIOS 2006 11/13/2019 [Fri May 29 08:00:02 2020] RIP: 0010:tun_do_read+0x524/0x6c0 [tun] [Fri May 29 08:00:02 2020] Code: 00 6a 01 0f b7 44 24 22 b9 10 00 00 00 48 c7 c6 cb 33 09 c1 48 c7 c7 d1 33 09 c1 83 f8 40 48 0f 4f c2 31 d2 50 e8 4c 14 df c5 <0f> 0b 58 5a 48 c7 c5 ea ff ff ff e9 d2 fc ff ff 4c 89 e2 be 04 00 [Fri May 29 08:00:02 2020] RSP: 0018:ffffaaf301dfbcb8 EFLAGS: 00010292 [Fri May 29 08:00:02 2020] RAX: 0000000000000000 RBX: ffff88ceae6b4800 RCX: 0000000000000007 [Fri May 29 08:00:02 2020] RDX: 0000000000000000 RSI: 0000000000000096 RDI: ffff88d14e8996b0 [Fri May 29 08:00:02 2020] RBP: 000000000000004e R08: 0000000000000516 R09: 0000000000000055 [Fri May 29 08:00:02 2020] R10: 000000000000072e R11: ffffaaf301dfba88 R12: ffffaaf301dfbe50 [Fri May 29 08:00:02 2020] R13: ffff88d0e98b8900 R14: 0000000000000000 R15: 0000000000000000 [Fri May 29 08:00:02 2020] FS: 0000000000000000(0000) GS:ffff88d14e880000(0000) knlGS:0000000000000000 [Fri May 29 08:00:02 2020] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [Fri May 29 08:00:02 2020] CR2: 000055f6b3af2bd8 CR3: 00000003c6c84000 CR4: 0000000000340ee0 [Fri May 29 08:00:02 2020] Call Trace: [Fri May 29 08:00:02 2020] ? __wake_up_common+0x77/0x140 [Fri May 29 08:00:02 2020] tun_recvmsg+0x6b/0xf0 [tun] [Fri May 29 08:00:02 2020] handle_rx+0x573/0x940 [vhost_net] [Fri May 29 08:00:02 2020] ? log_used.part.45+0x20/0x20 [vhost] [Fri May 29 08:00:02 2020] vhost_worker+0xcc/0x140 [vhost] [Fri May 29 08:00:02 2020] kthread+0x10c/0x130 [Fri May 29 08:00:02 2020] ? kthread_park+0x80/0x80 [Fri May 29 08:00:02 2020] ret_from_fork+0x22/0x40 [Fri May 29 08:00:02 2020] ---[ end trace 9df20668f2e81977 ]--- many thanks, L.

2 1

Problem with Ovirt Machines
by aigini82＠gmail.com 31 May '20

31 May '20

Hi, Our company uses Ovirt to host some of its virtual machines. The version used is 4.2.6.4-1.el7. There are about 36 virtual hosts in it. The specifications used for the host machine is 30G RAM and 6 CPUs. Some of the VMs in the ovirt host run with 4 CPUs. Some with 2 CPUs. The problem I face now is that recently there was a need for high CPU and memory specs to setup a VM for DR. I created a VM with 16G RAM and 6 CPUs, without checking the CPUs available in the host first. After DR, the VM was brought down already. Then later another person in the team brought the VM back up for a different DR use, for a much larger DB restoration purpose. This caused the VM to pause due to storage error. And then worse things happened, whereby 2 other VMs inadvertently went down. Although I assumed that this was caused by storage errors/problems, the senior admins in the team concluded that the problem was due to fencing because of the max allotted CPU for the host being used for the VM. Now what I need to know is how to properly allocate CPU resources to a host to run multiple virtual machines in it like the situation above. I even tried to look for errors in vdsm.log, but this log was not available in the host machine nor in the affected VM. My colleague asked me to check "Events" section of the ovirt management interface to see past the past events. However, I don't find much details about the fencing activity or how the fencing occurred or what caused the fencing. And how did they conclude that the CPU count caused the fencing and not the storage?

2 1

Failed to add storage domain
by thunderlight1＠gmail.com 31 May '20

31 May '20

Hi! I have installed oVirt using the iso ovirt-node-ng-installer-4.3.2-2019031908.el7. I the did run the Host-engine deployment through Cockpit. I got an error when it tries to create the domain storage. It sucessfully mounted the NFS-share on the host. Bellow is the error I got: 2019-04-14 10:40:38,967+0200 INFO ansible skipped {'status': 'SKIPPED', 'ansible_task': u'Check storage domain free space', 'ansible_host': u'localhost', 'ansible_playbook': u'/usr/share/ovirt-hosted-engine-setup/ansible/trigger_role.yml', 'ansible_type': 'task'} 2019-04-14 10:40:38,967+0200 DEBUG ansible on_any args <ansible.executor.task_result.TaskResult object at 0x7fb6918ad9d0> kwargs 2019-04-14 10:40:39,516+0200 INFO ansible task start {'status': 'OK', 'ansible_task': u'ovirt.hosted_engine_setup : Activate storage domain', 'ansible_playbook': u'/usr/share/ovirt-hosted-engine-setup/ansible/trigger_role.yml', 'ansible_type': 'task'} 2019-04-14 10:40:39,516+0200 DEBUG ansible on_any args TASK: ovirt.hosted_engine_setup : Activate storage domain kwargs is_conditional:False 2019-04-14 10:40:41,923+0200 DEBUG var changed: host "localhost" var "otopi_storage_domain_details" type "<type 'dict'>" value: "{ "changed": false, "exception": "Traceback (most recent call last):\n File \"/tmp/ansible_ovirt_storage_domain_payload_xSFxOp/__main__.py\", line 664, in main\n storage_domains_module.post_create_check(sd_id)\n File \"/tmp/ansible_ovirt_storage_domain_payload_xSFxOp/__main__.py\", line 526, in post_create_check\n id=storage_domain.id,\n File \"/usr/lib64/python2.7/site-packages/ovirtsdk4/services.py\", line 3053, in add\n return self._internal_add(storage_domain, headers, query, wait)\n File \"/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py\", line 232, in _internal_add\n return future.wait() if wait else future\n File \"/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py\", line 55, in wait\n return self._code(response)\n File \"/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py\", line 229, in callback\n self._check_fault(response)\n File \"/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py\", line 132, in _check_fault\n self._raise_error(response , body)\n File \"/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py\", line 118, in _raise_error\n raise error\nError: Fault reason is \"Operation Failed\". Fault detail is \"[]\". HTTP response code is 400.\n", "failed": true, "msg": "Fault reason is \"Operation Failed\". Fault detail is \"[]\". HTTP response code is 400." }" 2019-04-14 10:40:41,924+0200 DEBUG var changed: host "localhost" var "ansible_play_hosts" type "<type 'list'>" value: "[]" 2019-04-14 10:40:41,924+0200 DEBUG var changed: host "localhost" var "play_hosts" type "<type 'list'>" value: "[]" 2019-04-14 10:40:41,924+0200 DEBUG var changed: host "localhost" var "ansible_play_batch" type "<type 'list'>" value: "[]" 2019-04-14 10:40:41,924+0200 ERROR ansible failed {'status': 'FAILED', 'ansible_type': 'task', 'ansible_task': u'Activate storage domain', 'ansible_result': u'type: <type \'dict\'>\nstr: {\'_ansible_parsed\': True, u\'exception\': u\'Traceback (most recent call last):\\n File "/tmp/ansible_ovirt_storage_domain_payload_xSFxOp/__main__.py", line 664, in main\\n storage_domains_module.post_create_check(sd_id)\\n File "/tmp/ansible_ovirt_storage_domain_payload_xSFxOp/__main__.py", line 526', 'task_duration': 2, 'ansible_host': u'localhost', 'ansible_playbook': u'/usr/share/ovirt-hosted-engine-setup/ansible/trigger_role.yml'} 2019-04-14 10:40:41,924+0200 DEBUG ansible on_any args <ansible.executor.task_result.TaskResult object at 0x7fb691843190> kwargs ignore_errors:None 2019-04-14 10:40:41,928+0200 INFO ansible stats { "ansible_playbook": "/usr/share/ovirt-hosted-engine-setup/ansible/trigger_role.yml", "ansible_playbook_duration": "00:37 Minutes", "ansible_result": "type: <type 'dict'>\nstr: {u'localhost': {'unreachable': 0, 'skipped': 6, 'ok': 23, 'changed': 1, 'failures': 1}}", "ansible_type": "finish", "status": "FAILED" } 2019-04-14 10:40:41,928+0200 INFO SUMMARY: Duration Task Name -------- -------- [ < 1 sec ] Execute just a specific set of steps [ 00:01 ] Force facts gathering [ 00:01 ] Check local VM dir stat [ 00:01 ] Obtain SSO token using username/password credentials [ 00:01 ] Fetch host facts [ < 1 sec ] Fetch cluster ID [ 00:01 ] Fetch cluster facts [ 00:01 ] Fetch Datacenter facts [ < 1 sec ] Fetch Datacenter ID [ < 1 sec ] Fetch Datacenter name [ 00:02 ] Add NFS storage domain [ 00:01 ] Get storage domain details [ 00:01 ] Find the appliance OVF [ 00:01 ] Parse OVF [ < 1 sec ] Get required size [ FAILED ] Activate storage domain 2019-04-14 10:40:41,928+0200 DEBUG ansible on_any args <ansible.executor.stats.AggregateStats object at 0x7fb69404eb90> kwargs Any suggestions on how fix this?

2 2

OVirt Upgrade from 4.3 to 4.4 - Hosted engine
by ccesario＠blueit.com.br 30 May '20

30 May '20

Hello, Could someone please inform if Upgrade from OVirt 4.3 to 4.4 when using Hosted engine is it supported !? According the documentation https://www.ovirt.org/documentation/upgrade_guide/#Upgrading_from_4-3 the upgrade procedure make reference only to "standalone engine". If it is supported, what is correct steps to do it? Best regards Carlos

4 5

Q: Fixing SELinux Permissions on oVirt node
by Andrei Verovski 29 May '20

29 May '20

Hi ! I’m struggling with SELinux blocking SNMP script from reading log file (oVirt node manually installed on CentOS 7). Log file is readable by all (chmod ugo+r). Scripts working fine when executed from terminal. I did not dig deep into CentOS internals, I’m mostly use Debian and SuSE. As far as I know, SELinux can’t be turned off on oVirt node. Thanks in advance for any suggestion(s). ********************** option in snmpd.conf extend .1.3.6.1.4.1.2021.7890.5 checkraid /opt/4anvcheckraid_hp.sh ********************** script 4anvcheckraid_hp.sh #!/bin/bash LOGFILE='/var/log/anvraidcheck.log' if [ ! -f $LOGFILE ]; then exit 0 fi # Variant 1 with sed sed '/^[ \t]*$/d' $LOGFILE | while read line; do echo "$line" exit 1 done # Variant 2 without sed while read line do if [[ "$line" =~ [^[:space:]] ]]; then echo "$line" exit 1 fi done < $LOGFILE ********************** SELinux audit log: type=AVC msg=audit(1590673970.198:469304): avc: denied { read } for pid=12142 comm="sed" name="anvraidcheck.log" dev="dm-8" ino=138 scontext=system_u:system_r:snmpd_t:s0 tcontext=system_u:object_r:cron_log_t:s0 tclass=file permissive=0 type=AVC msg=audit(1590673970.197:469303): avc: denied { read } for pid=12141 comm="4anvcheckraid_h" name="anvraidcheck.log" dev="dm-8" ino=138 scontext=system_u:system_r:snmpd_t:s0 tcontext=system_u:object_r:cron_log_t:s0 tclass=file permissive=0

4 6