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.
Bug 1006663 - qemu-kvm abort after migrate to itself inside incoming host(des host)
Summary: qemu-kvm abort after migrate to itself inside incoming host(des host)
Keywords:
Status: CLOSED DUPLICATE of bug 1086987
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: qemu-kvm
Version: 7.0
Hardware: x86_64
OS: Linux
medium
high
Target Milestone: rc
: ---
Assignee: Juan Quintela
QA Contact: Virtualization Bugs
URL:
Whiteboard:
: 1021840 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-09-11 04:36 UTC by Jun Li
Modified: 2017-06-07 16:41 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-08-13 11:34:14 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Jun Li 2013-09-11 04:36:33 UTC 
Description of problem:
When migrate to itself inside incoming host(des host), qemu-kvm will abort.
But migrate to other host, qemu-kvm will works well.

Version-Release number of selected component (if applicable):
qemu-kvm-1.5.3-2.el7.x86_64
3.10.0-18.el7.x86_64

How reproducible:
100%

Steps to Reproduce:
1.Boot guest with -incoming.
# gdb /usr/libexec/qemu-kvm 
(gdb) run -monitor stdio  -incoming tcp:0:5800
2.Migrate to itself inside incoming host(des host).
(qemu) migrate -d tcp:10.66.6.115:5800
3.check the result.

Actual results:
(qemu) [New Thread 0x7fffdbfff700 (LWP 19184)]
ERROR: invalid runstate transition: 'inmigrate' -> 'finish-migrate'
Program received signal SIGABRT, Aborted.
[Switching to Thread 0x7fffdbfff700 (LWP 19184)]
0x00007ffff32df999 in raise () from /lib64/libc.so.6
(gdb) bt
#0  0x00007ffff32df999 in raise () from /lib64/libc.so.6
#1  0x00007ffff32e10a8 in abort () from /lib64/libc.so.6
#2  0x000055555573017c in runstate_set ()
#3  0x0000555555737ca7 in vm_stop_force_state ()
#4  0x00005555556c6475 in migration_thread ()
#5  0x00007ffff625dde3 in start_thread () from /lib64/libpthread.so.0
#6  0x00007ffff33a00dd in clone () from /lib64/libc.so.6

Expected results:
Give a error message or warning.qemu-kvm will works well.

Additional info:
Comment 2 Hai Huang 2013-12-18 14:31:00 UTC 

*** This bug has been marked as a duplicate of bug 1021840 ***
Comment 3 Jun Li 2013-12-19 01:59:17 UTC 
(In reply to Hai Huang from comment #2)
> 
> *** This bug has been marked as a duplicate of bug 1021840 ***

Hi,

Why this bug is DUPLICATE of 1021840 ? 
This bug is filed before bug 1021840. Maybe bug 1021840 is duplicate of this bug.

Best Regards,

Jun Li
Comment 4 Hai Huang 2013-12-23 18:34:06 UTC 
*** Bug 1021840 has been marked as a duplicate of this bug. ***
Comment 5 Juan Quintela 2014-02-11 22:21:35 UTC 
This is not a regression.
It is doing an abort. but basically it can't do much more.  You are trying to migrate a process to itself, and it is not possible to detect that thing (we don't know where the stream cames from).

What I can agree is that we can fix in 7.1 is to give a wraning if we try to migrate from the state inmigrate.
Comment 8 Juan Quintela 2014-08-13 11:34:14 UTC 
This is worked as expected.

We are trying to migrate to "inside" the same guest that we are migrating.

Fixed with this bugzilla 1086987.

We disabled migrating while we were waiting for an incoming migration, to any place.

*** This bug has been marked as a duplicate of bug 1086987 ***
Comment 9 Jun Li 2014-08-14 02:17:10 UTC 
(In reply to Juan Quintela from comment #8)
> This is worked as expected.
> 
> We are trying to migrate to "inside" the same guest that we are migrating.
> 
> Fixed with this bugzilla 1086987.
> 
> We disabled migrating while we were waiting for an incoming migration, to
> any place.
> 
> *** This bug has been marked as a duplicate of bug 1086987 ***

Hi Juan,

  This bz1006663 is before bz1086987. Maybe bug 1086987 should duplicate of this bug(Just as comment #3 description). When you got a minute, could you give some explanation. Thx.

Best Regards,
Jun Li
Note You need to log in before you can comment on or make changes to this bug.