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: Fri, 06 Jan 2006 12:17:03 +0100 [thread overview]
Message-ID: <43BE51AF.6090205@web.de> (raw)
In-Reply-To: <a78ed5315a57007fe767319c37144379@cl.cam.ac.uk>
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
next prev parent reply other threads:[~2006-01-06 11:17 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
2006-01-04 16:52 ` Keir Fraser
2006-01-06 11:17 ` Patrick Scharrenberg [this message]
-- 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=43BE51AF.6090205@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.