All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick Scharrenberg <pittipatti@web.de>
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: Xen-devel@lists.xensource.com
Subject: Re: xen 3 dom0 eats memory
Date: Wed, 04 Jan 2006 17:39:23 +0100	[thread overview]
Message-ID: <43BBFA3B.8030502@web.de> (raw)
In-Reply-To: <8a5e6e221bc2a6e9b9315f8d568681e7@cl.cam.ac.uk>

Keir Fraser schrieb:
>
> On 4 Jan 2006, at 15:35, Patrick Scharrenberg wrote:
>
>>>>> 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
>>>
>>> What interface do you attach the domU gateway address to?
>>>
>> it's the xen-bridge-interface where I set the domU gateway address.
>
> I can't repro the problem. My setup is that the domU vif is the only
> interface I attach to the bridge (eth0 is not attached). I give the
> bridge address 10.0.0.1, enable IP forwarding, and set up IP
> masquerade on eth0. I set domU IP address to 10.0.02 gw 10.0.0.1 and
> disable transmit checksumming.  I then did a TCP bulk transfer to an
> external host (a few million packets) and observed no memory leak in
> domain 0.
>
Hmm.. thats strange, since I did nothing special.

Here once more what I did, maybe (hopefully) we misunderstood:

eth0 has my internet ip address.

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.

I have the following interfaces in the bridge: peth0, vif0.0, vif1.0

I'm using debian sarge as os. Maybe they set something special in their
networking-scripts?

It is a test-machine, so i can give you the root-pw, if nothing helps.

Patrick

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

  reply	other threads:[~2006-01-04 16:39 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-04 13:43 xen 3 dom0 eats memory Patrick Scharrenberg
2006-01-04 14:35 ` Keir Fraser
2006-01-04 14:47   ` Patrick Scharrenberg
2006-01-04 14:58     ` Keir Fraser
2006-01-04 15:35       ` Patrick Scharrenberg
2006-01-04 15:52         ` Keir Fraser
2006-01-04 16:39           ` Patrick Scharrenberg [this message]
2006-01-04 16:52             ` Keir Fraser
2006-01-06 11:17               ` Patrick Scharrenberg
  -- strict thread matches above, loose matches on Subject: below --
2006-01-04 14:34 Ian Pratt
2006-01-04 16:22 ` Patrick Scharrenberg
2006-01-04 16:43   ` Keir Fraser

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=43BBFA3B.8030502@web.de \
    --to=pittipatti@web.de \
    --cc=Keir.Fraser@cl.cam.ac.uk \
    --cc=Xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.