Bug 1978253 - OGA memory report isn't shown in the VM general tab
Summary: OGA memory report isn't shown in the VM general tab
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: Frontend.WebAdmin
Version: 4.4.7.3
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ovirt-4.4.8
: ---
Assignee: Liran Rotenberg
QA Contact: Nisim Simsolo
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-07-01 11:52 UTC by Liran Rotenberg
Modified: 2021-08-19 06:23 UTC (History)
4 users (show)

Fixed In Version: ovirt-engine-4.4.8
Clone Of:
Environment:
Last Closed: 2021-08-19 06:23:02 UTC
oVirt Team: Virt
Embargoed:
pm-rhel: ovirt-4.4+


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 115499 0 master MERGED frontend: fix memory stats for OGA 2021-07-02 06:40:24 UTC

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.


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