How do I keep vmxnet3 NIC type when exporting to OVF/OVA

[yardie]

Hi,

I exported a VM from my ESXi 4.0.0 server using ovftool for Windows but the type of NIC seems to have been changed as part of the conversion. It was VMXNET3 on the host but ends up being VMXNET in the OVF.

The export was done as follows..

 ovftool --eula@=c:\MyEULA --powerOffSource vi://root:password@esxi4_host/MyVapp d:\dev\vapps\ 

Snippet from the original .vmx

ethernet0.virtualDev = "vmxnet3"

Snippet from the .ovf that was generated

   <VirtualHardwareSection>
...snip..
      <Item>
        <rasd:AddressOnParent>7</rasd:AddressOnParent>
        <rasd:AutomaticAllocation>true</rasd:AutomaticAllocation>
        <rasd:Connection>VM Network</rasd:Connection>
        <rasd:Description>VmxNet ethernet adapter on "VM Network"</rasd:Description>
        <rasd:ElementName>ethernet0</rasd:ElementName>
        <rasd:InstanceID>6</rasd:InstanceID>
        <rasd:ResourceSubType>VmxNet</rasd:ResourceSubType>
        <rasd:ResourceType>10</rasd:ResourceType>
...snip..
    </VirtualHardwareSection>

Is this a known issue ? Any workarounds ?

[admin · Accepted solution]

This is a know issue and is fixed in the next version of ovftool.

A work around is to open up the OVF file find the nic change the resourceSubType from

 <rasd:ResourceSubType>VmxNet</rasd:ResourceSubType>

to

 <rasd:ResourceSubType>VmxNet3</rasd:ResourceSubType>

You should also delete the .mf file after you have edit the OVF file.

hope this helps.

eske

[yardie]

This is a know issue and is fixed in the next version of ovftool.

Any idea when the new version will be made available ?

A work around is to open up the OVF file find the nic change the resourceSubType

Thanks that worked.

You should also delete the .mf file after you have edit the OVF file.

ok. I still wanted the .vmdk validity to be checked so I just put an updated sha1sum of the new .ovf back into the .mf and that worked fine as well.

[tomiii]

ovftool 2.1.0 on linux still drops the 3 when I export my VMs. Which version of ovftool has this issue fixed?

Thanks!

Tom.III