From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: xen-devel@lists.xensource.com
Subject: Re: PCI passthrough issue
Date: Thu, 13 Jan 2011 15:19:22 -0500 [thread overview]
Message-ID: <20110113201922.GA20494@dumpdata.com> (raw)
In-Reply-To: <4D2F5009.2090701@jbfavre.org>
On Thu, Jan 13, 2011 at 08:18:33PM +0100, Jean Baptiste Favre wrote:
> Hello,
> My dom0 is back and I performed some more tests.
>
> I told in my first mail that ping works. Indeed it works, but not always:
> # ping -c2 10.0.0.1
> PING 10.0.0.1 (10.0.0.1): 56 data bytes
> 64 bytes from 10.0.0.1: seq=0 ttl=64 time=0.846 ms
> 64 bytes from 10.0.0.1: seq=1 ttl=64 time=0.824 ms
>
> --- 10.0.0.1 ping statistics ---
> 2 packets transmitted, 2 packets received, 0% packet loss
> round-trip min/avg/max = 0.824/0.835/0.846 ms
> # ping -c2 -s60 10.0.0.1
> PING 10.0.0.1 (10.0.0.1): 60 data bytes
> 68 bytes from 10.0.0.1: seq=0 ttl=64 time=0.819 ms
> 68 bytes from 10.0.0.1: seq=1 ttl=64 time=0.807 ms
>
> --- 10.0.0.1 ping statistics ---
> 2 packets transmitted, 2 packets received, 0% packet loss
> round-trip min/avg/max = 0.807/0.813/0.819 ms
>
> Increasing packet size is ok until this one:
> # ping -c2 -s85 10.0.0.1
> PING 10.0.0.1 (10.0.0.1): 85 data bytes
> 93 bytes from 10.0.0.1: seq=0 ttl=64 time=0.823 ms
> 93 bytes from 10.0.0.1: seq=1 ttl=64 time=0.816 ms
>
> --- 10.0.0.1 ping statistics ---
> 2 packets transmitted, 2 packets received, 0% packet loss
> round-trip min/avg/max = 0.816/0.819/0.823 ms
> root@OpenWrt:/# ping -c2 -s86 10.0.0.1
> PING 10.0.0.1 (10.0.0.1): 86 data bytes
>
> --- 10.0.0.1 ping statistics ---
> 2 packets transmitted, 0 packets received, 100% packet loss
>
> As you see, packet size seems to be limited in a way. From another
> machine on the same LAN I can do ping -s1500 without any problem.
One thing that I just thought (which I keep on forgetting to do).
You did set 'iommu=soft' in your Linux guest, right?
>
> So I think I hit a bug. Either it's Xen related, or Debian (through
> debian kernel version). Now the question is: how can I determine which
> part is responsible ?
What does tcpdump tell you when you try to send it at -s86?
next prev parent reply other threads:[~2011-01-13 20:19 UTC|newest]
Thread overview: 73+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-12 15:38 PCI passthrough issue Jean Baptiste Favre
2011-01-12 15:43 ` Konrad Rzeszutek Wilk
2011-01-12 15:53 ` Jean Baptiste Favre
2011-01-12 16:09 ` Jean Baptiste Favre
2011-01-12 16:36 ` Konrad Rzeszutek Wilk
2011-01-12 16:56 ` Jean Baptiste Favre
2011-01-12 17:26 ` Konrad Rzeszutek Wilk
2011-01-12 17:44 ` Jean Baptiste Favre
2011-01-12 18:32 ` Konrad Rzeszutek Wilk
2011-01-12 20:07 ` Jean Baptiste Favre
2011-01-12 21:40 ` Konrad Rzeszutek Wilk
2011-01-12 21:46 ` Jean Baptiste Favre
2011-01-12 22:18 ` Jean Baptiste Favre
2011-01-13 11:28 ` Jean Baptiste Favre
2011-01-13 19:18 ` Jean Baptiste Favre
2011-01-13 20:19 ` Konrad Rzeszutek Wilk [this message]
2011-01-13 20:44 ` Jean Baptiste Favre
2011-01-14 14:53 ` Konrad Rzeszutek Wilk
2011-01-14 23:29 ` Jean Baptiste Favre
2011-01-17 8:59 ` Jean Baptiste Favre
2011-01-17 13:58 ` Jean Baptiste Favre
2011-01-22 10:22 ` Jean Baptiste Favre
2011-01-27 20:27 ` Konrad Rzeszutek Wilk
2011-01-27 21:47 ` Jean Baptiste Favre
2011-01-28 15:47 ` Jean Baptiste Favre
2011-02-01 11:34 ` Ian Campbell
2011-02-01 12:17 ` Jean Baptiste Favre
2011-02-01 13:20 ` Ian Campbell
2011-02-01 14:12 ` Jean Baptiste Favre
2011-02-01 14:18 ` Ian Campbell
2011-02-01 15:14 ` Jean Baptiste Favre
2011-02-01 15:38 ` Jean Baptiste Favre
2011-02-01 16:23 ` Ian Campbell
2011-02-01 19:37 ` Konrad Rzeszutek Wilk
2011-02-01 22:06 ` Jean Baptiste Favre
2011-02-02 9:12 ` Ian Campbell
2011-02-01 23:01 ` Jean Baptiste Favre
2011-02-02 9:44 ` Ian Campbell
2011-02-02 15:38 ` Konrad Rzeszutek Wilk
2011-02-02 15:55 ` Ian Campbell
2011-02-02 15:56 ` Jean Baptiste Favre
2011-02-01 22:04 ` Jean Baptiste Favre
2011-02-02 9:27 ` Ian Campbell
2011-02-02 10:24 ` Jean Baptiste Favre
2011-02-02 10:59 ` Ian Campbell
2011-02-02 11:33 ` Jean Baptiste Favre
2011-02-02 17:42 ` Konrad Rzeszutek Wilk
2011-02-04 8:43 ` Jean Baptiste Favre
2011-02-04 8:53 ` Ian Campbell
2011-02-04 8:54 ` Jean Baptiste Favre
2011-02-04 10:12 ` Jean Baptiste Favre
2011-02-04 11:04 ` Ian Campbell
2011-02-04 11:25 ` Jean Baptiste Favre
2011-02-04 11:28 ` Ian Campbell
2011-02-04 13:15 ` Jean Baptiste Favre
2011-02-04 13:50 ` Ian Campbell
2011-02-04 14:01 ` Jean Baptiste Favre
2011-02-09 9:59 ` Jean Baptiste Favre
2011-02-18 21:14 ` Jean Baptiste Favre
2011-02-25 14:40 ` Konrad Rzeszutek Wilk
2011-02-28 10:00 ` Jean Baptiste Favre
2011-02-28 12:18 ` Jean Baptiste Favre
2011-02-28 15:01 ` Konrad Rzeszutek Wilk
2011-02-28 15:17 ` Jean Baptiste Favre
[not found] ` <4D6CB851.40103@jbfavre.org>
2011-03-03 22:12 ` Konrad Rzeszutek Wilk
2011-03-03 22:47 ` Jean Baptiste Favre
2011-03-03 22:58 ` Konrad Rzeszutek Wilk
2011-03-04 7:25 ` Jean Baptiste Favre
2011-03-16 3:14 ` Konrad Rzeszutek Wilk
2011-03-25 13:06 ` Jean Baptiste Favre
2011-02-01 15:38 ` Ian Campbell
2011-02-01 16:16 ` Jean Baptiste Favre
2011-01-12 21:44 ` Jean Baptiste Favre
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=20110113201922.GA20494@dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=xen-devel@lists.xensource.com \
/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.