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.
commit 8d3a807a4acce72a9bce50dd6496c7e320cace39
Author: Peter Krempa <pkrempa>
Date: Fri Jun 3 15:49:01 2022 +0200
qemu: fd: Fix monitor usage of qemuFDPassDirectGetPath
We need to use the 'name' variable and just overwrite it with the FD
number when FDs are passed on the monitor. Otherwise we will read NULL
path if the FD is accessed before being passed on the monitor. The idea
of this helper is to simplify the monitor code so it would be
counterproductive to have other behaviour.
Fixes the following symptom:
$ virsh attach-interface cd network default --model virtio
error: Failed to attach interface
error: internal error: unable to execute QEMU command 'netdev_add': File descriptor named '(null)' has not been found
Fixes: bca9047906fd73fd30f275dd45b64998fbbcf6de
Resolves: https://gitlab.com/libvirt/libvirt/-/issues/318
Resolves: https://bugzilla.redhat.com/show_bug.cgi?id=2092856
Signed-off-by: Peter Krempa <pkrempa>
Reviewed-by: Ján Tomko <jtomko>
v8.4.0-87-g8d3a807a4a
Comment 2yalzhang@redhat.com
2022-06-07 03:38:19 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 (Low: libvirt security, bug fix, and enhancement update), 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/RHSA-2022:8003
Description: Hotplug interface fail with null file descriptor Version-Release number of selected component (if applicable): libvirt-8.4.0-1.el9.x86_64 How reproducible: 100% Steps to Reproduce: 1. start a vm 2. try to hotplug an interface # virsh attach-interface rhel network default --model virtio error: Failed to attach interface error: internal error: unable to execute QEMU command 'netdev_add': File descriptor named '(null)' has not been found 3. check the libvirt log: # cat /var/log/libvirt/libvirtd.log ... 2022-06-02 06:48:00.398+0000: 413311: info : qemuMonitorSend:887 : QEMU_MONITOR_SEND_MSG: mon=0x5597c0ac42f0 msg={"execute":"netdev_add","arguments":{"type":"tap","fd":"(null)","vhost":true,"vhostfd":"(null)","id":"hostnet1"},"id":"libvirt-419"} fd=-1 2022-06-02 06:48:00.398+0000: 414565: info : virObjectRef:402 : OBJECT_REF: obj=0x5597c0ac42f0 2022-06-02 06:48:00.398+0000: 414565: info : qemuMonitorIOWrite:383 : QEMU_MONITOR_IO_WRITE: mon=0x5597c0ac42f0 buf={"execute":"netdev_add","arguments":{"type":"tap","fd":"(null)","vhost":true,"vhostfd":"(null)","id":"hostnet1"},"id":"libvirt-419"} len=134 ret=134 errno=0 2022-06-02 06:48:00.398+0000: 414565: info : virObjectRef:402 : OBJECT_REF: obj=0x5597c0ac42f0 2022-06-02 06:48:00.398+0000: 414565: info : virObjectUnref:380 : OBJECT_UNREF: obj=0x5597c0ac42f0 2022-06-02 06:48:00.398+0000: 414565: info : virObjectUnref:380 : OBJECT_UNREF: obj=0x5597c0ac42f0 2022-06-02 06:48:00.399+0000: 414565: info : virObjectRef:402 : OBJECT_REF: obj=0x5597c0ac42f0 2022-06-02 06:48:00.399+0000: 414565: info : qemuMonitorJSONIOProcessLine:218 : QEMU_MONITOR_RECV_REPLY: mon=0x5597c0ac42f0 reply={"id": "libvirt-419", "error": {"class": "GenericError", "desc": "File descriptor named '(null)' has not been found"}} Actual results: Hotplug interface fail with null file descriptor Expected results: Hotplug interface should succeed Additional info: