When an OVF file under it's DiskSection defines any disk without the ovf:populatedSize, import will fail with Use of uninitialized value $usage in numeric gt (>) at /usr/share/perl5/vendor_perl/Sys/VirtConvert/Connection/VMwareOVASource.pm line 400. Use of uninitialized value $usage in numeric gt (>) at /usr/share/perl5/vendor_perl/Sys/VirtConvert/Connection/VMwareOVASource.pm line 400. Use of uninitialized value $usage in numeric gt (>) at /usr/share/perl5/vendor_perl/Sys/VirtConvert/Connection/VMwareOVASource.pm line 400. Use of uninitialized value $usage in numeric gt (>) at /usr/share/perl5/vendor_perl/Sys/VirtConvert/Connection/VMwareOVASource.pm line 400. Use of uninitialized value in subroutine entry at /usr/lib64/perl5/vendor_perl/Sys/Virt/Domain.pm line 51. Target count required for Term::ProgressBar new at blib/lib/Class/MethodMaker/Engine.pm (autosplit into blib/lib/auto/Class/MethodMaker/Engine/new.al) line 957. However, according to spec, the property is optional. Version-Release number of selected component (if applicable): Fedora 20 / virt-v2v 0.9.0 How reproducible: Import an OVA/OVF with a DiskSection and a Disk in it without the ovf:populatedSize but with the ovf:capacity property Actual results: Import fails. Expected results: Import succeeds. Additional info: The OVF standard (http://www.dmtf.org/sites/default/files/standards/documents/DSP0243_1.0.0.pdf) defines: "For non-empty disks, the actual used size of the disk may optionally be specified using the ovf:populatedSize attribute. The unit of this attribute is always bytes. ovf:populatedSize is allowed to be an estimate of used disk size but shall not be larger than ovf:capacity."
Solvable by defining $usage in _get_volume as my $usage = _node_val($disk, '@ovf:populatedSize') || $size;
Hi, thanks for the bug report. Unfortunately it is filed against a very old version of virt-v2v (0.9) which we don't support at all. Luckily there is a newer version which almost certainly fixes your bug already. It's available starting in Fedora 21. If you still experience this bug, please try with the new version, and reopen if it still happens.
(In reply to Richard W.M. Jones from comment #1) > Unfortunately it is filed against a > very old version of virt-v2v (0.9) Well, that tends to happen if you wait 16 months with a reply to a ready2commit submitted patch.