| |
|
 |
|
 |
|
|
|
| |
|
|
xen-devel
Re: [Xen-devel] [BUG] memory leak in xend
On Thu, 7 Apr 2005, Christopher S. Aker wrote:
> > A workaround for current systems could be a cron job that restarts Xend
> > every few days.
>
> Xend won't restart in my environment. The work-around that's been posted
> does allow
> xend to be restarted, but not quite. It loses the naming of domains (which, I
> suppose is to be expected) but other nasty things happen that make it not a
> reliable
> solution for me.
Note, that this problaby isn't that bad of a problem in the real world. We
have a xen box with 4g and 20 domains(including dom0). 64g ram for dom0(128m
swap). It's been up for 84 days, and python only has 15m in use for xend.
My guess is that as long as you don't do a lot with xm/xend, the memory usage
won't grow.
ps: the above box is running 2 tinderboxes constantly in an instance, and
running a busy mailserver, all over nfsroot. It's been rock solid(except for
nfs issues, which aren't xen related).
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
|
|
| |
|
Home