Red Hat Bugzilla – Bug 428867
[PATCH] unable to set current / max memory allocation simultaneously
Last modified: 2010-10-22 17:46:02 EDT
Description of problem:
When attempting to set both gtkspinbuttons to a max mem and current mem of the
same value it fails due to a conditional in domain.py where it thinks current
mem is greater than max mem value.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Access details of a shutdown domain through gui
2. Access memory tab and set both current and max memory to same value
3. Attempt to apply
Current mem is set less than max mem
Current mem set to same value as max mem
Created attachment 291731 [details]
allow simultaneous values
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
Hi Adam, I committed this fix upstream.
It's too late for anything non-critical for 5.2, but this could definitely be in
5.3. Thanks for the patch!
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.