On Fri, Jan 07, 2022 at 12:06:11PM +0000, Richard W.M. Jones wrote:
From the non-verbose output of virt-v2v we can derive 3 times of
interest for benchmarking performance:
$ virt-v2v -i disk fedora-35.img -o null
[ 1.1] Opening the source
[ 7.3] Inspecting the source
[ 12.4] Checking for sufficient free disk space in the guest
[ 12.4] Converting Fedora Linux 35 (Thirty Five) to run on KVM
[ 56.6] Mapping filesystem data to avoid copying unused and blank areas
[ 59.8] Closing the overlay
[ 60.3] Assigning disks to buses
[ 60.3] Checking if the guest needs BIOS or UEFI to boot
[ 61.3] Copying disk 1/1
█ 100% [****************************************]
[ 62.4] Creating output metadata
[ 62.4] Finishing off
=> Conversion time: 56.6 - 12.4 = 44.2
This is wrong. I actually started recording conversion time from the
moment the source image is opened by libguestfs, ie:
=> Conversion time: 56.6 - 1.1 = 55.5
Rich.
--
Richard Jones, Virtualization Group, Red Hat
http://people.redhat.com/~rjones
Read my programming and virtualization blog:
http://rwmj.wordpress.com
libguestfs lets you edit virtual machines. Supports shell scripting,
bindings from many languages.
http://libguestfs.org