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] Hard lock of server - saved history from serial consolew

To: "Matt Ayres" <matta@xxxxxxxxxxxx>
Subject: Re: [Xen-devel] Hard lock of server - saved history from serial consolewithin
From: "Christian Limpach" <christian.limpach@xxxxxxxxx>
Date: Sat, 22 Apr 2006 02:29:56 +0100
Cc: Ian Pratt <m+Ian.Pratt@xxxxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Fri, 21 Apr 2006 18:30:16 -0700
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=hPFT+RcPSmPiLEKdZls4iWFu2APanDvSj/VbXg9IPjT3vPTwyLUcXy9QIG2KotWLkmCEZyBimXA8jGKYGEvPrnqkrvVweF+ith26ncK83bTs+iPm5nTKC6ZrOEmdpfI2eP6o5YOHivBXyTfDtv6kkGxjtHn6BkXFggRhhCuGeKs=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <4446C708.4070802@xxxxxxxxxxxx>
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/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <A95E2296287EAD4EB592B5DEEFCE0E9D4BA377@xxxxxxxxxxxxxxxxxxxxxxxxxxx> <4446C708.4070802@xxxxxxxxxxxx>
Reply-to: Christian.Limpach@xxxxxxxxxxxx
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
On 4/20/06, Matt Ayres <matta@xxxxxxxxxxxx> wrote:

Ian Pratt wrote:
>> Yes, an iptable rule for each IP for bandwidth accounting.
>> Also 4 rules in the raw table and 4 rules in the nat table
>> for port redirection.  I don't see how the actual iptables
>> rules could effect the kernel though.
> (!) iptables causes big changes to the way packets pass through the
> kernel.
> In particular, it sounds like you may be using connection tracking for
> NAT. There were lots of changes in this area for 2.6.16, one of which
> broke bridging for large UDP and ICMP datagrams.
> Seeing what iptables modules you have loaded may be interesting. It
> doesn't look much like a xen issue, but I wouldn't totally rule it out.

Most all are compiled in. I do use connection tracking.  I doubt it is a
  Xen problem anymore.  I am upgrading all kernels to to see if
that fixes it. If not I'll have to try 2.6.17-rcX (whatever is the
latest).  I tried applying it and got many rejects so I don't know how
advanced of a kernel hacker I'd have to be to get that working.

You can get 2.6.17-rc2 from:

Re  If you drop the patch into patches/linux-2.6.16, you
should check if it changes any of the files in the sparse tree and/or
any of the original files which we copied (-xen suffix).  You'd then
want to apply the changes to the files in the sparse tree as well.


Xen-devel mailing list

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