- BZ#609483
Red Hat Enterprise Linux guest conversion did not update /etc/sysconfig/kernel, which would lead to an incorrect kernel being set as the default in future updates. This would cause boot failure. /etc/sysconfig/kernel now updates correctly.
- BZ#616720
Partially written guest images were not cleaned up if a conversion to a libvirt target failed or was interrupted. With this update, all created volumes are removed if a conversion is not successful.
- BZ#618965
virt-v2v would not always update software in the transfer volume when updates were available because it relied on timestamps. The transfer volume is now updated whenever virt-v2v is used.
- BZ#623571
virt-v2v could not detect VMware Tools to uninstall it if VMware Tools was installed via tarball. When VMware Tools detected that it was no longer running on a VMware platform and attempted to disable itself on the guest, it overwrote changes made by virt-v2v during conversion. This resulted in broken networking and initrd images containing unnecessary drivers. virt-v2v can now detect and uninstall VMware Tools even when VMware Tools is installed via tarball.
- BZ#623579
If a Linux guest had an invalid default entry in the grub.conf file, virt-v2v assumed it was an i686 guest. This resulted in a converted guest that did not boot. virt-v2v now assumes an AMD64 or Intel 64 default architecture instead of i686.
- BZ#642258
virt-v2v could not convert a Red Hat Enterprise Linux guest that did not have the /etc/securetty file. Conversion without this file is now possible.
- BZ#643867
Conversion failed if conversion required updating the kernel and the guest had additional kernel modules installed. Conversion now succeeds and virt-v2v no longer attempts to uninstall old kernels.
- BZ#644295
When performing an offline installation of the VirtIO block driver in a Windows guest, virt-v2v incorrectly assumed that ControlSet001 was always the current control set, even if ControlSet001 had been marked as failed. The correct control set is now detected, and the VirtIO block driver installed in the correct location.
- BZ#656883
When creating a libvirt guest using block storage, virt-v2v incorrectly set the disk type to auto. This made libvirt unable to start the guest. Disk type is now set explicitly based on source metadata or other detection methods.
- BZ#581421
In certain circumstances, virt-v2v exited with a return value of 0, even though conversion failed. The correct values are now returned.
- BZ#609448
Red Hat Enterprise Linux guest conversion did not update /boot/grub/device.map with converted block device names in certain circumstances. device.map now updates as expected.
- BZ#670778
virt-v2v failed to convert a guest to a Red Hat Enterprise Virtualization target if the current working directory was not universally readable. Universal readability is no longer required.
- BZ#672521
virt-v2v failed to convert Windows guests that had a C:\Temp directory because it created a C:\temp directory without checking for file names that used alternative cases. virt-v2v now checks for case-sensitive file names before creating an appropriate temporary directory.
- BZ#671300
virt-v2v failed to enable VirtIO support when converting a Xen guest that had both a paravirtualized Xen kernel and a fully virtualized kernel installed. The fully virtualized kernel is now made the default kernel and conversion succeeds as expected.
- BZ#676323
It was not possible to create a Red Hat Enterprise Virtualization template from a guest that was converted by virt-v2v. Guests imported with this updated package can now be used to create templates.
- BZ#679017
When converting a 64-bit Windows XP guest to run on Red Hat Enterprise Virtualization, virt-v2v incorrectly identified the guest as 64-bit Windows 2003. 64-bit Windows XP guests are now correctly identified as Windows XP when imported into Red Hat Enterprise Virtualization.
- BZ#690286
augeas was not thread safe, and could leak file descriptors when multiple programs attempted to use the libvirt library simultaneously. This resulted in the failure of the calling program. augeas has been modified to remove the global variable that caused this threading issue.
- BZ#620449
Sparse storage was not retained across conversion. Storage type is now retained across conversion, but can be modified with the -oa flag.
- BZ#654531
virt-v2v used enum integers to populate the ovf:disk-interface field when converting for Red Hat Enterprise Virtualization. However, this produced an ovf file that was not intelligible to Red Hat Enterprise Virtualization Manager. The disk-interface is now populated with correct enum values (IDE, SCSI, or VirtIO), allowing Red Hat Enterprise Virtualization Manager to understand the ovf file.
- BZ#664942
When converting a guest to run on Red Hat Enterprise Virtualization, virt-v2v identified created storage as sparse or raw. This combination is not supported when importing into a data center that uses block storage (fibre channel or iSCSI). virt-v2v can now convert storage format and allocation policy correctly. Additionally, customers can specify a format and allocation policy compatible with the target data center type by using the -of and -oa command line options.
- BZ#671083
virt-v2v conversion would hang if its output was redirected at the command line. This bug was reported and corrected during development. It was not seen in production systems in the field.
- BZ#678950
Conversion of a Red Hat Enterprise Linux Desktop virtual machine failed with the following error:
Can't locate object method "can_handle" via package
"Sys::VirtV2V::Converter::RedHat" at
/usr/share/perl5/vendor_perl/Sys/VirtV2V/Converter.pm line 121.
This issue has been resolved and conversion should now complete successfully
