WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

Re: [Xen-users] Serious performance problems - is Xen not ready for prod

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-users] Serious performance problems - is Xen not ready for production use?
From: Mark Williamson <mark.williamson@xxxxxxxxxxxx>
Date: Thu, 14 Jul 2005 15:41:46 +0100
Cc: Patrick Hess <posi@xxxxxxx>
Delivery-date: Thu, 14 Jul 2005 16:07:32 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <42D68706.2020708@xxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <42D4D8F4.4040106@xxxxxxx> <200507140013.45001.mark.williamson@xxxxxxxxxxxx> <42D68706.2020708@xxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: KMail/1.8.1
<snip>

> When I had a closer look to the mem line:
> Mem:    257488K total,   255368K used,     2120K free,      128K buffers
>
> ...it looked strange to me. I checked and found my config file for this
> domain looking like this:
>
> ...
> memory = 128
> extra = "mem=268435456"
> ...

Well spotted!

> This was left over from my tries to get the "xm balloon" working. I
> removed the extra line from the config file - and voila, it works... Is
> this config above wrong at all or is the strange behaviour I found
> related to the bugs with balloon feature..?

The config line looks OK at first glance but...  I wonder what units the mem 
parameter expects: if it expects KB then you've just caused it to allocate a 
frame table for an absolutely *huge* physical memory, which would account for 
all the real memory being allocated.

I can't guess any better without going through the code - it should hopefully 
become apparent when someone fixes the ballooning problem (does anyone want 
to volunteer for that, btw?  It'd be useful if someone could post a patch.).

Cheers,
Mark

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users