My engine version is 4.0.5.5-1.el7.centos. The first host is using vdsm-4.18.21-1.el7.centos and the second is using vdsm-4.18.15.3-1.el7.centos. I am trying to migrate guests off host2 to run updates. The Switch type is OVS so are there any pitfalls related to changing that to legacy?

>>> Edward Haas <ehaas@redhat.com> 02/09/17 12:55 AM >>>

Please share the versions you are using (VDSM and Engine).

Have you configured at the cluster level the switch type as OVS? If so, note it is experimental

and we have not supported migration over OVS in early 4.1 versions.

On Wed, Feb 8, 2017 at 10:27 PM, Tyson Landon <tlandon@ontario.k12.or.us> wrote:

I am new to Ovirt and have a test cluster running with 2 hosts. I have errors when live migrating that started after I installed a new NIC in one host. Live migrate was working fine before the changes. The vdsm log shows the errors below depending on if i am migrating from host1 or host2. Running ovs-vsctl list-br shows that the bridge exists. Ip a shows the interface is down. I do not know what a vdsm bridge is for or if the server just needs to restart a service to get things in order again. Have any of you seen this error before and were able to fix it?

HOST 1

libvirtError: Cannot get interface MTU on 'vdsmbr_TK4cSEjh': No such device

HOST 2

libvirtError: Cannot get interface MTU on 'vdsmbr_vqqOTlrR': No such device

HOST 1

ovs-vsctl list-br

vdsmbr_3fDBsCCF
vdsmbr_TK4cSEjh
vdsmbr_VWhs9soF

HOST2

ovs-vsctl list-br

vdsmbr_YBtJDFGg
vdsmbr_qf3gXZdq
vdsmbr_vqqOTlrR

Thanks

Tyson

_______________________________________________
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

_______________________________________________
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users