On Thu, 2013-10-17 at 12:32 +0100, Richard W.M. Jones wrote:
On Tue, Oct 15, 2013 at 06:29:39PM -0200, emitor@gmail.com wrote:
Hi,
I've imported a Windows VM from an ESXi to an export domain using virt-v2v. It didn't return me any error wen it finished (i think), but when attached the export domain I get the following advertising and the vm doesn't appear in the list to be imported:
Failed to read VM '[Empty Name]' OVF, it may be corrupted
Could you give me some hint to fix this, or what it could be the problem?
This seems like a bug in virt-v2v, but it's hard to say.
You should enable debugging in virt-v2v and then we should be able to see exactly what's going on.
export LIBGUESTFS_TRACE=1 virt-v2v [...etc...]
Remember to capture the complete, unedited output.
The most useful debugging information here would actually be the possibly corrupt OVF file. It's almost certainly going to be a metadata issue rather than a guest conversion issue. Whatever additional detailed logging you can provide about why RHEV rejected it would also be useful. Matt