Re: [libvirt] [PATCH 3/3] introduce pull backup

2016-10-04 Thread Nikolay Shirokovskiy
On 05.10.2016 00:55, John Ferlan wrote: > > > On 09/30/2016 10:38 AM, Nikolay Shirokovskiy wrote: >> >> >> On 30.09.2016 01:02, John Ferlan wrote: >>> >>> >>> [...] >>> > > Because it's also dependent upon an x-blockdev-del, it cannot be pushed > upstream to libvirt. I know qemu wor

Re: [libvirt] [PATCH 3/3] introduce pull backup

2016-10-04 Thread John Ferlan
On 09/30/2016 10:38 AM, Nikolay Shirokovskiy wrote: > > > On 30.09.2016 01:02, John Ferlan wrote: >> >> >> [...] >> Because it's also dependent upon an x-blockdev-del, it cannot be pushed upstream to libvirt. I know qemu work continues w/r/t blockdev-add and backups, but I d

Re: [libvirt] [PATCH 3/3] introduce pull backup

2016-09-30 Thread Nikolay Shirokovskiy
On 30.09.2016 14:35, Kashyap Chamarthy wrote: > On Thu, Sep 29, 2016 at 06:02:08PM -0400, John Ferlan wrote: > > [...] > Because it's also dependent upon an x-blockdev-del, it cannot be pushed upstream to libvirt. I know qemu work continues w/r/t blockdev-add and backups, but I d

Re: [libvirt] [PATCH 3/3] introduce pull backup

2016-09-30 Thread Nikolay Shirokovskiy
On 30.09.2016 01:02, John Ferlan wrote: > > > [...] > >>> >>> Because it's also dependent upon an x-blockdev-del, it cannot be pushed >>> upstream to libvirt. I know qemu work continues w/r/t blockdev-add and >>> backups, but I don't follow it in detail (not enough time in the day!). >> >> Ok,

Re: [libvirt] [PATCH 3/3] introduce pull backup

2016-09-30 Thread Kashyap Chamarthy
On Thu, Sep 29, 2016 at 06:02:08PM -0400, John Ferlan wrote: [...] > >> Because it's also dependent upon an x-blockdev-del, it cannot be pushed > >> upstream to libvirt. I know qemu work continues w/r/t blockdev-add and > >> backups, but I don't follow it in detail (not enough time in the day!).

Re: [libvirt] [PATCH 3/3] introduce pull backup

2016-09-29 Thread John Ferlan
[...] >> >> Because it's also dependent upon an x-blockdev-del, it cannot be pushed >> upstream to libvirt. I know qemu work continues w/r/t blockdev-add and >> backups, but I don't follow it in detail (not enough time in the day!). > > Ok, at least the patch can be some kind of candidate to be

Re: [libvirt] [PATCH 3/3] introduce pull backup

2016-09-27 Thread Nikolay Shirokovskiy
On 27.09.2016 01:04, John Ferlan wrote: > > > On 09/07/2016 05:24 AM, Nikolay Shirokovskiy wrote: >> Add API to start/stop exporting disks for a backup and add qemu >> implementation. >> >> The latter is not complete yet. At least backup disks are not >> cleaned up and libvirt restart is not ha

Re: [libvirt] [PATCH 3/3] introduce pull backup

2016-09-26 Thread John Ferlan
On 09/07/2016 05:24 AM, Nikolay Shirokovskiy wrote: > Add API to start/stop exporting disks for a backup and add qemu > implementation. > > The latter is not complete yet. At least backup disks are not > cleaned up and libvirt restart is not handled. > --- > examples/object-events/event-test.c

[libvirt] [PATCH 3/3] introduce pull backup

2016-09-07 Thread Nikolay Shirokovskiy
Add API to start/stop exporting disks for a backup and add qemu implementation. The latter is not complete yet. At least backup disks are not cleaned up and libvirt restart is not handled. --- examples/object-events/event-test.c | 3 + include/libvirt/libvirt-domain-backup.h | 45 +++ incl