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.
Bug 2000505 - virtqemud gets segment fault when 'virsh list' after the restart of libvirt services
Summary: virtqemud gets segment fault when 'virsh list' after the restart of libvirt s...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: libvirt
Version: 9.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Tim Wiederhake
QA Contact: zhentang
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-09-02 09:50 UTC by Han Han
Modified: 2022-05-17 13:02 UTC (History)
5 users (show)

Fixed In Version: libvirt-7.7.0-3.el9
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-05-17 12:45:08 UTC
Type: Bug
Target Upstream Version: 7.7.0
Embargoed:

Attachments (Terms of Use)
Full threads backtrace (29.32 KB, text/plain)
2021-09-02 09:50 UTC, Han Han 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-95971 0 None None None 2021-09-02 09:52:12 UTC
Red Hat Product Errata RHBA-2022:2390 0 None None None 2022-05-17 12:45:33 UTC

Description Han Han 2021-09-02 09:50:31 UTC 
Created attachment 1819971 [details]
Full threads backtrace

Description of problem:
As subject

Version-Release number of selected component (if applicable):
libvirt-7.6.0-2.el9.x86_64

How reproducible:
100%

Steps to Reproduce:
# systemctl start libvirtd; systemctl restart virtqemud; virsh list; systemctl restart virtproxyd; virsh list
 Id   Name   State
--------------------

error: failed to connect to the hypervisor
error: no connection driver available for <null>


Actual results:
➜  ~ coredumpctl -1
TIME                          PID UID GID SIG     COREFILE EXE                   SIZE
Thu 2021-09-02 05:46:56 EDT 38453   0   0 SIGSEGV present  /usr/sbin/virtqemud 818.5K

Core was generated by `/usr/sbin/virtqemud --timeout 120'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  ___pthread_mutex_lock (mutex=mutex@entry=0x40) at pthread_mutex_lock.c:76
76        unsigned int type = PTHREAD_MUTEX_TYPE_ELISION (mutex);
[Current thread is 1 (Thread 0x7f42536f8ac0 (LWP 38453))]
(gdb) bt
#0  ___pthread_mutex_lock (mutex=mutex@entry=0x40) at pthread_mutex_lock.c:76
#1  0x00007f4255170659 in virMutexLock (m=m@entry=0x40) at ../src/util/virthread.c:91
#2  0x00007f4255170ef9 in virThreadPoolStop (pool=0x0) at ../src/util/virthreadpool.c:491
#3  0x00007f424e2ed5fd in qemuStateShutdownPrepare () at ../src/qemu/qemu_driver.c:1063
#4  0x00007f425530c490 in virStateShutdownPrepare () at ../src/libvirt.c:691
#5  0x00007f425523615d in virNetDaemonRun (dmn=0x5648808d9020) at ../src/rpc/virnetdaemon.c:863
#6  0x000056487fc7923d in main (argc=<optimized out>, argv=<optimized out>) at ../src/remote/remote_daemon.c:1213


Expected results:
No segment fault

Additional info:
It works well on libvirt-6.0.0-35.module+el8.4.0+10230+7a9b21e4.x86_64
Comment 1 Jaroslav Suchanek 2021-09-06 15:10:15 UTC 
Tim, please triage this one. Thanks.
Comment 2 Tim Wiederhake 2021-09-24 14:26:33 UTC 
This seemed to be a modular daemon issue:

* libvirt-7.6.0-2.el9 (8eaad4cc89): segfault
* libvirt-7.7.0-1.el9 (12c67b3b70): segfault
* libvirt-7.7.0-2.el9 (fe2cbd9a2d): works
* libvirt-7.7.0-3.el9 (fdbfa94e98): works
Comment 4 zhentang 2021-10-14 06:36:58 UTC 
Verified
-------------------------------------------
Tested on Env libvirt-7.8.0-1.el9, works with no error
Comment 7 errata-xmlrpc 2022-05-17 12:45:08 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 (new packages: libvirt), 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/RHBA-2022:2390
Note You need to log in before you can comment on or make changes to this bug.