Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

For bugs related to Red Hat Enterprise Linux 5 product line. The current stable release is 5.10. For Red Hat Enterprise Linux 6 and above, please visit Red Hat JIRA https://issues.redhat.com/secure/CreateIssue!default.jspa?pid=12332745 to report new issues.

Bug 542522

Summary:	vm -> detail -> hardware -> memory inconsistent
Product:	Red Hat Enterprise Linux 5	Reporter:	Subhendu Ghosh <sghosh>
Component:	virt-manager	Assignee:	Cole Robinson <crobinso>
Status:	CLOSED DUPLICATE	QA Contact:	Virtualization Bugs <virt-bugs>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	5.4	CC:	ghelleks, xen-maint
Target Milestone:	rc
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2009-12-13 19:44:47 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Subhendu Ghosh 2009-11-30 02:03:39 UTC

Description of problem:

Cannot change Current memory allocation, but can change(increase) Max memory allocation. Seems incorrect to be able to increase max memory on a running system.
Inside the system, the memory changes to Max memory are not visible.

Version-Release number of selected component (if applicable):
virt-manager-0.6.1-8.el5
libvirt-0.6.3-20.1.el5_4


How reproducible:
always


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Cole Robinson 2009-12-13 19:44:47 UTC

Is this when changing the memory values of an inactive KVM guest? If so, this is a known issue with libvirt in 5.4. If my guess is wrong, please reopen this bug and attach ~/.virt-manager/virt-manager.log

*** This bug has been marked as a duplicate of bug 508266 ***