Re: [libvirt-users] Blockpull behavior when interrupted

2016-07-22 Thread Eric Blake
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

[libvirt-users] libvirtd terminates running instances after monitor's socket inode id is changed

2016-07-22 Thread Gavin Nicholson
We accidentally moved /var/lib/libvirt/qemu to another directory which is on a different disk partition, then we moved it back; however, that caused changing the inode ids of the files inside /var/lib/libvirt/qemu including the socket files ( .monitor ) of the running VMs. The problem we are facing

Re: [libvirt-users] Blockpull behavior when interrupted

2016-07-22 Thread Andrew Martin
- 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 wrote: > > Hello, > > > > I use snapshot-crea