Bug 1208588

Summary:	RFE: Provide a way to specify which disks are block copied during migration
Product:	[Community] Virtualization Tools	Reporter:	Matthew Gilliard <matthew.gilliard>
Component:	libvirt	Assignee:	Libvirt Maintainers <libvirt-maint>
Status:	CLOSED DUPLICATE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	unspecified	CC:	berrange, dyuan, j.rosenboom, kchamart, mprivozn, rbalakri, shyu, zpeng
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:
Clones:	1210352 (view as bug list)		Environment:
Last Closed:	2015-04-27 05:38:56 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Matthew Gilliard 2015-04-02 15:27:55 UTC

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%

Comment 1 Daniel Berrangé 2015-04-09 13:50:48 UTC

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.

Comment 2 Michal Privoznik 2015-04-27 05:38:56 UTC

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 ***