Created attachment 947531 [details] dumpxml Ftest Steps to reproduce: 1. virt-install --connect qemu:///system --name Ftest --memory 1024,maxmemory=4096 --hvm --graphics spice --memballoon model=virtio --os-variant=fedora20 --cpu host-passthrough --vcpus 4 --cdrom /var/lib/libvirt/images/Fedora-Live-Workstation-x86_64-21_Beta-TC3.iso --livecd --disk none 2. try fill memory in guest Actual results: 1G RAM in VM Expected results: all needed RAM in VM (2G for example)
libvirt 1.2.9 from F21
libvirt does not do any automatic adjusting of RAM, if you want to increase the memory available to a guest (up to the configured maximum), you need to do that manually. For example, using virsh setmem command.
Can I reopen this as RFE? This feature would be good.
I think it's a bit out of scope for libvirt. This feature is usually provided by higher-level management apps (e.g., oVirt) that implements some kind of policy which drives the memory adjustments.
(In reply to Jiri Denemark from comment #4) > I think it's a bit out of scope for libvirt. This feature is usually > provided by higher-level management apps (e.g., oVirt) that implements some > kind of policy which drives the memory adjustments. I think adding this feature will really helpful for desktop-users which want to save memory when using VMs. I mean adding base adjusting. User set up: 1024-4096 windows: blnsvr reports that need some memory - libvirt adjusts linux: something reports that need some memory - libvirt adjusts If RAM is not available - no problem. Just don't allocate memory there.
I agree with Jiri that I don't really see this fitting libvirt. Yes it would be nice to have a simple desktop use case option, but I guarantee it would open the flood gates of extra requests for all sorts of configuration tweaks, watermarks, domain whitelists, etc. And even if we did do something like this it would probably be a separate daemon with its own config file anyways since IMO it doesn't really fit the current libvirtd architecture, and at that point you can easily make it a separate project. I know ovirt has http://www.ovirt.org/develop/projects/mom/ which may be standalone for all I know So I don't think this is something that will ever end up in libvirt