- Original Message -
> From: "Eric Blake"
> To: "Andrew Martin"
> Cc: libvirt-users@redhat.com
> Sent: Friday, July 22, 2016 10:40:54 PM
> Subject: Re: [libvirt-users] Blockpull behavior when interrupted
>
> On 07/22/2016 11:30 AM, Andrew Mar
- Original Message -
> From: "Eric Blake"
> To: "Andrew Martin"
> Cc: libvirt-users@redhat.com
> Sent: Friday, July 22, 2016 10:40:54 PM
> Subject: Re: [libvirt-users] Blockpull behavior when interrupted
>
> On 07/22/2016 11:30 AM, Andrew Mar
On 07/22/2016 11:30 AM, Andrew Martin wrote:
>
> Thanks, that was a helpful overview. To clarify, block commit is changing
> the backing files,but even though it is doing that, the data is consistent
> even if it is interrupted?
Yes, the guest's view of the data is consistent. Intermediate back
- Original Message -
> From: "Eric Blake"
> To: "Andrew Martin" , libvirt-users@redhat.com
> Sent: Thursday, July 21, 2016 5:40:07 PM
> Subject: Re: [libvirt-users] Blockpull behavior when interrupted
>
> On 07/21/2016 03:05 PM, Andrew Martin wro
On 07/21/2016 03:05 PM, Andrew Martin wrote:
> Hello,
>
> I use snapshot-create-as followed by blockpull when creating external
> snapshots
> of VMs. This works well, however I am curious about the behavior of blockpull
> after an unexpected shutdown (or SIGKILL). If a blockpull is in progress an
Hello,
I use snapshot-create-as followed by blockpull when creating external snapshots
of VMs. This works well, however I am curious about the behavior of blockpull
after an unexpected shutdown (or SIGKILL). If a blockpull is in progress and an
unexpected power loss occurs, will the VM continue to
