search for: msg00177

...; > So it looks to me it was not sufficient, looking at the example codes in > spec, do we need to track last seen used_wrap_counter here? I don't think we have to track used_wrap_counter in driver. There was a discussion on this: https://lists.oasis-open.org/archives/virtio-dev/201802/msg00177.html And after that, below sentence was added (it's also in the above words you quoted): """ Other techniques to detect VIRTQ_DESC_F_AVAIL/VIRTQ_DESC_F_USED bit changes might also be possible. """ Best regards, Tiwei Bie > > Thanks

...; > So it looks to me it was not sufficient, looking at the example codes in > spec, do we need to track last seen used_wrap_counter here? I don't think we have to track used_wrap_counter in driver. There was a discussion on this: https://lists.oasis-open.org/archives/virtio-dev/201802/msg00177.html And after that, below sentence was added (it's also in the above words you quoted): """ Other techniques to detect VIRTQ_DESC_F_AVAIL/VIRTQ_DESC_F_USED bit changes might also be possible. """ Best regards, Tiwei Bie > > Thanks

This version addresses comments on v3. Changes since v3: - Finally got spacing right (Eric) - Reorder includes (Richard) - Return 0 or -1 instead of r (Richard) - Add common/include/isaligned.h to Makefile.am (Richard) v3 was here: https://www.redhat.com/archives/libguestfs/2018-August/msg00177.html Nir Soffer (4): file: Avoid unsupported fallocate() calls file: Support zero without ZERO_RANGE common: Add isaligned helper module file: Zero for block devices on old kernels common/include/Makefile.am | 1 + common/include/isaligned.h | 51 ++++++++++ plugins/file/Makefile.am...

...v3. > > Changes since v3: > - Finally got spacing right (Eric) > - Reorder includes (Richard) > - Return 0 or -1 instead of r (Richard) > - Add common/include/isaligned.h to Makefile.am (Richard) > > v3 was here: > https://www.redhat.com/archives/libguestfs/2018-August/msg00177.html > > Nir Soffer (4): > file: Avoid unsupported fallocate() calls > file: Support zero without ZERO_RANGE > common: Add isaligned helper module > file: Zero for block devices on old kernels I pushed the isaligned change. The others all look fine to me now, and I woul...

On Wed, Mar 7, 2018 at 12:18 AM Richard W.M. Jones <rjones@redhat.com> wrote: > Previous versions: > v3: https://www.redhat.com/archives/libguestfs/2018-March/msg00000.html > v2: > https://www.redhat.com/archives/libguestfs/2018-February/msg00177.html > v1: > https://www.redhat.com/archives/libguestfs/2018-February/msg00139.html > > This completely rethinks the approach taken by the previous patches. > > Instead of trying to involve qemu's curl driver, this uses a small > Python 3 nbdkit plugin to interface betwee...

...looking at the example codes in > > > spec, do we need to track last seen used_wrap_counter here? > > I don't think we have to track used_wrap_counter in > > driver. There was a discussion on this: > > > > https://lists.oasis-open.org/archives/virtio-dev/201802/msg00177.html > > > > And after that, below sentence was added (it's also > > in the above words you quoted): > > > > """ > > Other techniques to detect > > VIRTQ_DESC_F_AVAIL/VIRTQ_DESC_F_USED bit changes > > might also be possible. >...

...looking at the example codes in > > > spec, do we need to track last seen used_wrap_counter here? > > I don't think we have to track used_wrap_counter in > > driver. There was a discussion on this: > > > > https://lists.oasis-open.org/archives/virtio-dev/201802/msg00177.html > > > > And after that, below sentence was added (it's also > > in the above words you quoted): > > > > """ > > Other techniques to detect > > VIRTQ_DESC_F_AVAIL/VIRTQ_DESC_F_USED bit changes > > might also be possible. >...

Hello, http://wiki.xensource.com/xenwiki/XenBusDriver?highlight=%28xenbus%29 says that "XenBus provides a bus abstraction for paravirtualized drivers to communicate between domains. In practice, the bus is used for configuration negotiation, leaving most data transfer to be done via page flipping." What is the equivalent mechanism for fully-virtualized drivers in Xen (HVM running

...me it was not sufficient, looking at the example codes in >> spec, do we need to track last seen used_wrap_counter here? > I don't think we have to track used_wrap_counter in > driver. There was a discussion on this: > > https://lists.oasis-open.org/archives/virtio-dev/201802/msg00177.html > > And after that, below sentence was added (it's also > in the above words you quoted): > > """ > Other techniques to detect > VIRTQ_DESC_F_AVAIL/VIRTQ_DESC_F_USED bit changes > might also be possible. > """ > > Best regards,...

...:18 AM Richard W.M. Jones <rjones@redhat.com> > > wrote: > > > > > Previous versions: > > > v3: > https://www.redhat.com/archives/libguestfs/2018-March/msg00000.html > > > v2: > > > https://www.redhat.com/archives/libguestfs/2018-February/msg00177.html > > > v1: > > > https://www.redhat.com/archives/libguestfs/2018-February/msg00139.html > > > > > > This completely rethinks the approach taken by the previous patches. > > > > > > Instead of trying to involve qemu's curl driver, this...

...des in > > > > spec, do we need to track last seen used_wrap_counter here? > > > I don't think we have to track used_wrap_counter in > > > driver. There was a discussion on this: > > > > > > https://lists.oasis-open.org/archives/virtio-dev/201802/msg00177.html > > > > > > And after that, below sentence was added (it's also > > > in the above words you quoted): > > > > > > """ > > > Other techniques to detect > > > VIRTQ_DESC_F_AVAIL/VIRTQ_DESC_F_USED bit changes >...

...te: > On Wed, Mar 7, 2018 at 12:18 AM Richard W.M. Jones <rjones@redhat.com> > wrote: > > > Previous versions: > > v3: https://www.redhat.com/archives/libguestfs/2018-March/msg00000.html > > v2: > > https://www.redhat.com/archives/libguestfs/2018-February/msg00177.html > > v1: > > https://www.redhat.com/archives/libguestfs/2018-February/msg00139.html > > > > This completely rethinks the approach taken by the previous patches. > > > > Instead of trying to involve qemu's curl driver, this uses a small > > Python...

Previous versions: v3: https://www.redhat.com/archives/libguestfs/2018-March/msg00000.html v2: https://www.redhat.com/archives/libguestfs/2018-February/msg00177.html v1: https://www.redhat.com/archives/libguestfs/2018-February/msg00139.html This completely rethinks the approach taken by the previous patches. Instead of trying to involve qemu's curl driver, this uses a small Python 3 nbdkit plugin to interface between qemu and the oVirt server. The...

This series extract oVirt SDK and imageio code to make it eaiser to follow the code and improve error handing in open() and close(). The first small patches can be consider as fixes for downstream. Tested based on libguestfs v1.41.5, since I had trouble building virt-v2v and libguestfs from master. Nir Soffer (18): rhv-upload: Remove unused exception class rhv-upload: Check status more

...; > spec, do we need to track last seen used_wrap_counter here? > > > > I don't think we have to track used_wrap_counter in > > > > driver. There was a discussion on this: > > > > > > > > https://lists.oasis-open.org/archives/virtio-dev/201802/msg00177.html > > > > > > > > And after that, below sentence was added (it's also > > > > in the above words you quoted): > > > > > > > > """ > > > > Other techniques to detect > > > > VIRTQ_DESC_F_AVAIL...

...; > spec, do we need to track last seen used_wrap_counter here? > > > > I don't think we have to track used_wrap_counter in > > > > driver. There was a discussion on this: > > > > > > > > https://lists.oasis-open.org/archives/virtio-dev/201802/msg00177.html > > > > > > > > And after that, below sentence was added (it's also > > > > in the above words you quoted): > > > > > > > > """ > > > > Other techniques to detect > > > > VIRTQ_DESC_F_AVAIL...

Fixes the majority of the pycodestyle issues in the Python scripts, and fix the existing test-v2v-python-syntax.sh to use pycodestyle to actually perform style checks. Pino Toscano (6): PEP 8: adapt whitespaces in lines PEP 8: move imports at the top PEP 8: adapt empty lines tests: find all the Python scripts for syntax checks -o rhv-upload: remove unused Python imports Revamp check

v7 was here: https://www.redhat.com/archives/libguestfs/2018-March/msg00143.html Since then: - Earlier patches are now upstream. - The to-do list is moved from the commit message to the TODO file. - This version forces -of raw + -oa sparse and gives an error in any other mode. We intend to lift these restrictions later. - Tested against latest imageio which supports longer timeouts,

...initial_size = params['disk_size'], + provisioned_size = params['disk_size'], + # XXX Ignores params['output_sparse']. + # Handling this properly will be complex, see: + # https://www.redhat.com/archives/libguestfs/2018-March/msg00177.html + sparse = True, + storage_domains = [ + types.StorageDomain( + name = params['output_storage'], + ) + ], + ) + ) + + # Wait till the disk is up, as the transfer can't start if the + #...

...initial_size = params['disk_size'], + provisioned_size = params['disk_size'], + # XXX Ignores params['output_sparse']. + # Handling this properly will be complex, see: + # https://www.redhat.com/archives/libguestfs/2018-March/msg00177.html + sparse = True, + storage_domains = [ + types.StorageDomain( + name = params['output_storage'], + ) + ], + ) + ) + + # Wait till the disk is up, as the transfer can't start if the + #...