On 29.09.2016 23:51, John Ferlan wrote: > >> >>> a lot of exposure to that code. I do know there's still upstream qemu >>> work taking place. We really should be very careful about adding >>> anything to libvirt before the upstream work is done. In particular any >>> x-* command support. >>> >> >> AFAIK full pull backups as well as full/incremennal push backups are >> ready to use in qemu. It is a pity that other commands that helps >> organize pull backup process still has experimental status. One day >> they drop this x- and I doubt that things will changed very radically >> in comparison to what we have today. So if with the help of community >> this patch will be ironed out libvirt will get pull backups instantly >> after qemu be full ready. >> > > FWIW: Happened to be scanning through qemu-devel today and came across > the following topic (which interested me because it's related to other > work I'm involved in): > > http://lists.nongnu.org/archive/html/qemu-devel/2016-09/msg07721.html > > Anyway a few responses in there's this: > > http://lists.nongnu.org/archive/html/qemu-devel/2016-09/msg07748.html > > and finally this: > > http://lists.nongnu.org/archive/html/qemu-devel/2016-09/msg07773.html > > Since you do rely on blockdev-add - I'd just caution you to not rely on > something specific... > > > John > Thanx for information! -- libvir-list mailing list libvir-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvir-list