From: Nivedita Singhvi <niv@us.ibm.com>
To: mukesh agrawal <xen.sourceforge.net@mukesh.agrawals.org>
Cc: xen-devel@lists.sourceforge.net
Subject: Re: (repeatable) cross-domain networking failure
Date: Sat, 15 Jan 2005 13:14:27 -0800 [thread overview]
Message-ID: <41E987B3.3090605@us.ibm.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0501151139210.21950@slash.mukesh.agrawals.org>
mukesh agrawal wrote:
>
> Summary:
>
> After sending some UDP traffic between two xen domains (Domain 0 and
> Domain 1) the networking between the domains fails. This failure is 100%
> repeatable.
I don't have boxes at the moment and can't reproduce till
Monday, but can you show us the output of netstat -uan and
netstat -s on both domains? Is there stuff in the receive
or send queues? And was all the udp traffic going to the
same port? i.e. any successful udp traffic to another
endpoint?
> I then start a UDP server in D0, and a traffic generator in D1. After
> the traffic generator sends its 128-th packet, networking between the
> domains fails. The 128th packet is received successfully by the UDP
> server, but no later traffic arrives in D0. This includes UDP, TCP,
> ICMP, and ARP.
What does ifconfig on dom0 show?
Are there any error messages in /var/log/messages?
> Looking at the interrupt counts in /proc/interrupts, I see that D0 no
> longer receives packets sent by D1. D1, however, does receive packets
> sent by D0. (To be clear, D0->D1 traffic is ICMP ping requests,
> unrelated to the UDP traffic. There is not UDP traffic sent from D0 to D1.)
Is there any other successful traffic from D0 -> D1 (tcp?)
thanks,
Nivedita
-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
next prev parent reply other threads:[~2005-01-15 21:14 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-15 16:40 (repeatable) cross-domain networking failure mukesh agrawal
2005-01-15 17:04 ` Keir Fraser
[not found] ` <e15e04f9050115091893409f1@mail.gmail.com>
2005-01-15 17:26 ` Fwd: " mukesh agrawal
2005-01-15 21:14 ` Nivedita Singhvi [this message]
[not found] ` <e15e04f905011611313312b9f4@mail.gmail.com>
2005-01-16 20:49 ` mukesh agrawal
2005-01-16 21:09 ` Keir Fraser
2005-01-16 21:56 ` mukesh agrawal
-- strict thread matches above, loose matches on Subject: below --
2005-01-20 22:08 Ian Pratt
2005-01-17 23:14 Ian Pratt
2005-01-18 2:06 ` Adam Heath
2005-01-18 11:05 ` Keir Fraser
2005-01-18 11:28 ` Keir Fraser
2005-01-18 16:04 ` Nivedita Singhvi
2005-01-20 19:11 ` Adam Heath
2005-01-19 23:17 ` mukesh agrawal
2005-01-16 22:52 Ian Pratt
2005-01-16 22:57 ` mukesh agrawal
2005-01-15 1:38 mukesh agrawal
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=41E987B3.3090605@us.ibm.com \
--to=niv@us.ibm.com \
--cc=xen-devel@lists.sourceforge.net \
--cc=xen.sourceforge.net@mukesh.agrawals.org \
/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.