RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:

We're experiencing a memory leak in CNV 4.11 that was not present in CNV 4.10. This is occuring in our virt-launcher container at a rate of about 1 to 1.5MB per day.

During our investigation of this we used memleak from bcc-tools. We can see anonymous memory being allocated via cgo, but it lacks a stack trace so we were unable to pinpoint where in the code this allocation is occurring.

Libvirt is the only part of the virt-launcher code that uses cgo, so we suspect this might be the source of the issue.

The leak started appearing after commit https://github.com/kubevirt/kubevirt/commit/447a9487a2bad3513e6f3ffe75ce253d51178981 where we started requesting dirty rate migration metrics from libvirt.

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


How reproducible:

100%

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Stu, Michal found and fixed the issue in the libvirt-go bindings, see merge https://gitlab.com/libvirt/libvirt-go-module/-/merge_requests/33

There is nothing to be fixed in the libvirt, thus this bug is not necessary. I would move it back to CNV product/Virtualization component, but it seems that bug 2090350 should be used tracking the change. Agree? Then I would close this one as notabug. Okay?

@jsuchane I've adjusted the title and description to track this correctly since the bug was in libvirt-go.

Anyway, I confirm that the bug is now fixed and CNV has already picked up the change, thank you.