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

Re: [Xen-devel] [PATCH] Make ballooning work with maxmem > mem (i386 version)


  • To: Glauber de Oliveira Costa <gcosta@xxxxxxxxxx>, Keir Fraser <keir@xxxxxxxxxxxxx>
  • From: Keir Fraser <keir@xxxxxxxxxxxxx>
  • Date: Sat, 11 Nov 2006 00:08:27 +0000
  • Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Fri, 10 Nov 2006 16:08:46 -0800
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: AccFJYLQwRWAcHEYEduMWQANk04WTA==
  • Thread-topic: [Xen-devel] [PATCH] Make ballooning work with maxmem > mem (i386 version)

On 10/11/06 8:27 pm, "Glauber de Oliveira Costa" <gcosta@xxxxxxxxxx> wrote:

>> We have a way to tell the guest its maximum-ever memory allowance, it's just
>> not implemented on the tools and hypervisor side yet. That should be fixed.
> 
> Do we have any specification on how should this look like, and what kind
> of behaviour it should provide?

XENMEM_set_memory_map taking a struct { domain, range_list }. This can
initialise a small array embedded in the domain structure.

Plumb through libxc and python xc.so. Probably make the call from
LinuxImageHandler (or whatever it's called) in image.py.

Done. 

Most of the pain is in the tools plumbing (in particular arg parsing in the
python wrapper).

 -- Keir


_______________________________________________
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®.