From mboxrd@z Thu Jan  1 00:00:00 1970
From: Jean Baptiste Favre <xen-devel@jbfavre.org>
Subject: PCI passthrough issue
Date: Wed, 12 Jan 2011 16:38:49 +0100
Message-ID: <4D2DCB09.5010703@jbfavre.org>
Reply-To: xen-devel@lists.xensource.com
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xensource.com>
List-Unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: xen-devel@lists.xensource.com
List-Id: xen-devel@lists.xenproject.org

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.

- 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.

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.