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 1320500 - migration from RHEL6.8 to RHEL7.3 host failed with error "Unsupported migration cookie feature persistent"
Summary: migration from RHEL6.8 to RHEL7.3 host failed with error "Unsupported migrati...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: libvirt
Version: 7.3
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Jiri Denemark
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-03-23 10:56 UTC by yafu
Modified: 2016-11-03 18:40 UTC (History)
8 users (show)

Fixed In Version: libvirt-2.0.0-3.el7
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-11-03 18:40:31 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
libvirtd.log (111.04 KB, application/zip)
2016-03-23 10:56 UTC, yafu 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2016:2577 0 normal SHIPPED_LIVE Moderate: libvirt security, bug fix, and enhancement update 2016-11-03 12:07:06 UTC

Description yafu 2016-03-23 10:56:49 UTC 
Created attachment 1139508 [details]
libvirtd.log

Description of problem:
migration from RHEL6.8 to RHEL7.3 host failed with error "Unsupported migration cookie feature persistent"

Version-Release number of selected component (if applicable):
rhel6.8:
libvirt-0.10.2-59.el6.x86_64
qemu-kvm-rhev-0.12.1.2-2.490.el6.x86_64

rhel7.3:
libvirt-1.3.2-1.el7.x86_64
qemu-kvm-rhev-2.3.0-31.el7.x86_64


How reproducible:
100%

steps to reproduce:
1.Do migration from rhel6.8 to rhel7.3:
 #virsh migrate qemu+ssh://10.73.196.125/system --live --verbose
  root.196.125's password:
 Migration: [ 98 %]error: internal error: Unsupported migration cookie feature persistent

2.Check the libvirtd's log on target host:
 #cat /var/log/libvirt/libvirtd.log | grep -i "Unsupported migration cookie feature persistent"
  error : qemuMigrationCookieXMLParse:1250 : internal error: Unsupported migration cookie feature persistent


Actual results:
Migration from RHEL6.8 to RHEL7.3 failed with error "Unsupported migration cookie feature persistent"

Expected results:
Migration from RHEL6.8 to RHEL7.3 should be complete correctly.

Additional info:
1.Migration from rhel6.8 to rhel7.2 can be complete correctly.
2.The "Unsupported migration cookie feature persistent" is a result of a bug on RHEL-6 libvirt, which sends persistent XML in the cookie even though VIR_MIGRATE_PERSIST_DEST was not used. But this is harmless. So maybe the rhel7.3 needs to be compatible with it.
Comment 1 Dr. David Alan Gilbert 2016-06-09 18:02:26 UTC 
Yeh can confirm; just hit the same thing libvirt-0.10.2-60.el6.x86_64->libvirt-1.3.5-1.el7.x86_64

(It does work if I use --persistent on the migrate).

Dave
Comment 2 Jiri Denemark 2016-07-18 13:11:15 UTC 
Patch sent upstream for review: https://www.redhat.com/archives/libvir-list/2016-July/msg00638.html
Comment 3 Jiri Denemark 2016-07-18 15:37:43 UTC 
Fixed upstream by

commit 338f772e923ce07148abe6dcaf3d62b744e7baf5
Refs: v2.0.0-165-g338f772
Author:     Jiri Denemark <jdenemar>
AuthorDate: Mon Jul 18 13:17:28 2016 +0200
Commit:     Jiri Denemark <jdenemar>
CommitDate: Mon Jul 18 17:38:03 2016 +0200

    qemu: Fix migration from old libvirt

    Older libvirt versions send persistent XML in a migration cookie even
    when VIR_MIGRATE_PERSIST_DEST flag is not used, but current libvirt
    properly fails if the cookie contains unexpected flags. Thus migration
    from old libvirt fails with

        internal error: Unsupported migration cookie feature persistent

    unless VIR_MIGRATE_PERSIST_DEST flag is set.

    https://bugzilla.redhat.com/show_bug.cgi?id=1320500

    Signed-off-by: Jiri Denemark <jdenemar>
Comment 6 Fangge Jin 2016-08-09 05:53:39 UTC 
I can reproduce this BZ on build:
RHEL6.8:
libvirt-0.10.2-59.el6.x86_64
qemu-kvm-rhev-0.12.1.2-2.491.el6.x86_64

RHEL7.3:
libvirt-2.0.0-2.el7.x86_64
qemu-kvm-rhev-2.6.0-18.el7.x86_64


Verify this BZ on build:
RHEL7.3:
libvirt-2.0.0-4.el7.x86_64
qemu-kvm-rhev-2.6.0-18.el7.x86_64

Migration succeeds and guest disappears after destroyed on target
Comment 8 errata-xmlrpc 2016-11-03 18:40:31 UTC 
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.

https://rhn.redhat.com/errata/RHSA-2016-2577.html
Note You need to log in before you can comment on or make changes to this bug.