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
2013-10-11 15:10:26 UTC
Description of problem:
During migration, if qemu on the destination dies quickly, libvirtd crashes too. That is, if qemu happens to reply on the monitor with QMP greeting, but dies immediately after, libvirtd crashes.
Version-Release number of selected component (if applicable):
libvirt-1.1.1-8.el7
How reproducible:
100% (with patched qemu)
Steps to Reproduce:
1. Apply this patch to qemu to make it die at the correct place:
diff --git a/monitor.c b/monitor.c
index b096c7f..9e0777f 100644
--- a/monitor.c
+++ b/monitor.c
@@ -676,6 +676,7 @@ static int do_qmp_capabilities(Monitor *mon, const QDict *params,
mon->mc->command_mode = 1;
}
+ abort();
return 0;
}
2. Install the qemu on destination
3. Start a migration onto destination
4. Observe libvirtd segfault
Actual results:
libvirtd segfaults
Expected results:
libvirtd doesn't segfault
Additional info:
I can reproduce this with build:
libvirt-1.1.1-8.el7
verify with :
libvirt-1.1.1-9.el7
step:
1: build a qemu-kvm pkg with patch on destination
2: Start a migration onto destination
# virsh migrate rhel6 --live qemu+ssh://10.66.106.25/system --verbose --unsafe
root.106.25's password:
error: Unable to read from monitor: Connection reset by peer
migration failed.
3: check libvirtd both on source and destination,all active,no segfault occured.
verification passed. move to verified.
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.
Description of problem: During migration, if qemu on the destination dies quickly, libvirtd crashes too. That is, if qemu happens to reply on the monitor with QMP greeting, but dies immediately after, libvirtd crashes. Version-Release number of selected component (if applicable): libvirt-1.1.1-8.el7 How reproducible: 100% (with patched qemu) Steps to Reproduce: 1. Apply this patch to qemu to make it die at the correct place: diff --git a/monitor.c b/monitor.c index b096c7f..9e0777f 100644 --- a/monitor.c +++ b/monitor.c @@ -676,6 +676,7 @@ static int do_qmp_capabilities(Monitor *mon, const QDict *params, mon->mc->command_mode = 1; } + abort(); return 0; } 2. Install the qemu on destination 3. Start a migration onto destination 4. Observe libvirtd segfault Actual results: libvirtd segfaults Expected results: libvirtd doesn't segfault Additional info: