[Libguestfs] [PATCH 2/2] v2v: Add --print-target to display overlay and target information.

This is analogous to --print-source, except that it prints the overlay and target disk information. The output looks like below. Note there is one overlay and one target section per disk. Overlay and Target information (--print-target option): overlay file:

[Libguestfs] [PATCH 1/2] v2v: Update target.target_estimated_size in targets list in main function.

The rebasing in commit 5dae9ca23dab90dfb890f6663aa4bacf1df31ced caused this field to never get updated. --- v2v/v2v.ml | 14 -- 1 file changed, 8 insertions(+), 6 deletions(-) diff --git a/v2v/v2v.ml b/v2v/v2v.ml index f494defcf..75936c501 100644 --- a/v2v/v2v.ml +++ b/v2v/v2v.ml @@

Re: [Libguestfs] [PATCH v4 0/3] v2v: Add -o rhv-upload output mode.

On 03/14/2018 02:04 PM, Richard W.M. Jones wrote: I don't think we really need trim or flush. They're only minor optimizations. Zero is the one which is required. FWIW NBD allows you to flush ranges or flush the whole disk, in case that matters (your proposal only allows you to flush the

Re: [Libguestfs] [PATCH v4 0/3] v2v: Add -o rhv-upload output mode.

On 03/14/2018 04:07 PM, Nir Soffer wrote: What is the use case for flushing ranges? I guess we will have one or few flushes per images. Looking at sync_file_range(2), it does not seem to be a safe way to flush: Wow - I didn't know there was a syscall for flushing ranges. Even if it is

Re: [Libguestfs] [PATCH v4 0/3] v2v: Add -o rhv-upload output mode.

On Mon, Mar 12, 2018 at 2:57 PM Eric Blake wrote: > On 03/12/2018 07:13 AM, Nir Soffer wrote: > > On Mon, Mar 12, 2018 at 12:32 PM Richard W.M. Jones > > wrote: > > > >> On Mon, Mar 12, 2018 at 07:13:52AM +, Nir Soffer wrote: > >>> On Fri, Mar 9, 2018

Re: [Libguestfs] proposal for feature to add global setting for libguestfs emulation type

On Wed, Mar 14, 2018 at 03:08:18PM -0700, Raghu Toppur wrote: > The man page for libguestfs says: > > export LIBGUESTFS_BACKEND_SETTINGS=force_tcg > will force the direct and libvirt backends to use TCG (software emulation) > instead of KVM (hardware accelerated virtualization). > > However,

Re: [Libguestfs] [PATCH v4 0/3] v2v: Add -o rhv-upload output mode.

On Wed, Mar 14, 2018 at 9:04 PM Richard W.M. Jones wrote: > On Wed, Mar 14, 2018 at 06:56:19PM +, Nir Soffer wrote: > > I posted documentation for the new API optimized for random I/O: > > https://gerrit.ovirt.org/#/c/89022/ > > Wish I'd had this documentation when I

Re: [Libguestfs] [PATCH v4 0/3] v2v: Add -o rhv-upload output mode.

On Wed, Mar 14, 2018 at 09:07:31PM +, Nir Soffer wrote: > On Wed, Mar 14, 2018 at 9:04 PM Richard W.M. Jones > wrote: > > FWIW NBD allows you to flush ranges or flush the whole disk, in case > > that matters (your proposal only allows you to flush the whole disk). > > > >

Re: [Libguestfs] [PATCH v4 0/3] v2v: Add -o rhv-upload output mode.

On Wed, Mar 14, 2018 at 06:56:19PM +, Nir Soffer wrote: > I posted documentation for the new API optimized for random I/O: > https://gerrit.ovirt.org/#/c/89022/ Wish I'd had this documentation when I started the patch :-) Yes, it's much clearer. > I changed POST to PATCH to match the

[Libguestfs] proposal for feature to add global setting for libguestfs emulation type

The man page for libguestfs says: export LIBGUESTFS_BACKEND_SETTINGS=force_tcg will force the direct and libvirt backends to use TCG (software emulation) instead of KVM (hardware accelerated virtualization). However, our application has many services (run by different users) which make use of