Re: [Libguestfs] [PATCH] v2v/v2v.ml: Use larger request size for -o rhv-upload

This can be done in nbdcopy by adding http-ops. The pipeline in rhv-upload case will be: nbdkit (any input) -> nbdcopy (nbd-ops/http-ops) -> imageio server Another way is to drop nbdcopy for rhv-upload - if we provide nbd input, we can use imageio client to read from the nbd input and write to imageio server. The pipeline will be: nbdkit (any input) -> imageio client -> imageio server This means that the v2v output can optionally do the copy phase, if it knows how to read from the nbdkit input. Yet another way is to rewrite imageio in Go, and use libnbd async API, which will eliminate most of the overhead of the http requests. I started this work with the imageio client side. You can check what we have so far here: https://github.com/oVirt/ovirt-imageio/tree/master/ovirt-img For the long term, I think improving nbdcopy to support additional input/output backends is the right way and will make it more useful for other purposes.