WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] network hang trigger

To: Chris Andrews <chris@xxxxxxxxxx>
Subject: Re: [Xen-devel] network hang trigger
From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Date: Wed, 15 Sep 2004 13:33:23 +0100
Cc: xen-devel@xxxxxxxxxxxxxxxxxxxxx
Delivery-date: Wed, 15 Sep 2004 13:50:02 +0100
Envelope-to: steven.hand@xxxxxxxxxxxx
In-reply-to: Your message of "Wed, 15 Sep 2004 11:48:22 BST." <41481DF6.9080204@xxxxxxxxxx>
List-archive: <http://sourceforge.net/mailarchive/forum.php?forum=xen-devel>
List-help: <mailto:xen-devel-request@lists.sourceforge.net?subject=help>
List-id: List for Xen developers <xen-devel.lists.sourceforge.net>
List-post: <mailto:xen-devel@lists.sourceforge.net>
List-subscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=subscribe>
List-unsubscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=unsubscribe>
Sender: xen-devel-admin@xxxxxxxxxxxxxxxxxxxxx
Do you see this if you ping from DOM1 to an external machine? Or from
an external machine to DOM1?

My suspicion is that this is just some weird interaction between
bridging and local packet dleivery in DOM0. I also can cause lots of
packet loss when pinging DOM1 from DOM0, if I use DOM1's hostname
rather than IP address(!!!). It's very bizarre, and tcpdump tells me
that the ICMP packets come back to DOM0 via the VIF, but it looks like
they then get swallowed somehow within the bridge.

I think that the bridging code is really intended for dedicated bridge
boxes with no local IP interface. So I'm not sure whether the support
for that might not be flaky in some circumstances.

 -- Keir

> I'm seeing this problem:
> 
> 81.187.70.17 is a secondary on DOM0's bridge. The host 'uml18' is DOM1.
> 
> uml18:~# ping -s 2473 81.187.70.17
> PING 81.187.70.17 (81.187.70.17) 2473(2501) bytes of data.
> 2481 bytes from 81.187.70.17: icmp_seq=1 ttl=64 time=0.559 ms
> 
> .. time passes, I hit ^C ..
> 
> ping: sendmsg: No buffer space available
> ping: sendmsg: No buffer space available
> ping: sendmsg: No buffer space available
> ping: sendmsg: No buffer space available
> ping: sendmsg: No buffer space available
> ping: sendmsg: No buffer space available
> 2481 bytes from 81.187.70.17: icmp_seq=6 ttl=64 time=30297 ms
> --- 81.187.70.17 ping statistics ---
> 12 packets transmitted, 2 received, 83% packet loss, time 34627ms
> rtt min/avg/max/mdev = 0.559/15149.215/30297.872/15148.657 ms, pipe 7
> 
> DOM0 has 384M, DOM1 has 64M, MTU 1500 in both.
> 
> Different packet sizes seem to trigger the bug more or less quickly -- I 
> first tried with 2000 byte packets, and didn't see the problem, then I tried 
> 2473, and saw the problem then. Trying 2000 bytes again did then show the 
> problem.
> 
> This is running Xen-2.0 from 4th September -- I can give a more recent 
> version a try, but should I be able to turn on writable pagetables with 
> current code, given I had problems with that option with the code I'm 
> running now?


-------------------------------------------------------
This SF.Net email is sponsored by: thawte's Crypto Challenge Vl
Crack the code and win a Sony DCRHC40 MiniDV Digital Handycam
Camcorder. More prizes in the weekly Lunch Hour Challenge.
Sign up NOW http://ad.doubleclick.net/clk;10740251;10262165;m
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/xen-devel