From mboxrd@z Thu Jan 1 00:00:00 1970 From: Patrick Scharrenberg Subject: Re: xen 3 dom0 eats memory Date: Wed, 04 Jan 2006 15:47:45 +0100 Message-ID: <43BBE011.4080709@web.de> References: <43BBD0E8.1010700@web.de> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Keir Fraser Cc: Xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org >> 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 > > What iptables rules do you use to set this up? I used "iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE" for masquerading. > Is the gateway address for domU the net B address interface you add to > the bridge? Yes that right, i forgot to mention that. I have one official address on dom0 eth0 and a privat class B network for the domU's. The address used on the bridge is from this private network and the gateway for the domU's > It's worth trying 'ethtool -K eth0 tx off' in domU to turn off > checksum offload, just in case that is causing problems. Checksum offload is turned off in all domU's. The problem only appears if the pakets are masqueraded. Pinging the gateway-address (the one on the bridge-if) or the dom0-eth0-address causes no memory consumption Patrick