Bug 1978253

Summary:	OGA memory report isn't shown in the VM general tab
Product:	[oVirt] ovirt-engine	Reporter:	Liran Rotenberg <lrotenbe>
Component:	Frontend.WebAdmin	Assignee:	Liran Rotenberg <lrotenbe>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Nisim Simsolo <nsimsolo>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	4.4.7.3	CC:	ahadas, bugs, dfodor, nsimsolo
Target Milestone:	ovirt-4.4.8	Flags:	pm-rhel: ovirt-4.4+
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	ovirt-engine-4.4.8	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-08-19 06:23:02 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Virt	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Liran Rotenberg 2021-07-01 11:52:56 UTC

After moving to calculate the memory in the VM general tab to be able using QGA, the previous OGA calculation will remain empty even when we are using OGA (el7 guest and below with OGA).

Comment 1 Nisim Simsolo 2021-08-04 10:20:36 UTC

Verification builds:
ovirt-engine-4.4.8.2-0.11.el8ev
vdsm-4.40.80.3-1.el8ev.x86_64
libvirt-daemon-7.0.0-14.3.module+el8.4.0+11878+84e54169.x86_64
qemu-kvm-5.2.0-16.module+el8.4.0+11923+e8b883e4.4.x86_64

Verification scenario:
1. Run RHEL 7 VM with QGA
 Verify VM general tab displays Guest OS Memory as "Free/Cached+Buffered" with the correct values, 
 for example: 
 Guest OS Memory Free/Cached+Buffered:    3359 / 0 MB
2. Run RHEL 7 with OGA
 Verify VM general tab displays Guest OS Memory as " Free/Cached/Buffered" with the correct values, 
 for example: 
 Guest OS Memory Free/Cached/Buffered:    3335 / 2 / 233 MB

Comment 2 Sandro Bonazzola 2021-08-19 06:23:02 UTC

This bugzilla is included in oVirt 4.4.8 release, published on August 19th 2021.

Since the problem described in this bug report should be resolved in oVirt 4.4.8 release, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.