From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ted Kaczmarek Subject: network breakage, smoking gun Date: Sat, 15 Oct 2005 11:03:55 -0400 Message-ID: <1129388635.12282.347.camel@pluto.linsolutions.com> Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7BIT Return-path: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: xen-devel List-Id: xen-devel@lists.xenproject.org Reproduced the network breakage problem, easiest way to reproduce is to try a live migration across the xen-br0, but from what I am seeing just bringing domU's up causes it as well. You know its broke when you see peth0: received packet with own address as source address starts filling up the xen console. Tried to set the peth0 hardware address no joy [root@tarkus ~]# ifconfig peth0 hw ether FD:FF:FF:FF:FF:FF SIOCSIFHWADDR: Cannot assign requested address tried fd:ff:ff:ff:ff:ff as well. Gateway | -------------------------- subnet A | | dom0-1 dom0-2 dom0's | | subnet B -xen-br0 ---------------------------------------------------- | | | | | | | | | | | | | 1-1 1-2 1-3 1-4 1-5 1-6 1-7 1-8 1-9 1-10 2-1 2-2 2-3 domU's Ian stated that peth0 should not be end point src or destination of any packets, but I suspect some llc frames may be the cause of this. This has been lurking for a long time, actually thought this was expected behavior :-) The domO's each have three nics, but eth2 is not used at this time. Based upon what I have seen, almost anything will bring this problem on. I always find it because each dom0 has one domU running OpenNMS on it, and they each start reporting the neighbor dom0 xen-br0 ethernet down. It gets really funky, domU's on one dom0 can talk to all domU's, while domu's on the other dom0 can only see local domU's. The d This is the controller on both machines for xen-br0 ######## dom0-1 ######## 00:0c.0 Ethernet controller: Intel Corporation 82541GI/PI Gigabit Ethernet Controller Subsystem: Intel Corporation PRO/1000 MT Desktop Adapter Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66Mhz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- SERR- TAbort- SERR-