Red Hat Bugzilla – Bug 503786
virt-manager refuses to increase guest memory until max memory change is first applied
Last modified: 2009-10-07 08:26:54 EDT
This is a UI pain. Open v-m-m and open a system.
Go to details.
Click in the "Maximum Allocation" box
type in a larger number
Click in the "Change Allocation" box
type in the same larger number
click outside the change allocation box, hit tab, really anything, watch your choice of 'Change Allocation" fail.
Ways to make it work include using the 'up/down' arrows next to the 'Maximum Allocation' clicking apply between the changes, things of that nature. But really tabbing or clicking outside the 'Maximum Allocation' box should allow you to make changes in 'Change Allocation'
It's also a bit of a PITA that "Change Allocation" is before "Maximum Allocation" so turning things up requires using 'shift tab' to get back to the first one after you've changed the max. Seems that a max-first interface would be a bit easier to use....
Yeah, this is pretty annoying alright
This bug appears to have been reported against 'rawhide' during the Fedora 11 development cycle.
Changing version to '11'.
More information and reason for this action is here:
Okay, I've tried to improve the situation upstream:
There's basically a role reversal: max mem can't go lower than the current mem value, but current mem can do whatever it wants, and max mem will catch up. Manually entering values should be improved as well.
Moving to POST.
virt-manager-0.7.0-6.fc11 has been submitted as an update for Fedora 11.
virt-manager-0.7.0-6.fc11 has been pushed to the Fedora 11 testing repository. If problems still persist, please make note of it in this bug report.
If you want to test the update, you can install it with
su -c 'yum --enablerepo=updates-testing update virt-manager'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F11/FEDORA-2009-9871
This should be fixed by virt-manager-0.7.0-7.fc11 now in stable. Closing.