From mboxrd@z Thu Jan 1 00:00:00 1970 From: Patrick Scharrenberg Subject: Re: xen 3 dom0 eats memory Date: Fri, 06 Jan 2006 12:17:03 +0100 Message-ID: <43BE51AF.6090205@web.de> References: <43BBD0E8.1010700@web.de> <43BBE011.4080709@web.de> <43BBEB5B.3030308@web.de> <8a5e6e221bc2a6e9b9315f8d568681e7@cl.cam.ac.uk> <43BBFA3B.8030502@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 Hey Keir! >> I used the network-bridge-script to setup the (xen-) networking, >> set up ip 192.168.37.254 on xenbr0. >> Then I startet domU. >> After that I added masquerading to eth0. > > Possibly you can sidestep the whole issue, and end up with faster and > simpler networking setup in dom0, by not using network-bridge and > vif-bridge scripts at all. Instead make your own (much much simpler) > scripts to set up NAT. I found another odd thing regarding the vif-interfaces that my has something to do with the problem mentioned before: I have a high rate of dropped tx packets on all vif's except for vif 0.0. As mentioned before, the config without eth0->peth0 renaming and without vif for dom0 and the rest of the vif's in the bridge works well. Patrick