Re: [libvirt] Virtio Ballon driver problem

On 12/09/2011 02:39 AM, Pankaj Rawat wrote: Is that in the host or in the guest? Which process? The guest process trying to use memory, or the host qemu process running the guest? Can you show actual transcripts of your testing? Assigning 400MiB current memory to the guest implies that the balloon driver in the guest will prevent the guest from using more than 400MiB, even if the max allocation is higher. The balloon driver in the guest does not have the ability to dynamically request more memory from the host, rather, balloon expansion or contraction is controlled by host actions. On the host, did you use the 'virsh setmem' command (or other language binding to access the virDomainSetMemory API), which is the documented way to have the host request the guest to change the allocation consumed by the guest's balloon driver? The balloon driver only matters in the guest; it is a guest device designed for cooperation with host control. Disclaimers like this are unenforceable on publicly-archived mailing lists; you may want to consider sending mail from a different account that doesn't tack on this legalese. -- Eric Blake eblake(a)redhat.com +1-919-301-3266 Libvirt virtualization library http://libvirt.org