Created attachment 328177 [details] screen shot of this problem Description of problem: In virt-manager->hardware->Memory, user could allocate a size of Maximum exceed that total memory on host which should not be I think. Version-Release number of selected component (if applicable): 0.96 How reproducible: Everytime Steps to Reproduce: 1. launch virt-manager 2. go to "Hardware"->Memory, try to increase the size of Maximum allocation exceed the total memory below 3. Actual results: The size could be increased without a stop. Expected results: The size should be only allocated by the size of total memory on host. Additional info:
This is not so clear-cut. KVM allows overcommit of memory, and only pages in RAM when it is actually accessed by a guest. So you can trivially boot a guest with more RAM than is available in the host. It is wise to make sure there is enough SWAP space in the host to cope with this overcommit, but we shouldn't deny overcommit in virt-manager IMHO.
Closing as NOTABUG as per comment #1.