From: Taku Izumi Date: Fri, 8 Apr 2011 05:07:27 +0000 (+0900) Subject: maxmem: introduces VIR_DOMAIN_MEM_MAXIMUM flag X-Git-Url: http://xenbits.xensource.com/gitweb?a=commitdiff_plain;h=e3b4ca21b2039e23215eeb0b18097d7edcccc13b;p=libvirt.git maxmem: introduces VIR_DOMAIN_MEM_MAXIMUM flag This patch introduces VIR_DOMAIN_MEM_MAXIMUM flag. Signed-off-by: Taku Izumi --- diff --git a/include/libvirt/libvirt.h.in b/include/libvirt/libvirt.h.in index d7654120d1..04b7fbf2c8 100644 --- a/include/libvirt/libvirt.h.in +++ b/include/libvirt/libvirt.h.in @@ -857,6 +857,7 @@ typedef enum { VIR_DOMAIN_MEM_CURRENT = 0, /* affect current domain state */ VIR_DOMAIN_MEM_LIVE = (1 << 0), /* affect active domain */ VIR_DOMAIN_MEM_CONFIG = (1 << 1), /* affect next boot */ + VIR_DOMAIN_MEM_MAXIMUM = (1 << 2), /* affect Max rather than current */ } virDomainMemoryModFlags; diff --git a/src/libvirt.c b/src/libvirt.c index abde7db80b..4a396955ba 100644 --- a/src/libvirt.c +++ b/src/libvirt.c @@ -2832,6 +2832,8 @@ error: * (that is, @flags is VIR_DOMAIN_MEM_CURRENT), then an inactive domain * modifies persistent setup, while an active domain is hypervisor-dependent * on whether just live or both live and persistent state is changed. + * If VIR_DOMAIN_MEM_MAXIMUM is set, the change affects domain's maximum memory + * size rather than current memory size. * Not all hypervisors can support all flag combinations. * * Returns 0 in case of success, -1 in case of failure.