From: Peri Hankey <mpah@thegreen.co.uk>
To: James Harper <JamesH@bendigoit.com.au>
Cc: xen-devel@lists.sourceforge.net
Subject: Re: network hang trigger
Date: Wed, 15 Sep 2004 09:38:50 +0100 [thread overview]
Message-ID: <4147FF9A.4060307@thegreen.co.uk> (raw)
In-Reply-To: <AEC6C66638C05B468B556EA548C1A77D3BE070@trantor>
James
I can confirm that your problem occurs in xen-2.0-20040914. In this
example a4.local is the xen0 machine (2.6.8.1-xen0), a30 is one of
several xenU guests on a4 (all 2.6.8.1-xenU). First a simple ping,
which works OK. Then your special poison ping: nasty pause, and possibly
useful messages.
[administrator@a30 administrator]$ ping a4.local
PING a4.local (192.168.0.4) 56(84) bytes of data.
64 bytes from a4.local (192.168.0.4): icmp_seq=1 ttl=64 time=5.72 ms
64 bytes from a4.local (192.168.0.4): icmp_seq=2 ttl=64 time=0.150 ms
--- a4.local ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1010ms
rtt min/avg/max/mdev = 0.150/2.937/5.724/2.787 ms
[administrator@a30 administrator]$ ping -s 1473 a4.local
PING a4.local (192.168.0.4) 1473(1501) bytes of data.
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
ping: sendmsg: No buffer space available
From 192.168.0.4 icmp_seq=1 Frag reassembly time exceeded
1481 bytes from 192.168.0.4: icmp_seq=2 ttl=64 time=28980 ms
1481 bytes from 192.168.0.4: icmp_seq=3 ttl=64 time=27980 ms
1481 bytes from a4.local (192.168.0.4): icmp_seq=4 ttl=64 time=26980 ms
--- a4.local ping statistics ---
11 packets transmitted, 3 received, +1 errors, 72% packet loss, time
29287ms
rtt min/avg/max/mdev = 26980.569/27980.589/28980.612/816.525 ms, pipe 11
I hope that helps.
Peri
James Harper wrote:
>I have found that simply doing a ping with packetsize > 1500 (maybe
>mtu???) causes the network to hang for a short time. This is from xenU
>and xen0 on the same machine.
>
>Can someone else _please_ test this? I am able to make the network hang
>by saying from domU:
>ping -s 1473 <dom0 ip>
>(1473 + 28 byte header = 1501 byte packet)
>
>I'll do more testing tomorrow.
>
>thanks
>
>James
>
>
>-------------------------------------------------------
>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@lists.sourceforge.net
>https://lists.sourceforge.net/lists/listinfo/xen-devel
>
>
>
>
-------------------------------------------------------
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
next prev parent reply other threads:[~2004-09-15 8:38 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-15 7:23 network hang trigger James Harper
2004-09-15 8:38 ` Peri Hankey [this message]
2004-09-15 9:54 ` Keir Fraser
2004-09-15 10:48 ` Chris Andrews
2004-09-15 12:33 ` Keir Fraser
2004-09-15 12:56 ` Chris Andrews
2004-09-15 13:13 ` Keir Fraser
-- strict thread matches above, loose matches on Subject: below --
2004-09-15 8:38 James Harper
2004-09-15 14:43 James Harper
2004-09-15 15:19 ` Keir Fraser
2004-09-15 15:29 Charles Coffing
2004-09-15 21:19 ` Bin Ren
2004-09-15 21:23 Bin Ren
2004-09-15 22:11 Bin Ren
2004-09-16 7:33 ` Keir Fraser
2004-09-15 23:53 James Harper
2004-09-15 23:54 Bin Ren
2004-09-16 0:04 Bin Ren
2004-09-16 0:48 James Harper
2004-09-16 7:24 ` Keir Fraser
2004-09-16 2:32 James Harper
2004-09-16 11:06 Bin Ren
2004-09-16 11:22 Bin Ren
2004-09-16 11:33 Bin Ren
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4147FF9A.4060307@thegreen.co.uk \
--to=mpah@thegreen.co.uk \
--cc=JamesH@bendigoit.com.au \
--cc=xen-devel@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.