On Mon, 24 Sep 2018 14:57:24 -0000 "Davide Butti" <dbutti194@gmail.com> wrote:
Hello; despite many tests and tentative adjustments, I'm currently unable to live migrate VMs on oVirt 4.2.6.
The vdsm.log contains a "failed to migrate" error, that points to an attempt to access a non-existent network port "TestOne". This is in fact the name of the (externally defined) network, and isn't anywhere to be seen as OVS port.
2018-09-24 14:32:57,059+0000 ERROR (migsrc/4c0255b5) [virt.vm] (vmId='4c0255b5-0f52-4da7-ac97-d54d815cd6ab') Cannot get interface MTU on 'TestOne': No such device (migration:290) 2018-09-24 14:32:57,793+0000 ERROR (migsrc/4c0255b5) [virt.vm] (vmId='4c0255b5-0f52-4da7-ac97-d54d815cd6ab') Failed to migrate (migration:455) Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/vdsm/virt/migration.py", line 437, in _regular_run self._startUnderlyingMigration(time.time()) File "/usr/lib/python2.7/site-packages/vdsm/virt/migration.py", line 509, in _startUnderlyingMigration self._perform_with_conv_schedule(duri, muri) File "/usr/lib/python2.7/site-packages/vdsm/virt/migration.py", line 587, in _perform_with_conv_schedule self._perform_migration(duri, muri) File "/usr/lib/python2.7/site-packages/vdsm/virt/migration.py", line 529, in _perform_migration self._migration_flags) File "/usr/lib/python2.7/site-packages/vdsm/virt/virdomain.py", line 98, in f ret = attr(*args, **kwargs) File "/usr/lib/python2.7/site-packages/vdsm/common/libvirtconnection.py", line 130, in wrapper ret = f(*args, **kwargs) File "/usr/lib/python2.7/site-packages/vdsm/common/function.py", line 92, in wrapper return func(inst, *args, **kwargs) File "/usr/lib64/python2.7/site-packages/libvirt.py", line 1746, in migrateToURI3 if ret == -1: raise libvirtError ('virDomainMigrateToURI3() failed', dom=self) libvirtError: Cannot get interface MTU on 'TestOne': No such device
The setup was previously working under OVS, and I have "migration_ovs_hook_enabled = true" under /etc/vdsm/vdsm.conf
Can you please remove the "migration_ovs_hook_enabled = true" from vdsm.conf? If removing this option from vdsm.conf works for you, would you please create a bug for this? - Thanks! In 4.2.6 only OVN networks for VMs in clusters with switch type OVS are allowed. OVN networks does not require migration_ovs_hook_enabled and migration seems to be broken if set.
Do I need to change anything? Is this supposed to work in the first place?
Many thanks for your help, have a nice day _______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to 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/HAQ3PDEUUKSXKE...