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 1053405 - Migrate failed with: unexpected migration status in setup
Summary: Migrate failed with: unexpected migration status in setup
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: libvirt
Version: 7.0
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: Jiri Denemark
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-01-15 08:00 UTC by zhoujunqin
Modified: 2014-06-18 01:02 UTC (History)
5 users (show)

Fixed In Version: libvirt-1.1.1-19.el7
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-06-13 10:53:18 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
The libvirtd's log . (2.75 MB, text/plain)
2014-01-15 08:00 UTC, zhoujunqin 		no flags Details
The qemu log for guest q2 (4.83 KB, text/plain)
2014-01-15 08:01 UTC, zhoujunqin 		no flags Details
View All

Description zhoujunqin 2014-01-15 08:00:34 UTC 
Created attachment 850371 [details]
The libvirtd's log .

Description of problem:
Migrate failed with: unexpected migration status in setup

Version-Release number of selected component (if applicable):
kernel-3.10.0-67.el7.x86_64
libvirt-1.1.1-18.el7.x86_64
qemu-kvm-rhev-1.5.3-36.el7.x86_64
qemu-img-1.5.3-36.el7.x86_64

How reproducible:
100%

Steps to Reproduce:
1.Define and start a domain, specify the physical cpuset using "cpuset" attribute of vcpu element. xml as follows:
...
  <vcpu cpuset='2'>4</vcpu>
...
# virsh dumpxml q2
  <vcpu placement='static' cpuset='2'>4</vcpu>
2. Check vcpu pin info
# virsh vcpuinfo q2
VCPU:           0
CPU:            2
State:          running
CPU time:       6.9s
CPU Affinity:   --y-----

VCPU:           1
CPU:            2
State:          running
CPU time:       1.1s
CPU Affinity:   --y-----

VCPU:           2
CPU:            2
State:          running
CPU time:       1.2s
CPU Affinity:   --y-----

VCPU:           3
CPU:            2
State:          running
CPU time:       1.2s
CPU Affinity:   --y-----
3. Migrate the domain to taget host:
# virsh migrate --live <guestname> qemu+ssh://<target_host_ip>/system
error: internal error: unexpected migration status in setup

4.It works well  on rhel6.5

Actual Results:
Failed to migrate with error:unexpected migration status in setup
Expected results:
Should migrate the guest to the target successfully

Additional info:
Comment 1 zhoujunqin 2014-01-15 08:01:56 UTC 
Created attachment 850372 [details]
The qemu log for guest q2
Comment 5 zhe peng 2014-01-24 03:38:18 UTC 
Can reproduce this with libvirt-1.1.1-18.el7.x86_64.
verify on libvirt-1.1.1-19.el7.x86_64

step:
1.Define and start a domain, specify the physical cpuset using "cpuset" attribute of vcpu element. xml as follows:
...
  <vcpu cpuset='2'>4</vcpu>
...
# virsh dumpxml test
  <vcpu placement='static' cpuset='2'>4</vcpu>
2:# virsh vcpuinfo test
VCPU:           0
CPU:            2
State:          running
CPU time:       8.3s
CPU Affinity:   --y-

VCPU:           1
CPU:            2
State:          running
CPU time:       1.6s
CPU Affinity:   --y-

VCPU:           2
CPU:            2
State:          running
CPU time:       1.4s
CPU Affinity:   --y-

VCPU:           3
CPU:            2
State:          running
CPU time:       2.2s
CPU Affinity:   --y-

3: do migration
# virsh migrate --live test qemu+ssh://$target_IP/system --verbose
Migration: [100 %]
4: check vcpuinfo
# virsh vcpuinfo test
VCPU:           0
CPU:            2
State:          running
CPU time:       0.0s
CPU Affinity:   --y---------

VCPU:           1
CPU:            2
State:          running
CPU time:       0.0s
CPU Affinity:   --y---------

VCPU:           2
CPU:            2
State:          running
CPU Affinity:   --y---------

VCPU:           3
CPU:            2
State:          running
CPU Affinity:   --y---------

verification passed. move to verified.
Comment 6 Ludek Smid 2014-06-13 10:53:18 UTC 
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.
Note You need to log in before you can comment on or make changes to this bug.