That ovf contains a vApp with 6 VMs :
"vpodrouter v3"
"esx-01a"
"vnx-blk-02-gold"
"vc-w8-01a"
"esx-02a"
"vnxf-01a"
I doubt that this is supported in Workstation or with the ovf-tool that is buildin to WS.
Do you have these vmdks ?
"HOL01-VSI-VAAI-v11-disk1.vmdk"
"HOL01-VSI-VAAI-v11-disk2.vmdk"
"HOL01-VSI-VAAI-v11-disk3.vmdk"
"HOL01-VSI-VAAI-v11-disk4.vmdk"
"HOL01-VSI-VAAI-v11-disk5.vmdk"
"HOL01-VSI-VAAI-v11-disk6.vmdk"
"HOL01-VSI-VAAI-v11-disk7.vmdk"
"HOL01-VSI-VAAI-v11-disk8.vmdk"
If yes - then create the vmx-files manually - the info to do that is inside the ovf
Hi uli
If I do them all one by one they are working so it's something more basic
VMware Communities<http://communities.vmware.com/index.jspa>
cannot import an ovf
reply from Ulli Hankeln<http://communities.vmware.com/people/continuum> in VMware Workstation - View the full discussion<http://communities.vmware.com/message/2133305#2133305
Lol - you are right - it is very basic 😉
This xml element is not supported in WS: VirtualSystemCollection
It does not work here either - try the latest OVF-tool 3 - or just assemble the VMs manually if you are in a hurry
http://www.vmware.com/support/developer/ovf/
So how can it bypassed
VMware Communities<http://communities.vmware.com/index.jspa>
cannot import an ovf
reply from Ulli Hankeln<http://communities.vmware.com/people/continuum> in VMware Workstation - View the full discussion<http://communities.vmware.com/message/2133308#2133308
example:
<VirtualSystem ovf:id="esx-02a">
<Info>A virtual machine</Info>
<Name>esx-02a</Name>
....
<OperatingSystemSection ovf:id="102" ovf:version="5" vmw:osType="vmkernel5Guest">
<Info>The kind of installed guest operating system</Info>
<Description>VMware ESXi 5.x</Description>
</OperatingSystemSection>
<VirtualHardwareSection>
<Info>Virtual hardware requirements</Info>
<System>
<vssd:ElementName>Virtual Hardware Family</vssd:ElementName>
<vssd:InstanceID>0</vssd:InstanceID>
<vssd:VirtualSystemIdentifier>esx-02a</vssd:VirtualSystemIdentifier>
<vssd:VirtualSystemType>vmx-09</vssd:VirtualSystemType>
</System>
this translates to the following lines in the vmx-file :esx-02a.vmx
guestOS = "vmkernel5"
virtualHW.version = "9"