[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [Xen-devel] questions about mem-max


  • To: "Li Ge" <lge@xxxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: "Ian Pratt" <m+Ian.Pratt@xxxxxxxxxxxx>
  • Date: Thu, 1 Sep 2005 00:11:18 +0100
  • Delivery-date: Wed, 31 Aug 2005 23:09:15 +0000
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: AcWueR2bixxB0tzeR32LA0bNtu9wNgAB41TA
  • Thread-topic: [Xen-devel] questions about mem-max

> I am trying to understand how the command "xm mem-max" works 
> and write some testcases for it. Here are some confusion I have:
> 
> 1. Can maximum memory be adjusted for a domain at runtime by 
> using 'xm mem-max'? Right now, I see that the max memory 
> change made by 'xm mem-max' is only recorded by xend. There 
> is no change in /proc/xen/balloon and /proc/meminfo.
> 
> 2. If the answer to 1 is no, how to activate the change to 
> the domain? How should I verify it?

max-mem isn't really intended as a user command. It doesn't really
server any purpose in a world with well-behaved VMs. What probably
should happen is that when balloning a domain down in size, xend should
periodically poll the domain's memory usage and set max-mem to be the
current usage plus some small slack. This would prevent a runaway domain
ignoring its memory target and trying to grow its allocation.

Ian 

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


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.