[ovirt-users] Re: Live Migration broken in 4.2.6 under OVS/OVN networking
Yes, after setting "migration_ovs_hook_enabled = false" it works indeed, thanks. Shouldn't the upgrade process that care of resetting this option automatically? Also, after the upgrade no VM can be started before redefining all the network connections - shouldn't the release notes be updated to inform about that? I will post a bug with an explanation of the issues I've encountered, hope this helps. ___ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@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/P6FVI6EPHIQOGCQ6UZLDPONGKNKE6HHZ/
[ovirt-users] Live Migration broken in 4.2.6 under OVS/OVN networking
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+ 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+ 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
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-le...@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/HAQ3PDEUUKSXKED7ET6EKKOV4XYYOLUD/
[ovirt-users] Re: VLAN Trunk interface with OVN provider (ovirt HE 4.2.6.4-1.el7)
Well, I have already two examples taken directly from my cluster: a pair of highly available OpenStack Controllers and a pair of Sophos ASG Security Firewalls rely on the ability to have multiple MAC addresses on the same port. It turns out that virtual MAC addresses are frequently used with HA/clustering protocols, and this is why every virtual network controller should have a way to disable strict MAC address filtering. ___ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@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/6WQ5MGJYPA72KMAM5FH7LFOYF2KTVV62/
[ovirt-users] Re: VLAN Trunk interface with OVN provider (ovirt HE 4.2.6.4-1.el7)
Hi Dominik, thanks for your reply. Of course use cases for VLAN trunks to the guests are not difficult to find, for example when you want to run a virtual router inside the VM, and you don't want to define dozens or hundreds individual VLANs into the router. Anyways, I'll take the time to write a full bug description to try and have this supported. In the meantime I've found another disturbing issue: even when I create a vNIC profile with "no network filter" assigned, the vNIC will only accept incoming network packets with the "correct" destination MAC address, although the VM is also replying to ARP queries for different ones (ARP spoofing, which is needed by many Virtual-IP protocols). What's going on in this case? Is there a "no-mac-spoofing" filter which is applied inadvertently, independent of vNIC profile? Or am I missing something? Do you believe I should post a bug for this issue, too? Thanks again, ___ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@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/UPKTZANZ2YEJDSIJLJTDU2NYBDGTWTOM/
[ovirt-users] VLAN Trunk interface with OVN provider (ovirt HE 4.2.6.4-1.el7)
Hello; I'm having some hard time getting my oVirt cluster back to work, after the last update to 4.2.6. One thing that does not work anymore is VLAN Trunks; before the update, the cluster was running in OVS mode, and I could define logical networks without VLAN tag; then, networks packets got forwarded to the guest as "tagged". Right now version 4.2.6 won't allow me to assign the (OVS) Logical network to the guest NICs anymore, but it insists that I use a vNIC profile from an external provider. First question: Is this expected? Must I really work with externally provided networks only? Anyway, for the vNIC interfaces that only carry untagged traffic, I was able to define an external OVN network, connect it to the corresponding "Data center Network", and everything works as it did before. But the "trick" does not work for "trunk" interfaces that should carry VLAN tagged traffic. So to the second (main) question? How is this to be solved? Is there a way to define a VLAN trunk under OVN? Or is there a way to pickup a Data Center logical network to attach to the vNIC as we did before? Thanks in advance for your help! ___ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@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/P4OCWNPMJ442EJJJ3IC6MQD5G44ID26B/
