WARNING - OLD ARCHIVES

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

xen-devel

Re: [Xen-devel] PCI passthrough issue

To: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] PCI passthrough issue
From: Ian Campbell <Ian.Campbell@xxxxxxxxxx>
Date: Wed, 2 Feb 2011 09:27:53 +0000
Delivery-date: Wed, 02 Feb 2011 01:28:40 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4D488355.8010706@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>
Organization: Citrix Systems, Inc.
References: <4D2E28C5.30203@xxxxxxxxxxx> <4D2EE1DE.5070006@xxxxxxxxxxx> <4D2F5009.2090701@xxxxxxxxxxx> <20110113201922.GA20494@xxxxxxxxxxxx> <4D2F6431.8030606@xxxxxxxxxxx> <20110114145350.GB7371@xxxxxxxxxxxx> <4D30DC5A.9080303@xxxxxxxxxxx> <4D340504.7020203@xxxxxxxxxxx> <4D344AF4.80301@xxxxxxxxxxx> <4D3AB003.3040603@xxxxxxxxxxx> <20110127202755.GA4194@xxxxxxxxxxxx> <4D41E7EE.4060502@xxxxxxxxxxx> <4D42E520.9020107@xxxxxxxxxxx> <1296560086.13091.131.camel@xxxxxxxxxxxxxxxxxxxxxx> <4D47F9CF.2040107@xxxxxxxxxxx> <1296566401.13091.171.camel@xxxxxxxxxxxxxxxxxxxxxx> <4D4814CE.5050303@xxxxxxxxxxx> <1296569931.13091.194.camel@xxxxxxxxxxxxxxxxxxxxxx> <4D48234F.2020907@xxxxxxxxxxx> <4D4828D9.6090601@xxxxxxxxxxx> <1296577389.13091.288.camel@xxxxxxxxxxxxxxxxxxxxxx> <4D488355.8010706@xxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
On Tue, 2011-02-01 at 22:04 +0000, Jean Baptiste Favre wrote:
> Le 01/02/2011 17:23, Ian Campbell a écrit :

> > I assume you are not seeing "rx mapping error" in your domU dmesg? Did
> > you post a full guest console log at some point? Comparing the logs for
> > the 256MB, 398MB and 512MB guest RAM case might be useful.
> No sure I've ever posted that logs. But I can redo my tests :)

yes, please do that.

Please can you also collect and post the information from ifconfig and
ethtool -S which I asked for earlier.

Can you confirm that on the domU tcpdump shows no incoming frames at
all, including no corrupted or strange frames. It has been suggested
that the frames could be being received ok but contain garbage (e.g. due
to swiotlb not syncing the memory properly) and hence are not ICMP
Responses but appear as some random frame type.

Please can you use "tcpdump -w" on both the gateway/peer side and the
affected domU to capture a short session while the failing ping is
running and post (or link to if large) the resulting pcap files. On the
peer side you can use "ether host <domU-MAC>" (plus optionally "or ether
broadcast") on the tcpdump command line to limit the capture to just the
one peer and reduce the size of the capture.

Ian.


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

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