- The virt-v2v packages used to rename block devices in various guest configuration files during conversion, including the /etc/fstab file. Consequently, the virt-v2v utility returned a redundant warning message when a guest's /etc/fstab file referenced to the /etc/fd0 file as the block device did not know it. To fix this bug, warning messages concerning floppy devices have been explicitly suppressed and virt-v2v no longer returns warning messages in this situation.
- When reading a libvirt guest, virt-v2v uses libvirt metadata to determine the on-disk format, considering only those of "dir", "fs", and "netfs" types as meaningful. If a guest used a different type of storage pool, virt-v2v interpreted these data as a format type, which was unable to convert by libvirt guests. To address this bug, virt-v2v now only uses volume format metadata from storage pools of type "dir", "fs", and "netfs", but also all other storage pools can only hold raw data, so the format is assumed to be "raw". As a result, virt-v2v can now convert libvirt guests using any supported storage pool type.
- When creating a new libvirt guest, virt-v2v failed to disable caching for disks as recommended. As a consequence, guests created by virt-v2v used caching for their disks, unless explicitly disabled by the user after conversion. To address this bug, virt-v2v now explicitly disables caching for all disks when creating a new libvirt guest, and guests created by virt-v2v now have caching disabled for all disks. The user can enable it again if required after conversion.
- Virt-v2v failed when attempting to perform an on-disk format conversion when reading a guest using the libvirtxml input method. A patch has been provided to fix this bug and virt-v2v can now perform format conversions on guests using libvirtxml.
- With this update, virt-v2v can do an on-disk format conversion while converting a remote libvirt guest. Note that when doing this kind of format conversion, virt-v2v must make an intermediate copy of the guest storage data on the conversion server. Other types of conversion do not require any intermediate storage on the conversion server. The user must ensure that the TMPDIR temporary directory has sufficient space for this intermediate copy.