Description of problem: When a VM has both a local boot disk and a remote volume attached, a blockcopy live migration will attempt to blockcopy the remote volume as well as the local disk. This is likely to cause problems as the remote volume will have the same source and destination. For context, please see the thread leading up to this: http://lists.openstack.org/pipermail/openstack-dev/2015-March/059355.html Version-Release number of selected component (if applicable): libvirtd (libvirt) 1.2.8 How reproducible: 100%
To be explicit, what we need is a way to specify exactly which list of disks need to be block-copied during migration. ie to replace the (bogus) assumption that only disks marked read-write need copying.
I think this is the same as bug 1203032. Closing as such. If you disagree, please feel free to reopen. *** This bug has been marked as a duplicate of bug 1203032 ***