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/
Home Products Support Community News


Re: [Xen-devel] PCI passthrough issue

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-devel] PCI passthrough issue
From: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
Date: Wed, 12 Jan 2011 10:43:44 -0500
Delivery-date: Wed, 12 Jan 2011 07:46:10 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4D2DCB09.5010703@xxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <4D2DCB09.5010703@xxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.20 (2009-06-14)
On Wed, Jan 12, 2011 at 04:38:49PM +0100, Jean Baptiste Favre wrote:
> Hello,
> I'm facing a strange issue with network card PCI passthrough on my
> openwrt test domU.
> - With network PCI passthrough, DNS lookup failed for some domains
> (exemple, google.com) but not for other (free.fr my ISP, or my domain
> jbfavre.org). I can ping an IP address without any problem.

Do you have "both" (so PCI passthrough and the Xen network driver)
in the guest? If so, have you tried eliminating the xen network driver
to see if it is just a routing issue?

What does your routing table look like? Your IP table?

> - Starting domU as a "normal" (ie without PCI passthrough), no problem.
> As far as I can say, domU is not the root cause. I really think this is
> related to PCI passsthrough. This seems to be related to packet length.

Then that would imply the MTU is not set right. 
> Did not see anything strange in dom0 logs.
> Is there any incompatibility between 2.6.32 dom0 kernel with Xen 4.0.1
> and 2.6.37 domU kernel ?

> Regards,
> JB
> Dom0: Debian Squeeze
> # uname -a
> Linux remus 2.6.32-5-xen-amd64
> # dpkg -l|grep hyper
> ii  xen-hypervisor-4.0-amd64                           4.0.1-1
> DomU: Openwrt backfire
> # uname -a
> Linux OpenWrt 2.6.37
> # lsmod
> Module                  Size  Used by    Not tainted
> sky2                   35744  0
> All Xen related stuff is integrated into the kernel, not compiled as module.
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel

Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>