Created attachment 1689894 [details] convert-to-libvirt.log Description of problem: [RFE]Remove cache=none for guest after v2v converting to libvirt Version-Release number of selected component (if applicable): virt-v2v-1.42.0-3.module+el8.3.0+6497+b190d2a5.x86_64 libguestfs-1.42.0-1.module+el8.3.0+6496+d39ac712.x86_64 libvirt-6.3.0-1.module+el8.3.0+6478+69f490bb.x86_64 qemu-kvm-5.0.0-0.module+el8.3.0+6620+5d5e1420.x86_64 nbdkit-1.20.1-1.module+el8.3.0+6491+7f1d5b30.x86_6 VMware-vix-disklib-7.0.0-15832853.x86_64.tar.gz How reproducible: 100% Steps to Reproduce: 1.Convert a guest from VMware to libvirt by virt-v2v # virt-v2v -ic vpx://root.198.169/data/10.73.199.217/?no_verify=1 -it vddk -io vddk-libdir=/home/vmware-vix-disklib-distrib -io vddk-thumbprint=B5:52:1F:B4:21:09:45:24:51:32:56:F6:63:6A:93:5D:54:08:2D:78 esx7.0-rhel8.2-x86_64 -ip /home/passwd -o local -os /home -v -x |& tee > convert-to-libvirt.log 2.Check guest xml about cache setting # cat /home/esx7.0-rhel8.2-x86_64.xml |grep cache <driver name='qemu' type='raw' cache='none'/> Expected results: As live migration doesn't require cache=none Since libvirt-5.6.0-2 + qemu-kvm-4.0.0, and kvm guest will have better disk I/O performance, so it's time to remove cache=none for guest after v2v converting to libvirt Additional info:
Patch posted upstream: https://www.redhat.com/archives/libguestfs/2020-May/msg00038.html
Upstream: https://github.com/libguestfs/virt-v2v/commit/9720f45e0cd9283739fd2a67c19e66912489dfc7
I can reproduce this bug with old virt-v2v version. Test the bug with below builds: # rpm -qa virt-v2v libvirt qemu-kvm qemu-kvm-5.0.0-0.module+el8.3.0+6620+5d5e1420.x86_64 libvirt-6.3.0-1.module+el8.3.0+6478+69f490bb.x86_64 virt-v2v-1.42.0-4.module+el8.3.0+6798+ad6e66be.x86_64 # virt-v2v -ic vpx://root.198.169/data/10.73.199.217/?no_verify=1 -it vddk -io vddk-libdir=/home/vmware-vix-disklib-distrib -io vddk-thumbprint=B5:52:1F:B4:21:09:45:24:51:32:56:F6:63:6A:93:5D:54:08:2D:78 esx7.0-rhel8.2-x86_64 --network default -ip /home/passwd -os default [ 0.0] Opening the source -i libvirt -ic vpx://root.198.169/data/10.73.199.217/?no_verify=1 esx7.0-rhel8.2-x86_64 -it vddk -io vddk-libdir=/home/vmware-vix-disklib-distrib -io vddk-thumbprint=B5:52:1F:B4:21:09:45:24:51:32:56:F6:63:6A:93:5D:54:08:2D:78 [ 1.7] Creating an overlay to protect the source from being modified [ 5.0] Opening the overlay [ 19.4] Inspecting the overlay [ 42.5] Checking for sufficient free disk space in the guest [ 42.5] Estimating space required on target for each disk [ 42.5] Converting Red Hat Enterprise Linux 8.2 (Ootpa) to run on KVM virt-v2v: This guest has virtio drivers installed. [ 186.1] Mapping filesystem data to avoid copying unused and blank areas [ 187.0] Closing the overlay [ 187.3] Assigning disks to buses [ 187.3] Checking if the guest needs BIOS or UEFI to boot [ 187.3] Initializing the target -o libvirt -os default [ 187.4] Copying disk 1/1 to /var/lib/libvirt/images/esx7.0-rhel8.2-x86_64-sda (raw) (100.00/100%) [ 475.4] Creating output metadata [ 475.4] Finishing off # virsh dumpxml esx7.0-rhel8.2-x86_64|grep cache After conversion,cache='none' has been removed from guest xml. Start the guest and guest works well,refer to the above comments,move the bug to VERIFIED.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (virt:8.3 bug fix and enhancement update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2020:5137