On Thu, Jan 14, 2016 at 04:14:49PM +0300, Maxim Nestratov wrote:
14.01.2016 16:01, Daniel P. Berrange пишет:
[snip]
>I agree we should be more explicit about this all in the docs. For
>initial XML config, we should just raise an error if both
><memory> and <currentMemory> are present and have different values,
>or possibly just clamp <currentMemory> to match <memory>.
Hmm. And what if a user wants a VM to be started with inflated balloon and
be
able to deflate it later to add some memory to the VM in runtime?
If libvirt raised an error in case <memory> and <currentMemory> are present
and different a user wouldn't have such a possibility.
Sorry, I should clarify we'd only clamp them together for container
based virt
Regards,
Daniel
--
|:
http://berrange.com -o-
http://www.flickr.com/photos/dberrange/ :|
|:
http://libvirt.org -o-
http://virt-manager.org :|
|:
http://autobuild.org -o-
http://search.cpan.org/~danberr/ :|
|:
http://entangle-photo.org -o-
http://live.gnome.org/gtk-vnc :|