On Mon, Nov 4, 2019 at 1:46 PM <ccesario@blueit.com.br> wrote:
Hi Edward,
I thought that was it. I remembered some experience I had with a test install that recommended turning the network filter off.
You probably already did this, but when you turn off filtering or make other changes to the logical network like MTU size you must completely shutdown the attached VMs and restart them Yes, I already did it, but no success :(
from oVIrt engine to pickup the change for their network interface.
Restarting networking in a VM from within its OS won't pick up the logical network change at the necessary KVM/qemu/libvirt levels.
There should a way to verify the various virtual interfaces don't have any filtering configured or enabled,
On Sun, Nov 3, 2019 at 11:16 AM <ccesario(a)blueit.com.br> wrote:
Have you other suggestion!? because I dont have more idea :/
Hello, can you see the traffic on the tap e.g. vnet0 device that is attached to the VM? Traffic filtering from libvirt is stored in ebtables. Can you take a look into them and see if there is any suspicious rule? (ebtables -L) Maybe track the packet drop here if your VM is sending DHCP requests. If everything there seems alright. I would suggest going through the chain and check the bridge interface if the DHCP packets are going through it. Hopefully this helps. Regards, Ales
Best regards Carlos _______________________________________________ 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/LW2N75GERKDMMX...
-- Ales Musil Associate Software Engineer - RHV Network Red Hat EMEA <https://www.redhat.com> amusil@redhat.com IM: amusil <https://red.ht/sig>