Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

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:

Libvirtd CPU usage goes to 100% for more than 15 minutes.

Customer tried to get core dump but could not attach gdb to libvirtd as it was not responding during the time of issue.


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

libvirt-0.10.2-18.el6_4.14.x86_64


How reproducible:

Steps to Reproduce:
1.
2.
3.

Actual results: libvirtd CPU usage goes to 100% for more than 15 minutes.


Expected results:


Additional info:

Created attachment 865954 [details]
gdb core of libvirt

libvirt-0.10.2-29.el6.1.x86_64

(In reply to Jaison Raju from comment #9)
> Created attachment 865954 [details]
> gdb core of libvirt
> 
> libvirt-0.10.2-29.el6.1.x86_64

I don't think I can read much from the core file. I mean, a core file is created in a single shot hence it captures only one state that an application is currently in. And this can be completely unrelated state. In order to identify bottleneck I need to get a consecutive states = profile info. The best would be to gather profile data via oprofile which offers insight into whole system, not just a single application. Jaison, can you try to get the profile data?