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.
DescriptionMichal Privoznik
2011-09-29 15:03:10 UTC
Description of problem:
If there is an incoming migration and user run virsh dumpxml on incoming domain, but the migration fails, the daemon will then either block indefinitely or crash. This is because dumpxml tries to lock monitor, which gets free()'d meanwhile.
Version-Release number of selected component (if applicable):
libvirt-0.9.4-14.el6
How reproducible:
100%
Steps to Reproduce:
1. start migration
2. on destination run 'virsh dumpxml <domain>'
3. observe segfault or hangup
Actual results:
The daemon crashes
Expected results:
The daemon will not crash and virsh prints something useful
Additional info:
verify pass on
libvirt-0.9.4-16.el6.x86_64
kernel-2.6.32-206.el6.x86_64
qemu-kvm-0.12.1.2-2.195.el6.x86_64
steps:
1. Prepare 2 hosts and prepare a nfs which is mounted on both hosts, and setting the virt_use_nfs boolean on both sides
# setsebool virt_use_nfs 1
and close the iptable on both sides
# iptables -F
2. Start a guest located on nfs
3. Ensure two hosts have no FQDN.
on hostA: # hostname
test1
on hostB: # hostname
test2
4. Ensure /etc/hosts have no domain name resolve on two hosts
# cat /etc/hosts
127.0.0.1 localhost localhost.localdomain localhost4 loclhost4.localdomain4 ::1 localhost localhost.localdomain localhost6 localhost6.localdomain6
5. On destination host, do
# while true; do virsh dumpxml guest; done
6. On source host, do migration
# virsh migrate --live guest qemu+ssh://{dest ip}/system
Migration will fail with error like
error: Unable to resolve address 'dhcp-4.196' service '49153': Name or service not known
7. Check the libvirtd status on destination host
# service libvirtd status
libvirtd still running
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/RHBA-2011-1513.html