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:
The libvirtd deamon was killed abnormally when i destroy a domain which was in creating process
Version-Release number of selected component (if applicable):
# rpm -qa|grep libvirt
libvirt-0.9.13-3.el6.x86_64
#rpm -qa|grep kvm
qemu-kvm-0.12.1.2-2.297.el6.x86_64
# uname -r
2.6.32-287.el6.x86_64
How reproducible:
100%
Steps to Reproduce:
1.# ps aux |grep libvirtd
root 30305 0.6 0.1 1029192 13836 ? Sl 19:49 0:00 libvirtd --daemon
root 30615 0.0 0.0 103240 824 pts/3 S+ 19:51 0:00 grep libvirtd
# virsh list --all
Id Name State
----------------------------------------------------
1 rhel6 running
2.[terminal~A]# virsh create --console abc.xml
Domain rhel58 created from abc.xml
Connected to domain rhel58
Escape character is ^]
Memory for crash kernel (0x0 to 0x0) notwithin permissible range
WARNING calibrate_APIC_clock: the APIC timer calibration may be wrong.
PCI: PIIX3: Enabling Passive Release on 0000:00:01.0
Red Hat nash version 5.1.19.6 starting
3.destroy the creating domain at the same time
[terminal~B]# virsh destroy rhel58
error: Failed to destroy domain rhel58
error: End of file while reading data: Input/output error
# virsh list --all
error: Failed to reconnect to the hypervisor
error: no valid connection
error: Failed to connect socket to '/var/run/libvirt/libvirt-sock': Connection refused
# ps aux |grep libvirtd
root 29580 0.0 0.0 103240 820 pts/3 S+ 19:42 0:00 grep libvirtd
Actual results:
the libvirtd deamon was killed abnormally
Expected results:
the libvirtd deamon should run normally and this operation should't affect other guest
Additional info:
abc.xml
Fixed upstream:
commit ba226d334acbc49f6751b430e0c4e00f69eef6bf
Author: Peter Krempa <pkrempa>
Date: Fri Jul 27 14:50:54 2012 +0200
conf: Remove callback from stream when freeing entries in console hash
When a domain has a active console connection and is destroyed the
callback is called on private data that no longer exist causing a
segfault.
Moving to POST as RHEL will pick this up in a rebase.
Test with libvirt-0.10.0-0rc0.el6.x86_64.
Just following the reproduce steps in comment 0, after destroy the creating guest, libvirtd not crash and work well.
# service libvirtd status
libvirtd (pid 31964) is running...
# ps aux |grep libvirtd
root 31964 0.0 0.2 1037280 11072 ? Sl 14:45 0:00 libvirtd --daemon
root 32203 0.0 0.0 103240 848 pts/0 S+ 15:01 0:00 grep libvirtd
So move this bug to verify.
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.
http://rhn.redhat.com/errata/RHSA-2013-0276.html