Bug 2121340 - Overhead Memory consumption calculations are incorrect
Summary: Overhead Memory consumption calculations are incorrect
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Container Native Virtualization (CNV)
Classification: Red Hat
Component: Virtualization
Version: 4.8.0
Hardware: Unspecified
OS: Unspecified
urgent
high
Target Milestone: ---
: 4.10.6
Assignee: ffossemo
QA Contact: Denys Shchedrivyi
URL:
Whiteboard:
Depends On: 2052689
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-08-25 08:01 UTC by Antonio Cardace
Modified: 2022-10-25 14:47 UTC (History)
14 users (show)

Fixed In Version: hco-bundle-registry-container-v4.10.6-30
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 2052689
Environment:
Last Closed: 2022-10-25 14:47:02 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github kubevirt kubevirt pull 7636/ 0 None None None 2022-08-25 08:03:32 UTC
Github kubevirt kubevirt pull 8370 0 None Merged [release-0.49] virt-launcher overhead: bump virtlauncher and virtlogd 2022-08-30 08:58:28 UTC
Github kubevirt kubevirt pull 8557 0 None Merged [release-0.49] Bump virtlogd memory requirement to 18Mi 2022-10-11 10:14:57 UTC
Red Hat Product Errata RHEA-2022:7179 0 None None None 2022-10-25 14:47:11 UTC

Comment 4 Kedar Bidarkar 2022-10-04 14:25:32 UTC 
Looking at comment2 and comment3 , it appears this bug should be in POST state as the PR still needs to get merged.
Comment 5 Denys Shchedrivyi 2022-10-12 17:36:19 UTC 
Verified - all virt processes memory usage below the limits
Comment 11 errata-xmlrpc 2022-10-25 14:47:02 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (OpenShift Virtualization 4.10.6 Images), and where to find the updated
files, follow the link below.

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

https://access.redhat.com/errata/RHEA-2022:7179
Note You need to log in before you can comment on or make changes to this bug.