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.

+++ This bug was initially created as a clone of Bug #1203032 +++

This is more a feature request than bug.  As libvirt is working it's just that users would benefit from this support.

Here is some context form the openstack world (which at least some of you are
aware of).  There are at least 2 open bug against openstack (nova) in the area
of block/disk migration.

1) Live migration fails when the instance has a config-drive[1]
   Here openstack(nova) fails because a drive that nova expects to be migrated
   isn't migrated.

2) libvirt live_snapshot periodically explodes on libvirt 1.2.2 in the gate[2]
   Here openstack(nova) fails because a drive that nova expects NOT to be
   migrated is migrated.

To me these are essentially the same bug/issue.  There is no way to communicate with
libvirt the users expectations around block/disk mirgration.


The suggestions from the mailing list are to enhance virDomainMigrate3 to take a list of devices to migrate.

[1] https://bugs.launchpad.net/nova/+bug/1246201
[2] https://bugs.launchpad.net/nova/+bug/1334398

--- Additional comment from Tony Breeds on 2015-03-17 20:31:18 EDT ---

I'm very happy to do this work (so I assigned it to me).

I just need to free up the time.

*** This bug has been marked as a duplicate of bug 1210352 ***