On Fri, 2020-07-03 at 16:06 +0200, Michal Privoznik wrote:
> On 7/3/20 3:59 PM, Andrea Bolognani wrote:
> > Is this change something that we should mention in the release notes?
> > If so, please post a patch that updates them accordingly. Thanks!
>
> Of course! I was think that I have to write a
On 7/3/20 3:59 PM, Andrea Bolognani wrote:
On Fri, 2020-07-03 at 12:28 +0200, Michal Privoznik wrote:
Michal Prívozník (9):
libvirt-storage: Document volume upload/download stream format
virstring: Introduce virStringIsNull()
virfile: Introduce virFileInDataDetectZeroes()
virsh: Pass
On Fri, 2020-07-03 at 12:28 +0200, Michal Privoznik wrote:
> Michal Prívozník (9):
> libvirt-storage: Document volume upload/download stream format
> virstring: Introduce virStringIsNull()
> virfile: Introduce virFileInDataDetectZeroes()
> virsh: Pass virshStreamCallbackDataPtr to virshStre
On Fri, Jul 03, 2020 at 01:50:22PM +0200, Michal Privoznik wrote:
> On 7/3/20 1:34 PM, Daniel P. Berrangé wrote:
> > On Fri, Jul 03, 2020 at 12:28:41PM +0200, Michal Privoznik wrote:
> > > The way our sparse streams are implemented is:
> > >
> > > 1) user facing APIs (virStreamSparseRecvAll() and
On 7/3/20 1:34 PM, Daniel P. Berrangé wrote:
On Fri, Jul 03, 2020 at 12:28:41PM +0200, Michal Privoznik wrote:
The way our sparse streams are implemented is:
1) user facing APIs (virStreamSparseRecvAll() and virStreamSparseSendAll()) take
callbacks as arguments. These callbacks read/write d
On Fri, Jul 03, 2020 at 12:28:41PM +0200, Michal Privoznik wrote:
> The way our sparse streams are implemented is:
>
> 1) user facing APIs (virStreamSparseRecvAll() and virStreamSparseSendAll())
> take
>callbacks as arguments. These callbacks read/write data or determine if
> there
>is a
The way our sparse streams are implemented is:
1) user facing APIs (virStreamSparseRecvAll() and virStreamSparseSendAll()) take
callbacks as arguments. These callbacks read/write data or determine if there
is a hole in the underlying file and big it is.
2) libvirtd has something similar - v
