Bug 428868 - [PATCH] able to set maxmem lower than current mem allocation
[PATCH] able to set maxmem lower than current mem allocation
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: virt-manager (Show other bugs)
5.3
All Linux
high Severity high
: rc
: ---
Assigned To: Cole Robinson
Virtualization Bugs
:
Depends On:
Blocks: 391501 449772
  Show dependency treegraph
 
Reported: 2008-01-15 14:26 EST by Adam Stokes
Modified: 2009-12-14 16:03 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2009-01-20 16:20:11 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
disallows setting the value of maxmem below current mem value (1.80 KB, patch)
2008-01-15 14:26 EST, Adam Stokes
no flags Details | Diff

  None (edit)
Description Adam Stokes 2008-01-15 14:26:24 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):
virt-manager 0.4.0

How reproducible:
100%

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
  
Actual results:
virt-manager allows this setting to be applied

Expected results:
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.

Additional info:
Comment 1 Adam Stokes 2008-01-15 14:26:24 EST
Created attachment 291732 [details]
disallows setting the value of maxmem below current mem value
Comment 2 RHEL Product and Program Management 2008-01-15 14:36:15 EST
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
release.
Comment 3 Cole Robinson 2008-03-07 11:14:22 EST
I've applied this patch upstream:

http://hg.et.redhat.com/virt/applications/virt-manager--devel?cs=1f1ee216fcef

Might be a bit late for 5.2 since this isn't an intrusive bug, though.
Comment 4 RHEL Product and Program Management 2008-03-11 15:37:01 EDT
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.
Comment 6 RHEL Product and Program Management 2008-06-23 21:32:33 EDT
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
release.
Comment 7 Cole Robinson 2008-09-15 12:06:31 EDT
Okay, this should be fixed in virt-manager-0.5.3-9.el5. Setting bug to MODIFIED.
Comment 10 errata-xmlrpc 2009-01-20 16:20:11 EST
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.

http://rhn.redhat.com/errata/RHBA-2009-0137.html

Note You need to log in before you can comment on or make changes to this bug.