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] Network drop to domU (netfront: rx->offset: 0, size: 429

To: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Subject: Re: [Xen-devel] Network drop to domU (netfront: rx->offset: 0, size: 4294967295)
From: "PCextreme B.V. - Wido den Hollander" <wido@xxxxxxxxxxxx>
Date: Mon, 25 May 2009 12:02:27 +0200
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Mon, 25 May 2009 03:07:00 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <C6394D3A.6A95%keir.fraser@xxxxxxxxxxxxx>
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: <C6394D3A.6A95%keir.fraser@xxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Hi,

My tests kept running this weekend and it seems it affects ALL the
domU's at the same moment.

For example on May 24 at 13:54 and 16:45 the traffic dropped for about
30 seconds to both domU's i have been monitoring.

My ifconfig on the dom0 shows a lot of TX drops (14663 atm) and a total
of 11047260 packets, that's about 0.1% packetloss over the uptime of the
domU (12 days atm).

The errors didn't change yet.

-  
Met vriendelijke groet,

Wido den Hollander
Hoofd Systeembeheer / CSO
Telefoon Support Nederland: 0900 9633 (45 cpm)
Telefoon Support België: 0900 70312 (45 cpm)
Telefoon Direct: (+31) (0)20 50 60 104
Fax: +31 (0)20 50 60 111
E-mail: support@xxxxxxxxxxxx
Website: http://www.pcextreme.nl
Kennisbank: http://support.pcextreme.nl/
Netwerkstatus: http://nmc.pcextreme.nl


On Wed, 2009-05-20 at 06:01 -0700, Keir Fraser wrote:
> On 20/05/2009 05:50, "PCextreme B.V. - Wido den Hollander"
> <wido@xxxxxxxxxxxx> wrote:
> 
> >> If it's an issue that crops up with many guests then I suppose it's
> > more likely a netback issue, which is a pain.
> > 
> > I already assumed this would be a pain, any way to determine if it is a
> > netback issue? Adding some verbose messages to the kernel?
> 
> The visible effects of the bug start in dom0, when it presents a buffer
> reference (aka a 'grant reference') to Xen as provided to it by domU. Xen
> notes that the grant reference is bogus (the xm dmesg output shows the flag
> field of the grant is zero, which means it's currently unused). Now, does
> that mean domU forgot to initialise the buffer grant, or got out of sync
> somehow, or is the dom0 which has got out of sync? It's rather hard to tell.
> But dom0 is more likely to be affected by scaling to large numbers of
> domains than a domU is. The logic in domU netfront doesn't change, whereas
> dom0 netback has the actual multiplexing job. Hence dom0 is more likely to
> be the culprit.
> 
> If you define DEBUG at the very top of dom0's drivers/xen/netback/netback.c
> you will get more debug output from dom0 kernel when things go wrong. It may
> be not much extra help unfortunately, but extra tracing could be added I
> suppose (the pain being of course that each such change will require a dom0
> reboot or a netback module reload, which itself may require domains to be
> restarted).
> 
>  -- Keir
> 
> 

Attachment: signature.asc
Description: This is a digitally signed message part

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