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] setting max memory

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-users] setting max memory
From: Danilo Godec <danilo.godec@xxxxxxxxx>
Date: Thu, 21 Jul 2011 13:37:03 +0200
Delivery-date: Thu, 21 Jul 2011 04:38:11 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4E27E39A.1060500@xxxxxxxxxxx>
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/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <4E25B5EB.3000509@xxxxxxxxx> <4E25B969.8010004@xxxxxxxxxxx> <4E27D7B9.5040904@xxxxxxxxx> <4E27E2A5.3070804@xxxxxxxxxxx> <4E27E39A.1060500@xxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:5.0) Gecko/20110624 Thunderbird/5.0
On 07/21/2011 10:30 AM, Jonathan Tripathy wrote:

On 21/07/2011 09:26, Jonathan Tripathy wrote:


If you are going to be using these DomUs for anything even remotely
serious, then I would strongly advise against dynamically resizing a
Linux environment's available memory. Form personal experience, I can
categorically say that this leads to a very unstable system.

Just my 2 pence

Even without keeping beside the memory-max? I remember Having done it
too but it did not turn the system unstable AFAICT.

Does anybody have similar feelings about playing with meme making Linux
domU unstable?

Not really.

My Xen servers have 32GB of memory. I limit Dom0 memory to 2GB.

I start all my DomU's with 'maxmem=xxxx' (where xxxx is what I consider to be 'enough' in every possible scenario for that particular host). I also use 'mem=xxxxM' kernel parameter for DomU kernels - maybe that's deprecated now but in the past it was required for the DomU kernel to properly allocate memory.


http://wiki.xensource.com/xenwiki/XenBestPractices

Read the section "http://wiki.xensource.com/xenwiki/XenBestPractices";.
Even though that talks about Dom0, the same still applys for DomU as
they run Linux too.

That should be "read section "Why should I dedicate fixed amount of memory for Xen dom0""

To me the ability to dynamically reduce or increase DomU memory is one of the essentials of virtualization. Besides - I've been doing it for about 4-5 years now and wouldn't say I noticed any related stability issues.

IMHO the section of the XenBestPractices you mention it's applicable to Dom0 only (as in you start with huge amount of memory, but eventually end up with just 'a bit' anyway. It's usually a different story with DomU's - I like to start with not-so-much memory and add it when needed.

   D.



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


--
Danilo Godec, sistemska podpora / system administration

Predlog! Obiscite prenovljeno spletno stran www.agenda.si

ODPRTA KODA IN LINUX
STORITVE : POSLOVNE RESITVE : UPRAVLJANJE IT : INFRASTRUKTURA IT : 
IZOBRAZEVANJE : PROGRAMSKA OPREMA

Visit our updated web page at www.agenda.si

OPEN SOURCE AND LINUX
SERVICES : BUSINESS SOLUTIONS : IT MANAGEMENT : IT INFRASTRUCTURE : TRAINING : 
SOFTWARE


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

<Prev in Thread] Current Thread [Next in Thread>