- Users - oVirt List Archives

Gluster snapshots on hyperconverged with VDO ?
by guillaume.pavese＠interact-iv.com 17 Oct '18

17 Oct '18

I evaluate deploying ovirt 4.2 on centos 7.5 with VDO dedup in production. When deploying gluster with cockpit, after selecting deduplication/compression, the option to have the brick thin provisioned is grayed out. As a result, gluster snapshots are not possible. : - Neither in CLI : "snapshot create: failed: Snapshot is supported only for thin provisioned LV. Ensure that all bricks of data are thinly provisioned LV. " - Nor through the scheduler in volume management : I see the icon "Volume snapshots are scheduled" but I do not see any being created. There are no snapshot creation failure message in the manager. So I have two questions : - At deployment, is changing the gdeploy option manually from thick to thin supported for a LV on VDO device(or even a good idea)? - Should I open a bug report?

2 4

nul interface error when engine is creating ovirtmgmt bridge post-deployment
by Brad Riemann 17 Oct '18

17 Oct '18

Hello again, I've been working on an automated solution that uses the API to add a host on first boot, the code checks out (or maybe it doesn't), however I can confirm that the ovirt engine works through adding all requirements of a host properly except when it gets to setting up the bridge on the new node. The following link contains the log lines from the engine.log file, I can confirm that if I go to the engine web interface, I see my two interfaces on the new node, em1 and em2 (this is a Dell R420 server), and I can click on the "Setup Host Networks" button. The proceeding dialog window gives me the ability to drag over the ovirtmgmt logical interface onto the active physical interface and once saved I can see the engine go to work on setting up the bridge without an issue. My understanding is that this is supposed to be an automated process (which is what i'm going for), might someone be able to help me understand why im seeing the error I am? Am I just missing something from the api standpo int that is supposed to tell the system which physical interface it needs to use for building the ovirtmgmt bridge on top of? One thing to note (it shouldn't matter I don't think) but the engine is behind a nat, communicating over a vpn to the new node. I have to nat traffic from the engine so the ip address seen is different than what was supplied to the ansible playbook, i'm not familiar with ansible nor the playbooks used to know if that will have adverse impacts such as i'm seeing in the logs. Logs: https://pastebin.com/UC4WfBix Thank you in advance, Brad

2 5

How do you install oVirt Hyperconverged with six or nine nodes instead of the default three nodes?
by Ravi Chalasani 17 Oct '18

17 Oct '18

Already have working three node 4.2.5 HA cluster in the lab using this guide: https://ovirt.org/blog/2017/04/up-and-running-with-ovirt-4.1-and-gluster-st…. Now I would like to test a six or nine node cluster mentioned in the RHHI 1.1 guide. Is there some doc I am missing? Thanks

4 7

Periodic fall host
by Spickiy Nikita 17 Oct '18

17 Oct '18

Hi, i have oVirt instance (4.2.1.6-1.el7.centos). So, i have cluster with gluster. Hosts periodically non response and VM's is not responding. Usually it happens after get message "command GetGlusterVolumeHealInfoVDS failed: Message timeout which can be caused by communication issues". Will solve the trouble if an increase timeout for get heat status? And how to do it? I attach part log below: https://paste.fedoraproject.org/paste/8TTzwjMbYk32d7wd7Ix0Pw/raw 2018-10-15 14:44:22,582+03 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (DefaultQuartzScheduler6) [70cfd553] EVENT_ID: VDS_BROKER_COMMAND_FAILURE(10,802), VDSM ovirt3.example.org command GetGlusterVolumeHealInfoVDS failed: Message timeout which can be caused by communication issues 2018-10-15 14:44:22,584+03 ERROR [org.ovirt.engine.core.vdsbroker.gluster.GetGlusterVolumeHealInfoVDSCommand] (DefaultQuartzScheduler6) [70cfd553] Command 'GetGlusterVolumeHealInfoVDSCommand(HostName = ovirt3.example.org, GlusterVolumeVDSParameters:{hostId='39215015-2537-4329-921f-c11256f99e04', volumeName='domain1'})' execution failed: VDSGenericException: VDSNetworkException: Message timeout which can be caused by communication issues 2018-10-15 14:44:22,584+03 WARN [org.ovirt.engine.core.vdsbroker.VdsManager] (EE-ManagedThreadFactory-engine-Thread-7) [70cfd553] Host 'ovirt3.example.org' is not responding. It will stay in Connecting state for a grace period of 77 seconds and after that an attempt to fence the host will be issued. 2018-10-15 14:44:22,591+03 WARN [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engine-Thread-7) [70cfd553] EVENT_ID: VDS_HOST_NOT_RESPONDING_CONNECTING(9,008), Host ovirt3.example.org is not responding. It will stay in Connecting state for a grace period of 77 seconds and after that an attempt to fence the host will be issued. 2018-10-15 14:44:54,620+03 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engine-Thread-13) [] EVENT_ID: VDS_STORAGE_VDS_STATS_FAILED(189), Host ovirt3.example.org reports about one of the Active Storage Domains as Problematic. 2018-10-15 14:44:54,827+03 WARN [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engineScheduled-Thread-46) [6d9504d1] EVENT_ID: VDS_SET_NONOPERATIONAL_DOMAIN(522), Host ovirt3.example.org cannot access the Storage Domain(s) DOMAIN1 attached to the Data Center Default. Setting Host state to Non-Operational. 2018-10-15 14:44:54,840+03 WARN [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engineScheduled-Thread-46) [6d9504d1] EVENT_ID: CONNECT_STORAGE_POOL_FAILED(995), Failed to connect Host ovirt3.example.org to Storage Pool Default 2018-10-15 14:45:28,698+03 WARN [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engineScheduled-Thread-87) [] EVENT_ID: VM_NOT_RESPONDING(126), VM HostedEngine is not responding. 2018-10-15 14:45:30,296+03 WARN [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engineScheduled-Thread-72) [] EVENT_ID: VM_NOT_RESPONDING(126), VM vm2 is not responding. 2018-10-15 14:45:30,362+03 WARN [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engineScheduled-Thread-72) [] EVENT_ID: VM_NOT_RESPONDING(126), VM vm3 is not responding.

2 2

engine HA with keeplived
by du_hongyu＠yeah.net 17 Oct '18

17 Oct '18

hi, I find hosted-engine restore service about 3 min, Has someone develop engine HA with keeplived? Regards Hongyu Du

2 1

oVirt / tungsten-fabric integration
by Tatsuya Naganawa 16 Oct '18

16 Oct '18

Hi, has anyone tried integration between oVirt and tungsten-fabric? https://tungsten.io/ I tried for two node cluster and it seems to work well with custom vdsm hook (live migration is not tried yet). I described procedure briefly, so let me share it :) https://github.com/tnaganawa/ovirt-tungstenfabric-integration Best Regards, /// Tatsuya

1 0

Affinity rules in ovirt
by Hari Prasanth Loganathan 16 Oct '18

16 Oct '18

Hi Team, I tried to follow up the affinity rules using this tutorial : https://www.youtube.com/watch?v=rs_5BSqacWE but I have few clarifications in it., 1) I understand the VM to VM affinity, It means both the individual VMs needs to run on a single common host, Say I have 2 hosts, so what happens in case of failure of host running the VMs? 2) If I create a affinity group and I get the following data, i) What is host rule / vms rule - enabled, enforcing and positive ? "enforcing": "true", "hosts_rule": { "enabled": "true", "enforcing": "true", "positive": "false" }, "vms_rule": { "enabled": "false", "enforcing": "true", "positive": "false" } 3) What is the difference between VM to VM affinity and VM to Host affinity? Doc's are not very clear, so please any help is appreciated. Thanks, Hari -- DISCLAIMER - *MSysTechnologies LLC* This email message, contents and its attachments may contain confidential, proprietary or legally privileged information and is intended solely for the use of the individual or entity to whom it is actually intended. If you have erroneously received this message, please permanently delete it immediately and notify the sender. If you are not the intended recipient of the email message,you are notified strictly not to disseminate,distribute or copy this e-mail.E-mail transmission cannot be guaranteed to be secure or error-free as Information could be intercepted, corrupted, lost, destroyed, incomplete or contain viruses and MSysTechnologies LLC accepts no liability for the contents and integrity of this mail or for any damage caused by the limitations of the e-mail transmission.

5 10

Backport KVM bug fix for nested KVM in ESXi and Hyper-V
by Gianluca Cecchi 16 Oct '18

16 Oct '18

Hello, I send a dedicated subject message on this topic. Also, the reply to my other related message seems not visible inside list archive page for some reason. It seems this nasty problem in nested virt using pc-i440fx-rhel7.X.0 machine type with X >= 3 impacts not only vSphere as main hypervisor for nested KVM, but other hypervisors too (Hyper-V) and other machine types too and could be due to a bug in KVM, so in the kernel, if I understood correctly. According to this link below https://bugs.launchpad.net/qemu/+bug/1636217 and its comment by Roman Kagan in June this year: " This is a KVM bug. It has been fixed in mainstream Linux in commit d391f1207067268261add0485f0f34503539c5b0 Author: Vitaly Kuznetsov <email address hidden> Date: Thu Jan 25 16:37:07 2018 +0100 x86/kvm/vmx: do not use vm-exit instruction length for fast MMIO when running nested I was investigating an issue with seabios >= 1.10 which stopped working for nested KVM on Hyper-V. The problem appears to be in handle_ept_violation() function: when we do fast mmio we need to skip the instruction so we do kvm_skip_emulated_instruction(). This, however, depends on VM_EXIT_INSTRUCTION_LEN field being set correctly in VMCS. However, this is not the case. Intel's manual doesn't mandate VM_EXIT_INSTRUCTION_LEN to be set when EPT MISCONFIG occurs. While on real hardware it was observed to be set, some hypervisors follow the spec and don't set it; we end up advancing IP with some random value. I checked with Microsoft and they confirmed they don't fill VM_EXIT_INSTRUCTION_LEN on EPT MISCONFIG. Fix the issue by doing instruction skip through emulator when running nested. Fixes: 68c3b4d1676d870f0453c31d5a52e7e65c7448ae Suggested-by: Radim Krčmář <email address hidden> Suggested-by: Paolo Bonzini <email address hidden> Signed-off-by: Vitaly Kuznetsov <email address hidden> Acked-by: Michael S. Tsirkin <email address hidden> Signed-off-by: Radim Krčmář <email address hidden> Although the commit mentions Hyper-V as L0 hypervisor, the same problem pertains to ESXi. The commit is included in v4.16. " Is it possible to backport the fix to the kernel provided by plain RHEL/CentOS hosts and/or RHVH/ovirt-ng nodes? Thanks, Gianluca

1 0

custom emulated machine in L2 ESXi
by Gianluca Cecchi 16 Oct '18

16 Oct '18

Hello, I had similar problem in the past with ESXi 6.0 U2 host where I defined a VM and used it as oVirt node for nested virtualization. If I run on this "virtual" node an L2 VM all went well until custom emulated machine value was at "pc-i440fx-rhel7.2.0". At some point the default became 7.3 and the L2 VM was not able to boot any more: it remained in blank screen at boot. The same up to now in 4.2.6.1 where this default seems to be 7.5 I'm having same problem in a mini lab on a nuc6 where I have ESXi 6.7 installed and try to setup an hosted engine environment. This problem prevents me to configure the hosted engine because the L2 VM that should be the hosted engine freezes (?) during its first startup and I see indeed that the qemu-kvm process is started with option "-machine pc-i440fx-rhel7.5.0" Being stated that I'm in an unsupported configuration, I would like to understand if I can correct in some point and proceed. So some questions: 1) How can I understand what is the difference between running qemu-kvm with "-machine pc-i440fx-rhel7.2.0" ad "-machine pc-i440fx-rhel7.5.0" so that I can then dig with ESXi parameters eventually to tune the settings of its VM that becomes my oVirt hypervisor? 2) Do I have any chance to configure my oVirt node so that when it runs the hosted-engine deploy it runs the engine VM with 7.2 parameter? Any conf file on host where I can somehow force 7.2 compatibility or set it as default? 3) during gluster base hosted-engine deployment at first "local" startup how can I connect to the console of the hosted engine VM and see where it is blocked? Thanks in advance, Gianluca

1 1

4.2 User Portal
by Стаценко Константин Юрьевич 16 Oct '18

16 Oct '18

Hello! Users cannot edit and expand VM’s disks from the User Portal after 4.2 upgrade anymore. VM UI screenshot attached. Users can press Edit icon, but only “Editing” appears and nothing more. Same thing happens under admin’s accounts on User Portal. From Admin Portal everything is fine. How can we fix this issue, so users can edit they VM from the User Portal as it was in 4.1 ? Thanks.

4 9