Bug 1081424

Summary:	Allocated memory is not updated properly after changing it.
Product:	[Fedora] Fedora	Reporter:	Diego <diego.ml>
Component:	virt-manager	Assignee:	Cole Robinson <crobinso>
Status:	CLOSED ERRATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	20	CC:	berrange, crobinso, virt-maint
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	virt-manager-1.0.1-2.fc20	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-04-25 04:29:34 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Diego 2014-03-27 09:44:01 UTC

Description of problem:
Changing currently allocated memory in virt-manager-1.0.0-6.fc20.noarch changes correctly memory amount assigned to the guest (running "free" in the guest shows the desired memory amount) but is not updated correctly in virt-manager GUI (the "current allocation" displayed value in "Memory" section.

Version-Release number of selected component (if applicable):

Manager on Fedora 20:
virt-manager-1.0.0-6.fc20.noarch
Host on Centos 6.5:
libvirt-0.10.2-29.el6_5.5.x86_64

How reproducible:
The problem is reproducible most of the times, expecially when expanding the amount of memory.

Steps to Reproduce:
1. Change dinamically the amount of RAM currently allocated to a guest.

Actual results:
Host memory changes according to what the user set, but the value display is different from the actual value.

Expected results:
The GUI shows updated and correct values.

Additional info:
Disconnecting and reconnecting to the host hypervisor make the GUI update the values and show correct amount of memory.

Comment 1 Cole Robinson 2014-03-31 16:44:29 UTC

There's a domain memory change event, we just needed to hook an XML refresh into that. Fixed upstream now:

commit adf3545671b155ca37c82bff0ab96d0c038ffee8
Author: Cole Robinson <crobinso>
Date:   Mon Mar 31 12:43:49 2014 -0400

    connection: Hook into domain balloon event (bz 1081424)

Comment 2 Fedora Update System 2014-04-16 21:41:40 UTC

virt-manager-1.0.1-2.fc20 has been submitted as an update for Fedora 20.
https://admin.fedoraproject.org/updates/virt-manager-1.0.1-2.fc20

Comment 3 Fedora Update System 2014-04-18 15:41:36 UTC

Package virt-manager-1.0.1-2.fc20:
* should fix your issue,
* was pushed to the Fedora 20 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing virt-manager-1.0.1-2.fc20'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2014-5335/virt-manager-1.0.1-2.fc20
then log in and leave karma (feedback).

Comment 4 Fedora Update System 2014-04-25 04:29:34 UTC

virt-manager-1.0.1-2.fc20 has been pushed to the Fedora 20 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 5 Diego 2014-04-30 09:23:28 UTC

I confirm the problem is fixed.