14.01.2016 16:16, Daniel P. Berrange пишет:
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
On Thu, Jan 14, 2016 at 04:14:49PM +0300, Maxim Nestratov wrote: based virt
Regards, Daniel Ahh, I see. I should have used the subject as a global context. Anyway, thank you for clarification.
Best, Maxim