Hello,
I''m new to xen and happily managed to boot into dom0 with default
settings so far.
xend is not started automatically, but as soon as I do, networking is
broken.
Here is what happens
the bridge is started by /etc/xen/scripts/network-bridge .
It gets the two interfaces peth0 (former eth0) and vif0.0, which connects
to eth0 (former veth0).
eth0 has IP address 10.147.160.15 (ok)
the MAC addess has also moved to eth0 (as it should)
Now, when I ping 10.147.160.11 (an existing system in the network), it
does''nt work.
When I do this ping without the xen networking stuff, it works perfectly.
I''ve tracked down the problem by attaching tcpdump to each interface
and
found out that
ARP requests leave the xen system, get into the target machine, which
generates the
ARP response. The ARP response is then sent over the network (one single
switch),
passes the switch (checked using a hub after it), but does not show up
in the
tcpdump for peth0, xenbr0, vif0.0 and eth0. causing ping to fail due to ARP.
I digged in the archive and found that people reported this problem
before, but I was''nt
able to find a solution yet. Any clues ?
Cheers,
-Jens
--
Dipl.-Inform. Jens Fiedler
FhI FOKUS, Competence Center for NGNI
Tel.: +49 30 3463 7270
jens.fiedler@fokus.fraunhofer.de
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
> ARP response. The ARP response is then sent over the network (one single > switch), > passes the switch (checked using a hub after it), but does not show up > in the > Cheers, > -Jens >Jens, it smells like a switch with autolearning. I would try it with a hub _in stead_ of the switch. Sincerely, Jan. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
John Smith wrote:>> ARP response. The ARP response is then sent over the network (one single >> switch), >> passes the switch (checked using a hub after it), but does not show up >> in the >> Cheers, >> -Jens >> > > Jens, > > it smells like a switch with autolearning. > I would try it with a hub _in stead_ of the switch. > > Sincerely, > > Jan.Hi, The ARP response passes the switch, the hub was placed behind the switch in order to check wheter the switch drops the ARP response. It does not, I can see the ARP responses using a 3rd machine (sniffer in the fig.) connected to that hub. So the switch is not the point of failure. <---------------------ARP request---------------- ----------------------ARP response----> +-------+ +-------------+ |target | +--------+ +-----+ | xen machine | |machine|-----| switch |-------| hub |--------|peth0 | +-------| +--------+ +-----+ +-------------+ | +--------+ | sniffer| +--------+ Additionally, when I look at the packet counters using ''ifconfig'', the counters for TX and RX go up, although tcpdump does not show any incoming ARP response on peth0. So the ARP responses are received by the interface, but get dropped before coming to tcpdump or xenbr0. peth0 counters for errors are 0. In tcpdump for peth0 I can see the outgoing ARP requests. The only incoming packets I see are broadcasts from other machines (router adv, other machines'' ARP reqs for different IP addresses, not related to the xen box) Still clueless, -Jens -- Dipl.-Inform. Jens Fiedler FhI FOKUS, Competence Center for NGNI Tel.: +49 30 3463 7270 jens.fiedler@fokus.fraunhofer.de _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Jens Fiedler wrote:> John Smith wrote: > >>> ARP response. The ARP response is then sent over the network (one >>> single >>> switch), >>> passes the switch (checked using a hub after it), but does not show up >>> in the >>> Cheers, >>> -Jens >>> >> >> Jens, >> >> it smells like a switch with autolearning. >> I would try it with a hub _in stead_ of the switch. >> >> Sincerely, >> >> Jan. > > > Hi, > > The ARP response passes the switch, the hub was placed behind the > switch in order to check > wheter the switch drops the ARP response. It does not, I can see the > ARP responses using a > 3rd machine (sniffer in the fig.) connected to that hub. So the switch > is not the point of > failure. > > <---------------------ARP request---------------- > ----------------------ARP response----> > +-------+ +-------------+ > |target | +--------+ +-----+ | xen machine | > |machine|-----| switch |-------| hub |--------|peth0 | > +-------| +--------+ +-----+ +-------------+ > | > +--------+ > | sniffer| > +--------+ > > Additionally, when I look at the packet counters using ''ifconfig'', the > counters for TX and > RX go up, although tcpdump does not show any incoming ARP response on > peth0. So the ARP > responses are received by the interface, but get dropped before coming > to tcpdump or xenbr0. > peth0 counters for errors are 0. In tcpdump for peth0 I can see the > outgoing ARP requests. > The only incoming packets I see are broadcasts from other machines > (router adv, other > machines'' ARP reqs for different IP addresses, not related to the xen > box) > > Still clueless, > -Jens >I "solved" the problem ... The xen machine has 4 ethernet devices: 04:00.0 Ethernet controller: Broadcom Corporation NetXtreme II BCM5708 Gigabit Ethernet (rev 11) 08:00.0 Ethernet controller: Broadcom Corporation NetXtreme II BCM5708 Gigabit Ethernet (rev 11) 0b:00.0 Ethernet controller: Intel Corporation 82571EB Gigabit Ethernet Controller (rev 06) 0b:00.1 Ethernet controller: Intel Corporation 82571EB Gigabit Ethernet Controller (rev 06) The problem vanished when switching from the Broadcom interface (eth0) to an Intel interface (eth2) as the physical device. I''m now running with peth2 on the xenbr0 bridge and it runs fine. I''m not a kernel guru, but seems that the driver for the broadcom nic (bnx2) has some bug. Cheers, -Jens -- Dipl.-Inform. Jens Fiedler FhI FOKUS, Competence Center for NGNI Tel.: +49 30 3463 7270 jens.fiedler@fokus.fraunhofer.de _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Thu, Oct 05, 2006 at 06:22:07PM +0200, Jens Fiedler wrote:> The problem vanished when switching from the Broadcom interface (eth0) > to an Intel interface (eth2) > as the physical device. I''m now running with peth2 on the xenbr0 bridge > and it runs fine. > I''m not a kernel guru, but seems that the driver for the broadcom nic > (bnx2) has some bug.I hit the same issue, and some kind soul on this list pointed me here: http://wiki.ncsa.uiuc.edu/wiki/Dell_PE1950_NIC_Firmware_Workaround Which solved the problem. -- Pete _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Peter McEvoy wrote:>On Thu, Oct 05, 2006 at 06:22:07PM +0200, Jens Fiedler wrote: > >>The problem vanished when switching from the Broadcom interface (eth0) >>to an Intel interface (eth2) >>as the physical device. I''m now running with peth2 on the xenbr0 bridge >>and it runs fine. >>I''m not a kernel guru, but seems that the driver for the broadcom nic >>(bnx2) has some bug. >> > >I hit the same issue, and some kind soul on this list pointed me here: > >http://wiki.ncsa.uiuc.edu/wiki/Dell_PE1950_NIC_Firmware_Workaround > >Which solved the problem. > >Big thx for the link, solved the prob. xen is now working with the broadcom interface. Cheers, -Jens -- Dipl.-Inform. Jens Fiedler FhI FOKUS, Competence Center for NGNI Tel.: +49 30 3463 7270 jens.fiedler@fokus.fraunhofer.de _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users