On Tue, Jul 19, 2016 at 07:02:24PM +0100, Cam Mac wrote:
Try to run virt-v2v -i ova -o local to import the ova to local disk (see the virt-v2v man page for more options) and see if that pass - the errors can be more detailed there (it suppose to reflect the same error that you get in vdsm log)., another options you can do is run virt-v2v in verbose mode (virt-v2v -v).
I can try this but I'm not quite sure how to go about it. The ovf I created via guest-image-ovf-creator is on an NFS mount on the engine: do I need to run virt-v2v on one of the nodes? If so, I assume I need to set the output to an export domain. Does '-o local' stick it on the node's VM storage?
Yes, don't use -o local. virt-v2v has an -o rhev option which will import directly from VMware to RHEV or oVirt. Please see the manual: http://libguestfs.org/virt-v2v.1.html#convert-from-vmware-to-rhev-m-ovirt http://libguestfs.org/virt-v2v.1.html#output-to-rhev Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com virt-top is 'top' for virtual machines. Tiny program with many powerful monitoring features, net stats, disk stats, logging, etc. http://people.redhat.com/~rjones/virt-top