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

[Xen-users] dom0_mem= major issue

To: <xen-users@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-users] dom0_mem= major issue
From: "Ian Tobin" <itobin@xxxxxxxxxxxxx>
Date: Fri, 14 Oct 2011 10:18:44 +0100
Delivery-date: Fri, 14 Oct 2011 02:20:22 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
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>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcyKUHQ4e/jAJqtPSi6uVnRrjzp9DA==
Thread-topic: dom0_mem= major issue

Hi,

 

I have already mentioned this in another email but no one seems to have the same issue?  Specifying the above line doesn’t seem to have much affect, in fact it makes the system more unstable as it seems that when launching domUs it takes memory from dom0 to the point where it is running at its minimum.  I have tested with various servers and all have the same issue.

 

I read that there was an issue with kernel 3.0 but this problem is happening with 2.6.32.43.  Also once you get to a certain point you can’t launch anymore domUs even though there is lots of RAM free, it complains there is no RAM in dom0. After this dom0 struggles as there is little RAM for it to use.

 

XEN is 4.1.1

Kernel is mixed, 2.6.32.43 – 3.1-rc4

 

To get round this issue I have removed the dom0_mem parameter for now so the memory is available to all domUs and dom0.

 

Has anyone got a solution to this or is it something we just have to deal with now? Seems a big problem to me.

 

Thanks

 

Ian

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
<Prev in Thread] Current Thread [Next in Thread>