From: Jean Baptiste Favre <xen-devel@jbfavre.org>
To: xen-devel@lists.xensource.com
Subject: Re: PCI passthrough issue
Date: Wed, 12 Jan 2011 23:18:45 +0100 [thread overview]
Message-ID: <4D2E28C5.30203@jbfavre.org> (raw)
In-Reply-To: <4D2E2149.1010002@jbfavre.org>
Ok, my bad. Screen IS available on OpenWRT.
I've added it to my disk image and now have a tcpdump capture of network
traffic of my DomU
Have the same network capture from my GW so I 'll be able to investigate
deeper.
Let me know if you have specific points you want me to look at.
Regards,
JB
Le 12/01/2011 22:46, Jean Baptiste Favre a écrit :
> Le 12/01/2011 22:40, Konrad Rzeszutek Wilk a écrit :
>> On Wed, Jan 12, 2011 at 09:07:30PM +0100, Jean Baptiste Favre wrote:
>>> Le 12/01/2011 19:32, Konrad Rzeszutek Wilk a écrit :
>>>>>
>>>>> Finally, I think that my setup shall not be responsible for the fact
>>>>> that ping works, small DNS answers are received but not bigger ones
>>>>
>>>> Aah, somehow I missed that fact.
>>>
>>> Seems yes :)
>>>
>>>>> (limit seems to be around 100 bytes).
>>>>
>>>> What does wireshark or tcpdump tell you when you send the larger packets?
>>>
>>> That's one of my problem: nothing special :(
>>>
>>> I can only run tcpdump on my gateway (no SSH available on my OpenWRT
>>> domU and only xm console access is available).
>>
>> You can install (or just compile it statically) tcpdump on your OpenWRT,
>> or just hook it up to a beffier guest..
>
> tcpdump is available on my OpenWRT domU, but I can not perform tcpdump
> and DNS lookup with only console access and AFAIK screen is not
> available on OpenWRT
>
>>> I see DNS requests comming in, I see DNS answers going out.
>>> ARP requests are fine.
>>>
>>> As an example:
>>> dig free.fr works
>>> dig jbfavre.org works
>>> dig amazon.fr works
>>> dig amazon.com works (quite long, but works)
>>> dig google.fr fails
>>> dig google.com fails
>>
>> Fails as in response or fails halfway?
>
> Fails as in:
> # dig google.com
>
> ; <<>> DiG 9.7.2-P3 <<>> google.com
> ;; global options: +cmd
> ;; connection timed out; no servers could be reached
>
>>>
>>> >From another machine in the same LAN, all requests work fine.
>>>
>>> Thought this was due to some ARP restriction setted up by default in
>>> OpenWRT, but in this case, I can not explain why some DNS lookup do work
>>> and some don't.
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
>
next prev parent reply other threads:[~2011-01-12 22:18 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 [this message]
2011-01-13 11:28 ` Jean Baptiste Favre
2011-01-13 19:18 ` Jean Baptiste Favre
2011-01-13 20:19 ` Konrad Rzeszutek Wilk
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=4D2E28C5.30203@jbfavre.org \
--to=xen-devel@jbfavre.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).