Seems like engines tries to validate a vNic with an empty MAC address and fails on that. The fact that in the direct flow it works sounds weird to me: either we loose the MAC in one flow or we do not validate it in the other one.

Kun, could you please send (in private if you like) the OVF file from the input tarball you've used, so we'd be able to debug the case more thoroughly?

Regards,
Yevgeny

On Thu, Jan 5, 2017 at 10:03 AM, Kun Wei <kuwei@redhat.com> wrote:

Hi,shavivi.

Thank you .Yes,as you know i can import ova directly and it can be import successful.

But  i am testing v2v now  and  i want to confirm if it is a new bug.



----- Original Message -----
From: "Shahar Havivi" <shavivi@redhat.com>
To: "Kun Wei" <kuwei@redhat.com>, "Yevgeny Zaspitsky" <yzaspits@redhat.com>
Cc: "users" <users@ovirt.org>, "Tingting Zheng" <tzheng@redhat.com>, "Ming Xie" <mxie@redhat.com>
Sent: Thursday, January 5, 2017 3:05:45 PM
Subject: Re: Import guest at rhv4.0.6 failed after convert a regular ova file by virt-v2v

Yevgeny, please look why it fails on "isMacInRange"

Kun, you know that you can import ova directly instead of using virt-v2v to
export domain and then import to data domain,
you can do that from the VMs tab->Import-> and change the source to OVA.

On Thu, Jan 5, 2017 at 4:35 AM, Kun Wei <kuwei@redhat.com> wrote:

>
> Hi,  I want to confirm a questions if it is a bug,or if something wrong
> with me.Thanks
>
> When i convert a ova guest file to rhv4.0.6 by virt-v2v,but import is
> failed.The attachment are engine.log and vdsm.log.
>
>
>
> Version:
> libguestfs-1.32.7-3.el7_3.2.x86_64
> virt-v2v-1.32.7-3.el7_3.2.x86_64
> qemu-img-rhev-2.6.0-28.el7_3.2.x86_64
> libvirt-2.0.0-10.el7_3.3.x86_64
> rhv4.0: 4.0.6.3
>
> Steps :
> 1:Prepare a regular ova file guest .
> 2:Use virt-v2v to convert the ova file to rhv4.0.
> # virt-v2v -i ova esx-rhel6.8-vmdkgz.tar -o rhev -os 10.73.131.93:/home/nfs_export
> -of qcow2
> [   0.0] Opening the source -i ova esx-rhel6.8-vmdkgz.tar
> [  44.1] Creating an overlay to protect the source from being modified
> [  45.0] Initializing the target -o rhev -os 10.73.131.93:/home/nfs_export
> [  45.3] Opening the overlay
> [  53.1] Inspecting the overlay
> [  70.2] Checking for sufficient free disk space in the guest
> [  70.2] Estimating space required on target for each disk
> [  70.2] Converting Red Hat Enterprise Linux Server release 6.8 (Santiago)
> to run on KVM
> virt-v2v: This guest has virtio drivers installed.
> [ 215.6] Mapping filesystem data to avoid copying unused and blank areas
> [ 216.0] Closing the overlay
> [ 217.2] Checking if the guest needs BIOS or UEFI to boot
> [ 217.2] Assigning disks to buses
> [ 217.2] Copying disk 1/1 to /tmp/v2v.8kDoXb/908b80fa-09a6-
> 4827-8e0a-a6a54520f685/images/47a1919e-1914-44b4-920f-
> b8e208fa4bc1/da74f1c3-8f43-4a15-934a-bb9d380615c3 (qcow2)
>     (100.00/100%)
> [ 254.6] Creating output metadata
> [ 254.7] Finishing off
> 3.Then login rhv4.0 and try to import the guest from export domain to data
> domain after finishing the conversion.But it is failed with the
> error:"Failed to import Vm rhel6u8 to Data Center Default, Cluster Default"
> as appendix picture.
>
> -Additional info :
> I can import a guest from kvm or vmware.Only can not import this way.
>
>
> -
> Best Regards,
> Kun Wei
>
>
>