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 crash when running perl-Sys-Virt api list_node_device_names

Version-Release number of selected component (if applicable):
libvirt-3.9.0-6.el7.x86_64
perl-Sys-Virt-3.9.0-2.el7.x86_64

How reproducible:
100%

Steps to Reproduce:
1. # ps -C libvirtd
   PID TTY          TIME CMD
184874 ?        00:00:00 libvirtd

2. Run below script

my $tck = Sys::Virt::TCK->new();
my $conn = eval { $tck->setup(); };
BAIL_OUT "failed to setup test harness: $@" if $@;
END { $tck->cleanup if $tck; }

my $nodename = $conn->list_node_device_names("net", 3);

3. # libvirt-tck --testdir host-node.t -v --force
host-node.t .. 
libvirt error code: 38, message: End of file while reading data: Input/output error
libvirt error code: 1, message: internal error: client socket is closed
END failed--call queue aborted at host-node.t line 71.
Dubious, test returned 22 (wstat 5632, 0x1600)
No subtests run 

4. ps _C libvirtd
   PID TTY          TIME CMD
185785 ?        00:00:00 libvirtd


Actual results:
See above

Expected results:
libvirtd should not be restarted.
The script should run PASS.

Additional info:
See attachment for gdb log.

Created attachment 1371208 [details]
gdb_libvirtd.log

Upstream patch posted:

https://www.redhat.com/archives/libvir-list/2018-January/msg00003.html

Upstream commit:

commit bbf6573e94528ac8a8867855e6671b48e13f1cd1
Author: Pavel Hrdina <phrdina>
Date:   Tue Jan 2 10:18:17 2018 +0100

    conf: honor maxnames in nodeListDevices API

Test package:
libvirt-3.9.0-7.el7.x86_64
qemu-kvm-rhev-2.10.0-14.el7.x86_64
kernel-3.10.0-768.el7.x86_64

Test:
# libvirt-tck --testdir scripts/host/050-host-node.t -v --force
...
1..185
ok
All tests successful.
Files=1, Tests=185,  1 wallclock secs ( 0.11 usr  0.02 sys +  0.23 cusr  0.02 csys =  0.38 CPU)
Result: PASS


050-host-node.t  include the API.
# Get node device by name
my $nodename = $conn->list_node_device_names("net", 1);
ok_node_device(sub { $conn->get_node_device_by_name($nodename) }, "Get node de...


So verify it.

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, 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-2018:0704