On 03/17/2011 04:56 AM, Daniel P. Berrange wrote:
On Wed, Mar 16, 2011 at 05:58:57PM +0900, Taku Izumi wrote:
>
> When the new maximum memory size becomes less than the current memory size,
> I think it is not the libvirt client but the each driver that decides the behavior
> (reject the operation or shrink the current memory size).
>
ACK
Pushed.
Oh dear - we missed this one for 0.9.0, even though it was acked in
plenty of time. I'm starting to agree with Laine's proposal that having
a mailing-list based helper engine that parses out known pending patch
series would be helpful to avoid losing these in the flurry of a busy inbox.
--
Eric Blake eblake(a)redhat.com +1-801-349-2682
Libvirt virtualization library
http://libvirt.org