This is a multi-part message in MIME format. --------------2363491D1BDE9DA861A526B0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Hello. I am facing a pretty bizzare problem in two of my Nodes running oVirt. A given VM running a few hundred Mbps of traffic simply stops passing traffic and only recovers after a reboot. Checking the bridge with 'brctl showmacs BRIDGE' I see the VM's MAC address missing during this event. It seems the bridge simply unlearn the VM's mac address which only returns when the VM is rebooted. This problems happened in two different Nodes running in different hardware, in different datacenter, in different network architecture, different switch vendors and different bonding modes. The main differences these Nodes have compared to others I have and which don't show this problem are: - The CentOS 7 installed is a Minimal installation instead of oVirt-NG - The Kernel used is 4.12 (elrepo) instead of the default 3.10 - The ovirtmgmt network is used also for the Virtual Machine showing this problem. Has anyone have any idea if it may have anything to do with oVirt (any filters) or any of the components different from a oVirt-NG installation ? Thanks Fernando --------------2363491D1BDE9DA861A526B0 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 8bit <html> <head> <meta http-equiv="content-type" content="text/html; charset=utf-8"> </head> <body bgcolor="#FFFFFF" text="#000000"> <font face="arial, helvetica, sans-serif">Hello.<br> <br> I am facing a pretty bizzare problem in two of my Nodes running oVirt. A given VM running a few hundred Mbps of traffic simply stops passing traffic and only recovers after a reboot. Checking the bridge with 'brctl showmacs BRIDGE' I see the VM's MAC address missing during this event.<br> <br> It seems the bridge simply unlearn the VM's mac address which only returns when the VM is rebooted.<br> This problems happened in two different Nodes running in different hardware, in different datacenter, in different network architecture, different switch vendors and different bonding modes.<br> <br> The main differences these Nodes have compared to others I have and which don't show this problem are:<br> - The CentOS 7 installed is a Minimal installation instead of oVirt-NG<br> - The Kernel used is 4.12 (elrepo) instead of the default 3.10<br> - The ovirtmgmt network is used also for the Virtual Machine showing this problem.<br> <br> Has anyone have any idea if it may have anything to do with oVirt (any filters) or any of the components different from a oVirt-NG installation ?<br> <br> Thanks<br> Fernando<br> </font> </body> </html> --------------2363491D1BDE9DA861A526B0--