Thanks for the review. That's upstream now in
commit 0805ea93796b8b57e7c9f0bc04f83ea76a9820a5.
I fixed up the commit message and added a non-mandatory -O option to
control output.
We can keep it experimental status for now and decide before
virt-v2v 2.2 (next stable) if we want to keep it or
On Thu, Nov 24, 2022 at 10:54:42AM +0100, Laszlo Ersek wrote:
> On 11/22/22 16:47, Richard W.M. Jones wrote:
> > In Kubernetes and tools like Kubevirt, it's not possible to create
> > some disks and then attach to them (in order to populate them with
> > data) in one step. This makes virt-v2v
On 11/22/22 16:47, Richard W.M. Jones wrote:
> This tool can be used to estimate the disk space needed before doing a
> virt-v2v conversion.
>
> It is a replacement for the old --print-estimate option which was
> dropped in virt-v2v 2.0 (commit 5828c9c7d5 "v2v: Remove
> --print-estimate option").
On 11/22/22 16:47, Richard W.M. Jones wrote:
> In Kubernetes and tools like Kubevirt, it's not possible to create
> some disks and then attach to them (in order to populate them with
> data) in one step. This makes virt-v2v conversions awkward because
> ideally we would like the output mode (-o
In Kubernetes and tools like Kubevirt, it's not possible to create
some disks and then attach to them (in order to populate them with
data) in one step. This makes virt-v2v conversions awkward because
ideally we would like the output mode (-o kubevirt) to both create the
target disks and populate
This tool can be used to estimate the disk space needed before doing a
virt-v2v conversion.
It is a replacement for the old --print-estimate option which was
dropped in virt-v2v 2.0 (commit 5828c9c7d5 "v2v: Remove
--print-estimate option").
---
docs/Makefile.am| 15 ++
