Red Hat Bugzilla – Bug 428868
[PATCH] able to set maxmem lower than current mem allocation
Last modified: 2009-12-14 16:03:43 EST
Description of problem:
When editing the gtkspinbutton directly (not using the actual spin buttons) you
are able to apply a max mem value lower than current mem.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. access a shutdown guest in gui
2. access memory tab
3. type a value in the maxmem spinbutton lower than current mem
virt-manager allows this setting to be applied
virt-manager should not set the max mem allocation lower than current mem
allocation. it should at least be set the same as current mem or give the
ability to set at a higher value.
Created attachment 291732 [details]
disallows setting the value of maxmem below current mem value
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux maintenance release. Product Management has requested
further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products. This request is not yet committed for inclusion in an Update
I've applied this patch upstream:
Might be a bit late for 5.2 since this isn't an intrusive bug, though.
This request was previously evaluated by Red Hat Product Management
for inclusion in the current Red Hat Enterprise Linux release, but
Red Hat was unable to resolve it in time. This request will be
reviewed for a future Red Hat Enterprise Linux release.
Okay, this should be fixed in virt-manager-0.5.3-9.el5. Setting bug to MODIFIED.
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.