search for: eric_blake

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 reference the backing file for the parts of it that have not yet been copied? Or, will will the disk

...he guest-visible data from the active layer is never corrupted even if individual backing files within the chain are (temporarily) out of sync with reality. For more ideas on how to visualize things, check out my presentation at last year's KVM Forum: http://www.linux-kvm.org/images/5/5f/03x02-Eric_Blake-Backing_Chain_Management_in_QEMU_and_libvirt.pdf -- Eric Blake eblake redhat com +1-919-301-3266 Libvirt virtualization library http://libvirt.org

...m the active layer is never corrupted even if individual backing > files within the chain are (temporarily) out of sync with reality. > > For more ideas on how to visualize things, check out my presentation at > last year's KVM Forum: > http://www.linux-kvm.org/images/5/5f/03x02-Eric_Blake-Backing_Chain_Management_in_QEMU_and_libvirt.pdf > Eric, 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? Reviewing the presentation brought up another question. I h...