Error: No network mapping specified. OVF networks: bridged custom. Target networks:

[andreireiand]

looks like by adding:

--net:"bridged"="VM Network" --net:"custom"="Dummy"

this will work - i.e., running this in cli:

Covftool --acceptAllEulas --noSSLVerify --X:useMacNaming=false -dm=thin --name="fs24vm-01" --overwrite -ds="datastore1" --net:"bridged"="VM Network" --net:"custom"="Dummy" "abc.vmx" "vi://root:[email protected]:443//"

was successful. Can this be baked into the provider?

[andreireiand]

looking at the ovftool definition for --net and --network:

https://vdc-download.vmware.com/vmwb-repository/dcr-public/bb505ca7-88b5-4b11-aff4-f59125ab27bc/f3d05149-23e9-4ac2-8f99-0c851a8a5231/ovftool-430-userguide.pdf

looks like --net should be used when multiple NICs are defined within the ovf ... few implementation ideas:

1. either create a "custom parameter" addition to the full command (such that one can specify "--net:a=b" multiple times
2. detect when nics are present and convert --network to multiple --nic:a=b

hope it makes sense

[josenk]

I had so many problems trying to get network mapping stuff working... There was just too many combinations to look for to make it work perfectly for every combination. I prefer to have it working with less compatibility.

https://github.com/josenk/terraform-provider-esxi?tab=readme-ov-file#known-issues-with-vmware_esxi
- Using a local source vmx files should not have any networks configured. There is very limited network interface mapping abilities in ovf_tools for vmx files. It's best to simply clean out all network information from your vmx file. The plugin will add network configuration to the destination vm guest as required.