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.
Created attachment 803188[details]
back trace of libvirtd crashed.
Description
libvirtd crashed when edit "backend model='egd' type='unix'" to guest xml file
Version:
libvirt-1.1.1-6.el7.x86_64
qemu-kvm-1.5.3-3.el7.x86_64
How reproducible:
100%
Steps to Reproduce:
# virsh edit guest
add following xml to guest:
"
<rng model='virtio'>
<rate bytes='1234' period='2000'/>
<backend model='egd' type='unix'>
<source mode='bind' service='1024'/>
<source mode='connect' host='10.66.7.179' service='1024'/>
</backend>
</rng>
"
save then :
error: End of file while reading data: Input/output error
Failed. Try again? [y,n,f,?]:
error: One or more references were leaked after disconnect from the hypervisor
error: Failed to reconnect to the hypervisor
Actual results：
libvirtd crashed.
Expected results:
libvirtd not crash.
This issue is now fixed upstream:
commit 795527548fea79902ea4ce32747e069944cf3e61
Author: Peter Krempa <pkrempa>
Date: Thu Sep 26 08:12:39 2013 +0200
conf: Don't crash on invalid chardev source definition of RNGs and other
Since commit 297c99a5 an invalid source definition XML of a character
device that is used as backend for RNG devices, smartcards and redirdevs
causes crash of the daemon when parsing such a definition.
The device types mentioned above are not a part of a regular character
device but are backends for other types. Thus when parsing such device
NULL is passed as the argument @chr_def. Later when checking the
validity of the definition @chr_def was dereferenced when parsing a UNIX
socket backend with missing path of the socket and crashed the daemon.
Sample offending configuration:
<devices>
...
<rng model='virtio'>
<backend model='egd' type='unix'>
<source mode='bind' service='1024'/>
</backend>
</rng>
</devices>
This request was resolved in Red Hat Enterprise Linux 7.0.
Contact your manager or support representative in case you have further questions about the request.
Created attachment 803188 [details] back trace of libvirtd crashed. Description libvirtd crashed when edit "backend model='egd' type='unix'" to guest xml file Version: libvirt-1.1.1-6.el7.x86_64 qemu-kvm-1.5.3-3.el7.x86_64 How reproducible: 100% Steps to Reproduce: # virsh edit guest add following xml to guest: " <rng model='virtio'> <rate bytes='1234' period='2000'/> <backend model='egd' type='unix'> <source mode='bind' service='1024'/> <source mode='connect' host='10.66.7.179' service='1024'/> </backend> </rng> " save then : error: End of file while reading data: Input/output error Failed. Try again? [y,n,f,?]: error: One or more references were leaked after disconnect from the hypervisor error: Failed to reconnect to the hypervisor Actual results： libvirtd crashed. Expected results: libvirtd not crash.