Re: [libvirt] [PATCH v1.2.[1-5]-maint] qemu: blockcopy: Don't remove existing disk mirror info

2014-07-01 Thread Eric Blake
On 06/26/2014 07:51 AM, Eric Blake wrote: > From: Peter Krempa > > When creating a new disk mirror the new struct is stored in a separate > variable until everything went well. The removed hunk would actually > remove existing mirror information for example when the api would be run > if a mirror

Re: [libvirt] [PATCH v1.2.[1-5]-maint] qemu: blockcopy: Don't remove existing disk mirror info

2014-06-26 Thread Eric Blake
On 06/26/2014 07:56 AM, Peter Krempa wrote: > On 06/26/14 15:51, Eric Blake wrote: >> From: Peter Krempa >> >> When creating a new disk mirror the new struct is stored in a separate >> variable until everything went well. The removed hunk would actually >> remove existing mirror information for ex

Re: [libvirt] [PATCH v1.2.[1-5]-maint] qemu: blockcopy: Don't remove existing disk mirror info

2014-06-26 Thread Peter Krempa
On 06/26/14 15:51, Eric Blake wrote: > From: Peter Krempa > > When creating a new disk mirror the new struct is stored in a separate > variable until everything went well. The removed hunk would actually > remove existing mirror information for example when the api would be run > if a mirror stil

[libvirt] [PATCH v1.2.[1-5]-maint] qemu: blockcopy: Don't remove existing disk mirror info

2014-06-26 Thread Eric Blake
From: Peter Krempa When creating a new disk mirror the new struct is stored in a separate variable until everything went well. The removed hunk would actually remove existing mirror information for example when the api would be run if a mirror still exists. (cherry picked from commit 02b364e186d