- Users - oVirt List Archives

ovirt-guest-agent-common version and repo
by Gianluca Cecchi 03 Jul '18

03 Jul '18

Hello, on CentOS 7.x VM with epel enabled it seems that latest package is ovirt-guest-agent-common-1.0.14-1.el7.noarch and from its changelog it seems far from being up 2 date and released before 4.2.0 release... * Thu Nov 02 2017 Tomáš Golembiovský <tgolembi(a)redhat.com> - 1.0.14-1 - Bump to version 1.0.14 - Changed link to upstream sources Am I doing something wrong with it and its repo or is it not so important component even after upgrading to oVirt 4.2.x? Thanks, Gianluca

2 2

Ovirt and L2 Gateway
by carlgrundholm＠gmail.com 03 Jul '18

03 Jul '18

I have install ovirt 4.2.3 and everything seems to be working fine: I can create virtual (Geneve overlay) networks for communication between virtual machines via the external provider ovirt-provider-ovn by using the OWS switch on the cluster. Live migrations and everything else within the virtual environment works perfectly :-) For connections from virtual machines to physical VLAN's in a switch, I can also create a logical network which is created using the external provider ovirt-provider-ovn by specifying a connection to a physical VLAN network created as a separate data center network. This method requires that all ovirt-nodes (hosts) in the cluster have access to the physical network though. What I am looking for is a way to implement a L2 Gateway such that (not all) ovirt nodes (hosts) need to have direct access to the physical network. What I am looking for is a way where virtual machines can communicate with the L2 Gateway via virtual (Geneve overlay) networks. On the L2 Gateway the virtual network shall then be bridged to the physical VLAN on a dedicated network interface. My goal is that the virtual network and the physical network becomes one big broadcast domain. This concept has been described by different people on the Internet such as these articles: - https://weiti.org/ovn/2018/01/03/ovn-l2-breakout-options - https://wiki.openstack.org/wiki/Neutron/L2-GW How can I accomplish something similar in an ovirt-environment? Thanks in advance, Carl Grundholm

2 3

Dedicated underlay network for overlay traffic
by carlgrundholm＠gmail.com 03 Jul '18

03 Jul '18

I am going to be using OVN Geneve overlay networks extensively and I expect a lot of traffic on the underlay network being used for transmission of the tunnel traffic. In oVirt the default seems to be that the network "ovirtmgmt" is being used for the underlay network - which could cause problems for management traffic if vms are saturating the link with traffic on different OVN overlay networks. When selecting a specific cluster, selecting "Logical Networks" and pressing the "Manage Networks" button it is possible to specify that a specific Data Center Network shall be limited to one or more of the following traffic types: - VM Network - Management - Display Network - Migration Network - Gluster Network - Default Route Here I miss an option called "Underlay Network for OVN Geneve traffic" or similar. Is there a way - e.g. by editing some configuration files on the oVirt engine and on the oVirt nodes - to divert all overlay Geneve traffic away from the management interface unto a dedicated network interface? Carl

2 1

Feature: Live migration for High Performance VMs
by Sharon Gratch 02 Jul '18

02 Jul '18

Hi everyone, I would like to share our plan for supporting live migration for High Performance VMs (and in general to all VM types with pinning settings). Implementing this will be done in 2 phases: Phase 1: 1. Only manual live migration will be supported for high performance VMs type. 2. The user will need to manually choose the destination host to migrate his VM to (can't base on scheduler manager to find the most suitable host). 3. Source and destination hosts should have the same hardware and supports the exact same configuration. Phase 2: 1. Both automatic and manual live migration modes will be supported for HP VMs. 2. Destination host can be automatically selected by the engine (scheduler manager). 3. Source and destination hosts should fit but not be necessarily identical. More Details on that can be found on the feature page <https://www.ovirt.org/develop/release-management/features/virt/high-perform…> . Any feedback on this feature will be greatly appreciated. Thanks, Sharon

2 1

[ANN] oVirt 4.2.5 First Release Candidate is now available
by Sandro Bonazzola 02 Jul '18

02 Jul '18

The oVirt Project is pleased to announce the availability of the oVirt 4.2.5 First Release Candidate, as of July 2nd, 2018. This update is a release candidate of the fourth in a series of stabilization updates to the 4.2 series. This is pre-release software. This pre-release should not to be used in production. This release is available now for: * Red Hat Enterprise Linux 7.5 or later * CentOS Linux (or similar) 7.5 or later This release supports Hypervisor Hosts running: * Red Hat Enterprise Linux 7.5 or later * CentOS Linux (or similar) 7.5 or later See the release notes [1] for installation / upgrade instructions and a list of new features and bugs fixed. Notes: - oVirt Appliance is available - oVirt Node will be available soon [2] Additional Resources: * Read more about the oVirt 4.2.5 release highlights: http://www.ovirt.org/release/4.2.5/ * 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.2.5/ [2] http://resources.ovirt.org/pub/ovirt-4.2-pre/iso/ -- SANDRO BONAZZOLA MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://red.ht/sig>

1 0

Hosted engine Deploy failed
by Lakhwinder Rai 01 Jul '18

01 Jul '18

i have error while installing hosted engine. if anybody have solution for this,please help i stuck here from two days. [ INFO ] TASK [Wait for the host to be up] [ ERROR ] fatal: [localhost]: FAILED! => {"ansible_facts": {"ovirt_hosts": []}, "attempts": 120, "changed": false} [ INFO ] TASK [include_tasks] [ INFO ] ok: [localhost] [ INFO ] TASK [Remove local vm dir] [ INFO ] changed: [localhost] [ INFO ] TASK [Notify the user about a failure] [ ERROR ] fatal: [localhost]: FAILED! => {"changed": false, "msg": "The system may not be provisioned according to the playbook results: please check the logs for the issue, fix accordingly or re-deploy from scratch.\n"} thanks

2 1

oVirt HCI point-to-point interconnection
by Stefano Zappa 29 Jun '18

29 Jun '18

Good morning, I would like to kindly ask you a question about the feasibility of defining a point-to-point interconnection between three ovirt nodes. Initially with the idea of optimizing the direct communications between the nodes and especially the gluster communications, and so it would seem quite easy, then evaluating a more complex configuration, assuming to create an overlay L2 network on the three L3 point-to-point, using techniques like geneve, of which at the moment I have no mastery. If the direct routing of three nodes to interconnect the public network with the private overlay network was not easily doable, we could leave the private overlay network isolated from the outside world and connect the VM hosted engine directly to the two networks with two adapters. This layout with direct interconnection of the nodes without switches and a shared L2 overlay network between the nodes may in future be contemplated in future releases of your HCI solution? Thank you for your attention, have a nice day! Stefano Zappa. [cid:609f1f14-f74e-489f-b86d-08647efc6d1c] Stefano Zappa IT Specialist CAE - TT-3 Industrie Saleri Italo S.p.A. Phone: +39 0308250480 Fax: +39 0308250466 This message contains confidential information and is intended only for users(a)ovirt.org, infra(a)ovirt.org, devel(a)ovirt.org. If you are not users(a)ovirt.org, infra(a)ovirt.org, devel(a)ovirt.org you should not disseminate, distribute or copy this e-mail. Please notify Stefano.Zappa(a)saleri.it immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. Stefano Zappa therefore does not accept liability for any errors or omissions in the contents of this message, which arise as a result of e-mail transmission. If verification is required please request a hard-copy version. PRIVACY INFORMATION ART. 13 EU REG. 2016/679 We inform you that the personal data contained in the present and subsequent electronic communications will be processed in compliance with the EU Regulation 2016/679, for the purpose of and only for the time necessary to allow the sender to carry out the activities connected to the existing commercial relationships. The provision of personal data is not mandatory. However, failure to provide them determines the impossibility of achieving the aforementioned purpose. With regard to these data, is allowed the exercise of the rights set out in art. 13 and from the articles from 15 to 22 of EU Regulation 2016/679 and in particular the right to request the access to, updating, rectification and erasure of your personal data, as well as the right to object to processing and to lodge a complaint with the Supervisory Authority, by sending an e-mail to privacy(a)saleri.it. Data Controller of your personal data is Industrie Saleri Italo S.p.a., with registered office in via Ruca, 406 - 25065 Lumezzane (BS).

5 8

Snapshot error with Cinder/Ceph disk
by Matthias Leopold 29 Jun '18

29 Jun '18

Hi, i'm having problems with snapshotting Cinder/Ceph disks since upgrading to 4.2. Observed behavior has changed between 4.2.2 and 4.2.4. With oVirt 4.2.2 and Cinder 11.1.0 - oVirt snapshot fails (according to oVirt), but is listed in GUI - disk snapshot are visible in oVirt storage domain tab and Cinder CLI - first try to remove the oVirt snapshot fails (according to oVirt), but disk snapshots are removed from oVirt storage domain tab and Cinder CLI - second try to remove oVirt snapshot succeeds With oVirt 4.2.4 and Cinder 11.1.1 - oVirt snapshot fails "completely" - in Cinder logs i can see that disk snapshots are created and immediately deleted oVirt error log message is the same in both cases: "Failed in 'SnapshotVDS' method" I'm attaching logs from oVirt engine from the latter case. thx for any advice matthias

2 2

where did virbr0: come from?
by Conrad Jones 29 Jun '18

29 Jun '18

I installed * CentOS * Master repo for ovirt * create ovirtmgmt bridge via network scripts (not virbr0) * installed VDSM * installed cockpit * installed cockpit-ovirt-dashboard.noarch i suspect the virbr0 came from installing the cockpit-ovirt-dashboard.noarch components as it also installed a whole host of stuff like virt-manager-common.noarch Anyway this causes the hosted ovirt-engine vm install to fail from cockpit as "[ ERROR ] fatal: [localhost]: FAILED! => {"changed": false, "msg": "hostname 'host-141' doesn't uniquely match the interface 'enp3s0' selected for the management bridge; it matches also interface with IP [u'192.168.122.1']. Please make sure that the hostname got from the interface for the management network resolves only there.\n"}" ----------- [sysadmin@host-141 ~]$ ip addr 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: enp3s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master ovirtmgmt state UP group default qlen 1000 link/ether e0:d5:5e:73:ad:5e brd ff:ff:ff:ff:ff:ff inet6 fe80::e2d5:5eff:fe73:ad5e/64 scope link valid_lft forever preferred_lft forever 18: ovirtmgmt: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether e0:d5:5e:73:ad:5e brd ff:ff:ff:ff:ff:ff inet 192.168.1.141/24 brd 192.168.1.255 scope global ovirtmgmt valid_lft forever preferred_lft forever inet6 fe80::e2d5:5eff:fe73:ad5e/64 scope link valid_lft forever preferred_lft forever 19: virbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000 link/ether 52:54:00:e5:0d:40 brd ff:ff:ff:ff:ff:ff inet 192.168.122.1/24 brd 192.168.122.255 scope global virbr0 valid_lft forever preferred_lft forever 20: virbr0-nic: <BROADCAST,MULTICAST> mtu 1500 qdisc pfifo_fast master virbr0 state DOWN group default qlen 1000 link/ether 52:54:00:e5:0d:40 brd ff:ff:ff:ff:ff:ff

2 1

Unable to do Live Migration
by rni＠chef.net 28 Jun '18

28 Jun '18

Hello, I'm using a 4 node cluster oVirt 4.1. After updating the Engine to 4.2.3.8 (and ContOS 7.5), I tried to update the nodes too. Unfortunally, the live migration is not working (any more). Maybe it's related to following error found in engine.log 2018-06-19 09:32:53,469+02 WARN [org.ovirt.engine.core.bll.provider.network.openstack.CustomizedRESTEasyConnector] (EE-ManagedThreadFactory-engineScheduled-Thread-7) [4d6a7dc4] Cannot register external providers trust store: java.io.IOException: Keystore was tampered with, or password was incorrect 2018-06-19 09:32:53,475+02 ERROR [org.ovirt.engine.core.bll.provider.network.SyncNetworkProviderCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-7) [4d6a7dc4] Command 'org.ovirt.engine.core.bll.provider.network.SyncNetworkProviderCommand' failed: EngineException: (Failed with error unable to find valid certification path to requested target and code 5050) I'm using the selfsigned CA provided with oVirt. Nodes (source and destination) OS-Version:RHEL - 7 - 4.1708.el7.centos Kernelversion: 3.10.0 - 693.21.1.el7.x86_64 KVM-Version:2.9.0 - 16.el7_4.14.1 LIBVIRT-Version:libvirt-3.2.0-14.el7_4.9 VDSM-Version:vdsm-4.19.45-1.el7.centos SPICE-Version:0.12.8 - 2.el7.1 CEPH-Version:librbd1-0.94.5-2.el7 Kernel Features:PTI: 1, IBPB: 0, IBRS: 0 engine.log for the mirgration: 2018-06-14 13:13:30,300+02 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engine-Thread-246968) [] EVENT_ID: VM_MIGRATION_START_SYSTEM_INITIATED(67), Migration initiated by system (VM: vm_to_migrate, Source: SOURCE, Destination: DESTINATION, Reason: Host preparing for maintenance). 2018-06-14 13:13:32,886+02 INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmsStatisticsFetcher] (EE-ManagedThreadFactory-engineScheduled-Thread-94) [] Fetched 8 VMs from VDS 'f3749f1e-a68d-424f-aa3a-f0ec996df498' 2018-06-14 13:13:32,887+02 INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (EE-ManagedThreadFactory-engineScheduled-Thread-94) [] VM '4aff4193-ba75-481d-92b3-59b62cd8b111'(vm_to_migrate) was unexpectedly detected as 'MigratingTo' on VDS 'f3749f1e-a68d-424f-aa3a-f0ec996df498'(DESTINATION) (expected on 'ea7bae8f-d966-4baa-b8b4-a5522b88ec3a') 2018-06-14 13:13:32,887+02 INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (EE-ManagedThreadFactory-engineScheduled-Thread-94) [] VM '4aff4193-ba75-481d-92b3-59b62cd8b111' is migrating to VDS 'f3749f1e-a68d-424f-aa3a-f0ec996df498'(DESTINATION) ignoring it in the refresh until migration is done 2018-06-14 13:13:47,939+02 INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (EE-ManagedThreadFactory-engineScheduled-Thread-42) [] VM '4aff4193-ba75-481d-92b3-59b62cd8b111'(vm_to_migrate) was unexpectedly detected as 'MigratingTo' on VDS 'f3749f1e-a68d-424f-aa3a-f0ec996df498'(DESTINATION) (expected on 'ea7bae8f-d966-4baa-b8b4-a5522b88ec3a') 2018-06-14 13:13:47,939+02 INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (EE-ManagedThreadFactory-engineScheduled-Thread-42) [] VM '4aff4193-ba75-481d-92b3-59b62cd8b111' is migrating to VDS 'f3749f1e-a68d-424f-aa3a-f0ec996df498'(DESTINATION) ignoring it in the refresh until migration is done 2018-06-14 13:14:02,993+02 INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (EE-ManagedThreadFactory-engineScheduled-Thread-13) [] VM '4aff4193-ba75-481d-92b3-59b62cd8b111'(vm_to_migrate) was unexpectedly detected as 'MigratingTo' on VDS 'f3749f1e-a68d-424f-aa3a-f0ec996df498'(DESTINATION) (expected on 'ea7bae8f-d966-4baa-b8b4-a5522b88ec3a') 2018-06-14 13:14:02,993+02 INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (EE-ManagedThreadFactory-engineScheduled-Thread-13) [] VM '4aff4193-ba75-481d-92b3-59b62cd8b111' is migrating to VDS 'f3749f1e-a68d-424f-aa3a-f0ec996df498'(DESTINATION) ignoring it in the refresh until migration is done 2018-06-14 13:14:18,042+02 INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (EE-ManagedThreadFactory-engineScheduled-Thread-67) [] VM '4aff4193-ba75-481d-92b3-59b62cd8b111'(vm_to_migrate) was unexpectedly detected as 'MigratingTo' on VDS 'f3749f1e-a68d-424f-aa3a-f0ec996df498'(DESTINATION) (expected on 'ea7bae8f-d966-4baa-b8b4-a5522b88ec3a') 2018-06-14 13:14:18,042+02 INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (EE-ManagedThreadFactory-engineScheduled-Thread-67) [] VM '4aff4193-ba75-481d-92b3-59b62cd8b111' is migrating to VDS 'f3749f1e-a68d-424f-aa3a-f0ec996df498'(DESTINATION) ignoring it in the refresh until migration is done 2018-06-14 13:14:33,090+02 INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (EE-ManagedThreadFactory-engineScheduled-Thread-85) [] VM '4aff4193-ba75-481d-92b3-59b62cd8b111'(vm_to_migrate) was unexpectedly detected as 'MigratingTo' on VDS 'f3749f1e-a68d-424f-aa3a-f0ec996df498'(DESTINATION) (expected on 'ea7bae8f-d966-4baa-b8b4-a5522b88ec3a') 2018-06-14 13:14:33,090+02 INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (EE-ManagedThreadFactory-engineScheduled-Thread-85) [] VM '4aff4193-ba75-481d-92b3-59b62cd8b111' is migrating to VDS 'f3749f1e-a68d-424f-aa3a-f0ec996df498'(DESTINATION) ignoring it in the refresh until migration is done 2018-06-14 13:14:38,356+02 INFO [org.ovirt.engine.core.bll.provider.network.SyncNetworkProviderCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-43) [6d991f10] Lock Acquired to object 'EngineLock:{exclusiveLocks='[d1457e7e-f29d-49ac-b635-2457a7cbc59f=PROVIDER]', sharedLocks=''}' 2018-06-14 13:14:38,369+02 INFO [org.ovirt.engine.core.bll.provider.network.SyncNetworkProviderCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-43) [6d991f10] Running command: SyncNetworkProviderCommand internal: true. 2018-06-14 13:14:38,370+02 WARN [org.ovirt.engine.core.bll.provider.network.openstack.CustomizedRESTEasyConnector] (EE-ManagedThreadFactory-engineScheduled-Thread-43) [6d991f10] Cannot register external providers trust store: java.io.IOException: Keystore was tampered with, or password was incorrect 2018-06-14 13:14:38,379+02 ERROR [org.ovirt.engine.core.bll.provider.network.SyncNetworkProviderCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-43) [6d991f10] Command 'org.ovirt.engine.core.bll.provider.network.SyncNetworkProviderCommand' failed: EngineException: (Failed with error unable to find valid certification path to requested target and code 5050) 2018-06-14 13:14:38,382+02 INFO [org.ovirt.engine.core.bll.provider.network.SyncNetworkProviderCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-43) [6d991f10] Lock freed to object 'EngineLock:{exclusiveLocks='[d1457e7e-f29d-49ac-b635-2457a7cbc59f=PROVIDER]', sharedLocks=''}' 2018-06-14 13:14:48,139+02 INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (EE-ManagedThreadFactory-engineScheduled-Thread-92) [] VM '4aff4193-ba75-481d-92b3-59b62cd8b111'(vm_to_migrate) was unexpectedly detected as 'MigratingTo' on VDS 'f3749f1e-a68d-424f-aa3a-f0ec996df498'(DESTINATION) (expected on 'ea7bae8f-d966-4baa-b8b4-a5522b88ec3a') 2018-06-14 13:14:48,139+02 INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (EE-ManagedThreadFactory-engineScheduled-Thread-92) [] VM '4aff4193-ba75-481d-92b3-59b62cd8b111' is migrating to VDS 'f3749f1e-a68d-424f-aa3a-f0ec996df498'(DESTINATION) ignoring it in the refresh until migration is done 2018-06-14 13:15:03,193+02 INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (EE-ManagedThreadFactory-engineScheduled-Thread-71) [] VM '4aff4193-ba75-481d-92b3-59b62cd8b111'(vm_to_migrate) was unexpectedly detected as 'MigratingTo' on VDS 'f3749f1e-a68d-424f-aa3a-f0ec996df498'(DESTINATION) (expected on 'ea7bae8f-d966-4baa-b8b4-a5522b88ec3a') 2018-06-14 13:15:03,193+02 INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (EE-ManagedThreadFactory-engineScheduled-Thread-71) [] VM '4aff4193-ba75-481d-92b3-59b62cd8b111' is migrating to VDS 'f3749f1e-a68d-424f-aa3a-f0ec996df498'(DESTINATION) ignoring it in the refresh until migration is done 2018-06-14 13:15:18,242+02 INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (EE-ManagedThreadFactory-engineScheduled-Thread-63) [] VM '4aff4193-ba75-481d-92b3-59b62cd8b111'(vm_to_migrate) was unexpectedly detected as 'MigratingTo' on VDS 'f3749f1e-a68d-424f-aa3a-f0ec996df498'(DESTINATION) (expected on 'ea7bae8f-d966-4baa-b8b4-a5522b88ec3a') 2018-06-14 13:15:18,242+02 INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (EE-ManagedThreadFactory-engineScheduled-Thread-63) [] VM '4aff4193-ba75-481d-92b3-59b62cd8b111' is migrating to VDS 'f3749f1e-a68d-424f-aa3a-f0ec996df498'(DESTINATION) ignoring it in the refresh until migration is done 2018-06-14 13:15:33,293+02 INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (EE-ManagedThreadFactory-engineScheduled-Thread-17) [] VM '4aff4193-ba75-481d-92b3-59b62cd8b111'(vm_to_migrate) was unexpectedly detected as 'MigratingTo' on VDS 'f3749f1e-a68d-424f-aa3a-f0ec996df498'(DESTINATION) (expected on 'ea7bae8f-d966-4baa-b8b4-a5522b88ec3a') 2018-06-14 13:15:33,293+02 INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (EE-ManagedThreadFactory-engineScheduled-Thread-17) [] VM '4aff4193-ba75-481d-92b3-59b62cd8b111' is migrating to VDS 'f3749f1e-a68d-424f-aa3a-f0ec996df498'(DESTINATION) ignoring it in the refresh until migration is done 2018-06-14 13:15:45,377+02 INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (EE-ManagedThreadFactory-engineScheduled-Thread-10) [] VM '4aff4193-ba75-481d-92b3-59b62cd8b111'(vm_to_migrate) moved from 'MigratingFrom' --> 'Up' 2018-06-14 13:15:45,377+02 INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (EE-ManagedThreadFactory-engineScheduled-Thread-10) [] Adding VM '4aff4193-ba75-481d-92b3-59b62cd8b111'(vm_to_migrate) to re-run list 2018-06-14 13:15:45,400+02 ERROR [org.ovirt.engine.core.vdsbroker.monitoring.VmsMonitoring] (EE-ManagedThreadFactory-engineScheduled-Thread-10) [] Rerun VM '4aff4193-ba75-481d-92b3-59b62cd8b111'. Called from VDS 'SOURCE' 2018-06-14 13:15:45,451+02 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.MigrateStatusVDSCommand] (EE-ManagedThreadFactory-engine-Thread-247023) [] START, MigrateStatusVDSCommand(HostName = SOURCE, MigrateStatusVDSCommandParameters:{hostId='ea7bae8f-d966-4baa-b8b4-a5522b88ec3a', vmId='4aff4193-ba75-481d-92b3-59b62cd8b111'}), log id: 25f95334 2018-06-14 13:15:45,453+02 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.MigrateStatusVDSCommand] (EE-ManagedThreadFactory-engine-Thread-247023) [] FINISH, MigrateStatusVDSCommand, log id: 25f95334 2018-06-14 13:15:45,478+02 WARN [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engine-Thread-247023) [] EVENT_ID: VM_MIGRATION_TRYING_RERUN(128), Failed to migrate VM vm_to_migrate to Host DESTINATION . Trying to migrate to another Host. 2018-06-14 13:15:45,557+02 INFO [org.ovirt.engine.core.bll.MigrateVmCommand] (EE-ManagedThreadFactory-engine-Thread-247023) [] Running command: MigrateVmCommand internal: true. Entities affected : ID: 4aff4193-ba75-481d-92b3-59b62cd8b111 Type: VMAction group MIGRATE_VM with role type USER 2018-06-14 13:15:45,595+02 INFO [org.ovirt.engine.core.vdsbroker.MigrateVDSCommand] (EE-ManagedThreadFactory-engine-Thread-247023) [] START, MigrateVDSCommand( MigrateVDSCommandParameters:{hostId='ea7bae8f-d966-4baa-b8b4-a5522b88ec3a', vmId='4aff4193-ba75-481d-92b3-59b62cd8b111', srcHost='10.157.8.37', dstVdsId='69ebacd7-ee55-4c52-abf1-437a14d5fb0d', dstHost='10.157.8.42:54321', migrationMethod='ONLINE', tunnelMigration='false', migrationDowntime='0', autoConverge='false', migrateCompressed='false', consoleAddress='null', maxBandwidth='500', enableGuestEvents='false', maxIncomingMigrations='2', maxOutgoingMigrations='2', convergenceSchedule='null', dstQemu='192.168.1.113'}), log id: 736d023f 2018-06-14 13:15:45,595+02 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.MigrateBrokerVDSCommand] (EE-ManagedThreadFactory-engine-Thread-247023) [] START, MigrateBrokerVDSCommand(HostName = SOURCE, MigrateVDSCommandParameters:{hostId='ea7bae8f-d966-4baa-b8b4-a5522b88ec3a', vmId='4aff4193-ba75-481d-92b3-59b62cd8b111', srcHost='10.157.8.37', dstVdsId='69ebacd7-ee55-4c52-abf1-437a14d5fb0d', dstHost='10.157.8.42:54321', migrationMethod='ONLINE', tunnelMigration='false', migrationDowntime='0', autoConverge='false', migrateCompressed='false', consoleAddress='null', maxBandwidth='500', enableGuestEvents='false', maxIncomingMigrations='2', maxOutgoingMigrations='2', convergenceSchedule='null', dstQemu='192.168.1.113'}), log id: 58572c5b 2018-06-14 13:15:45,601+02 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.MigrateBrokerVDSCommand] (EE-ManagedThreadFactory-engine-Thread-247023) [] FINISH, MigrateBrokerVDSCommand, log id: 58572c5b 2018-06-14 13:15:45,604+02 INFO [org.ovirt.engine.core.vdsbroker.MigrateVDSCommand] (EE-ManagedThreadFactory-engine-Thread-247023) [] FINISH, MigrateVDSCommand, return: MigratingFrom, log id: 736d023f

4 7