Re: [libvirt] SetMaxMemory vs. SetMemory

2009-05-24 Thread Daniel P. Berrange
On Fri, May 22, 2009 at 02:27:23PM +0200, Matthias Bolte wrote: > 2009/5/22 Daniel P. Berrange : > > Actually QEMU, KVM, Xen PV, Xen FV all  follow the same model, providing > > you have the balloon driver available in the guest. 'maxmem', confusingly > > calling in the XML sets the maximum possib

Re: [libvirt] SetMaxMemory vs. SetMemory

2009-05-22 Thread Matthias Bolte
2009/5/22 Daniel P. Berrange : > Actually QEMU, KVM, Xen PV, Xen FV all  follow the same model, providing > you have the balloon driver available in the guest. 'maxmem', confusingly > calling in the XML sets the maximum possible memory  for the > guest, as exposed in e820 maps. When the guest runs

Re: [libvirt] SetMaxMemory vs. SetMemory

2009-05-22 Thread Daniel P. Berrange
On Thu, May 21, 2009 at 08:37:18PM +0200, Chris Lalancette wrote: > Matthias Bolte wrote: > > Hello, > > > > I just took a look at the driver functions for SetMaxMemory and > > SetMemory, as they are not implemented yet for the ESX driver and > > Daniel Veillard was a bit surprised that they are m

Re: [libvirt] SetMaxMemory vs. SetMemory

2009-05-22 Thread Daniel Veillard
On Thu, May 21, 2009 at 10:39:03PM +0200, Matthias Bolte wrote: > 2009/5/21 Chris Lalancette : > > Well, this is because of a peculiarity with Xen PV domains.  In Xen PV > > guests, > > you specify a "maxmem" and a "memory" parameter in the configuration file.   > > The > > "maxmem" parameter is p

Re: [libvirt] SetMaxMemory vs. SetMemory

2009-05-21 Thread Matthias Bolte
2009/5/21 Chris Lalancette : > Well, this is because of a peculiarity with Xen PV domains.  In Xen PV guests, > you specify a "maxmem" and a "memory" parameter in the configuration file.   > The > "maxmem" parameter is presented to the guest as the end of the e820 map, hence > the end of real memor

Re: [libvirt] SetMaxMemory vs. SetMemory

2009-05-21 Thread Chris Lalancette
Matthias Bolte wrote: > Hello, > > I just took a look at the driver functions for SetMaxMemory and > SetMemory, as they are not implemented yet for the ESX driver and > Daniel Veillard was a bit surprised that they are missing, as he > expects them to be simple to implement. The problem is that I'

[libvirt] SetMaxMemory vs. SetMemory

2009-05-21 Thread Matthias Bolte
Hello, I just took a look at the driver functions for SetMaxMemory and SetMemory, as they are not implemented yet for the ESX driver and Daniel Veillard was a bit surprised that they are missing, as he expects them to be simple to implement. The problem is that I'm not sure how the memory model of