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] xen 3 dom0 eats memory - ME TOO

To: "Patrick Scharrenberg" <pittipatti@xxxxxx>, <Xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: RE: [Xen-devel] xen 3 dom0 eats memory - ME TOO
From: "James Harper" <james.harper@xxxxxxxxxxxxxxxx>
Date: Thu, 5 Jan 2006 10:15:46 +1100
Delivery-date: Wed, 04 Jan 2006 23:21:23 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcYRNR8TLAMuZEihSE+d9tZ13P1B+wATkqJw
Thread-topic: [Xen-devel] xen 3 dom0 eats memory - ME TOO
I have a similar situation on two machines running xen3 (xen-3.0-testing
20051228). After a short time (days) dom0 fills up with memory and
eventually kills the watchdog process (which in turn reboots the machine
as I use softdog with the nowayout module option, for exactly this
reason).

I am using bridging, not nat, if that makes any difference.

I'll add free memory to mrtg and see what that uncovers...

James

> -----Original Message-----
> From: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx [mailto:xen-devel-
> bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Patrick Scharrenberg
> Sent: Thursday, 5 January 2006 00:43
> To: Xen-devel@xxxxxxxxxxxxxxxxxxx
> Subject: [Xen-devel] xen 3 dom0 eats memory
> 
> Hi!
> 
> Since my upgrade from xen 2-testing  to xen 3-testing I have the
problem
> that domain0 consumes more and more memory on domU networktraffic.
> It is about 50 bytes per packet that gets lost.
> 
> I reproduced the bug on another machine.
> 
> In normal bridged setup all works fine.
> 
> I changed the setup in the following way:
> - added an ip address to the bridge (in another subnet (B))
> - changed domU ip address to a net B address
> - added masquerading for eth0 in the postrouting-chain in dom0
> 
> After that I pinged a host outside this machine.
> 
> Sending and receiving 100.000 pakets results to a
> dom0-memory-consumption increasement of about 5 MB!
> 
> I have to restart this machine once a day for not running out of
memory.
> 
> What can I do?
> 
> Patrick
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel


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

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