I have a VM that I exported as an OVA as a "Just in Case" backup a while ago.  Today I had to use it and I cannot import it.

There was an ISO mounted when I did the export and it exported the ISO as well.  The error I get is when it tries to access the ISO, it fails.

I downloaded OVFtool in the hopes I could strip the ISO from the OVA, but I am getting an error trying to use the --noImageFiles option.  it tells me:

Is it possible to remove this ISO?

After searching through the forum I uninstalled OVFtool from my E: drive and put it on C: with the same result.  Here is the logToConsole:

E:\ESX\OVA's>ovftool --X:logToConsole Win7-Tax64.ova test.ova

2012-03-09T17:08:08.405-05:00 [08672 verbose 'Default'] Subscribing to signal: 2

(SIGINT)

2012-03-09T17:08:08.405-05:00 [08672 verbose 'Default'] Subscribing to signal: 4

(SIGILL)

2012-03-09T17:08:08.405-05:00 [08672 verbose 'Default'] Subscribing to signal: 2

2 (SIGABRT)

2012-03-09T17:08:08.405-05:00 [08672 verbose 'Default'] Subscribing to signal: 8

(SIGFPE)

2012-03-09T17:08:08.405-05:00 [08672 verbose 'Default'] Subscribing to signal: 1

5 (SIGTERM)

2012-03-09T17:08:08.406-05:00 [08672 verbose 'Default'] [ovfTool.cpp] Using home

directory C:\Users\ItsTooHot\AppData\Roaming\VMware\ovftool.cfg

2012-03-09T17:08:08.406-05:00 [08672 verbose 'Default'] [ovfTool.cpp] OvfTool En

vironment:

--> /X:httpTimeout = "600"

--> /X:imageReadSize = "262144"

--> /X:logToConsole = "true"

--> /X:maxNumberOfTermSignals = "5"

--> /X:maxRedirects = "256"

--> /X:maximalDeltaConfSize = "8"

--> /X:maximalDeltaTreeSize = "6"

--> /X:progressSmoothing = "60"

--> /X:useMacNaming = "false"

--> /X:vCloudKeepTemplate = "true"

--> /X:vCloudTimeout = "3600"

--> /X:vimSessionTimeout = "600"

--> /authdPortSource = "902"

--> /authdPortTarget = "902"

--> /fencedMode = "bridged"

--> /prgPath = "C:\Program Files\VMware\VMware OVF Tool"

--> /source = "Win7-Tax64.ova"

--> /target = "test.ova"

-->

2012-03-09T17:08:08.412-05:00 [08672 verbose 'Default'] [ovfTool.cpp] Done initi

alizing libs

2012-03-09T17:08:08.412-05:00 [08672 verbose 'Default'] [ovfTool.cpp] Determinin

g source

2012-03-09T17:08:08.412-05:00 [08672 verbose 'Default'] [ovfTool.cpp] Determinin

g target

Opening OVA source: Win7-Tax64.ova

2012-03-09T17:08:08.479-05:00 [08672 verbose 'Default'] OVF Descriptor: <?xml ve

rsion="1.0" encoding="UTF-8"?>

--> <!--Generated by VMware VirtualCenter Server, User: ItsTooHot, UTC time: 201

2-03-02T23:49:58.21025Z-->

--> <Envelope vmw:buildId="build-345043" xmlns="http://schemas.dmtf.org/ovf/enve

lope/1" xmlns:cim="http://schemas.dmtf.org/wbem/wscim/1/common" xmlns:ovf="http:

//schemas.dmtf.org/ovf/envelope/1" xmlns:rasd="http://schemas.dmtf.org/wbem/wsci

m/1/cim-schema/2/CIM_ResourceAllocationSettingData" xmlns:vmw="http://www.vmware

.com/schema/ovf" xmlns:vssd="http://schemas.dmtf.org/wbem/wscim/1/cim-schema/2/C

IM_VirtualSystemSettingData" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instanc

e">

-->   <References>

-->     <File ovf:href="Win7-Tax64-disk1.vmdk" ovf:id="file1" ovf:size="80291440

64" />

-->     <File ovf:href="Win7-Tax64-file1.iso" ovf:id="file2" ovf:size="331949670

4" />

-->   </References>

-->   <DiskSection>

-->     <Info>Virtual disk information</Info>

-->     <Disk ovf:capacity="70" ovf:capacityAllocationUnits="byte * 2^30" ovf:di

skId="vmdisk1" ovf:fileRef="file1" ovf:format="http://www.vmware.com/interfaces/

specifications/vmdk.html#streamOptimized" ovf:populatedSize="18292015104" />

-->   </DiskSection>

-->   <NetworkSection>

-->     <Info>The list of logical networks</Info>

-->     <Network ovf:name="VM Network">

-->       <Description>The VM Network network</Description>

-->     </Network>

-->   </NetworkSection>

-->   <VirtualSystem ovf:id="Win7-Tax64">

-->     <Info>A virtual machine</Info>

-->     <Name>Win7-Tax64</Name>

-->     <OperatingSystemSection ovf:id="1" vmw:osType="windows7_64Guest">

-->       <Info>The kind of installed guest operating system</Info>

-->       <Description>Microsoft Windows 7 (64-bit)</Description>

-->     </OperatingSystemSection>

-->     <VirtualHardwareSection>

-->       <Info>Virtual hardware requirements</Info>

-->       <System>

-->         <vssd:ElementName>Virtual Hardware Family</vssd:ElementName>

-->         <vssd:InstanceID>0</vssd:InstanceID>

-->         <vssd:VirtualSystemIdentifier>Win7-Tax64</vssd:VirtualSystemIdentifi

er>

-->         <vssd:VirtualSystemType>vmx-07</vssd:VirtualSystemType>

-->       </System>

-->       <Item>

-->         <rasd:AllocationUnits>hertz * 10^6</rasd:AllocationUnits>

-->         <rasd:Description>Number of Virtual CPUs</rasd:Description>

-->         <rasd:ElementName>2 virtual CPU(s)</rasd:ElementName>

-->         <rasd:InstanceID>1</rasd:InstanceID>

-->         <rasd:ResourceType>3</rasd:ResourceType>

-->         <rasd:VirtualQuantity>2</rasd:VirtualQuantity>

-->       </Item>

-->       <Item>

-->         <rasd:AllocationUnits>byte * 2^20</rasd:AllocationUnits>

-->         <rasd:Description>Memory Size</rasd:Description>

-->         <rasd:ElementName>2048MB of memory</rasd:ElementName>

-->         <rasd:InstanceID>2</rasd:InstanceID>

-->         <rasd:ResourceType>4</rasd:ResourceType>

-->         <rasd:VirtualQuantity>2048</rasd:VirtualQuantity>

-->       </Item>

-->       <Item>

-->         <rasd:Address>0</rasd:Address>

-->         <rasd:Description>SCSI Controller</rasd:Description>

-->         <rasd:ElementName>SCSI controller 0</rasd:ElementName>

-->         <rasd:InstanceID>3</rasd:InstanceID>

-->         <rasd:ResourceSubType>lsilogicsas</rasd:ResourceSubType>

-->         <rasd:ResourceType>6</rasd:ResourceType>

-->       </Item>

-->       <Item>

-->         <rasd:Address>1</rasd:Address>

-->         <rasd:Description>IDE Controller</rasd:Description>

-->         <rasd:ElementName>IDE 1</rasd:ElementName>

-->         <rasd:InstanceID>4</rasd:InstanceID>

-->         <rasd:ResourceType>5</rasd:ResourceType>

-->       </Item>

-->       <Item>

-->         <rasd:Address>0</rasd:Address>

-->         <rasd:Description>IDE Controller</rasd:Description>

-->         <rasd:ElementName>IDE 0</rasd:ElementName>

-->         <rasd:InstanceID>5</rasd:InstanceID>

-->         <rasd:ResourceType>5</rasd:ResourceType>

-->       </Item>

-->       <Item>

-->         <rasd:AddressOnParent>0</rasd:AddressOnParent>

-->         <rasd:ElementName>Hard disk 1</rasd:ElementName>

-->         <rasd:HostResource>ovf:/disk/vmdisk1</rasd:HostResource>

-->         <rasd:InstanceID>6</rasd:InstanceID>

-->         <rasd:Parent>3</rasd:Parent>

-->         <rasd:ResourceType>17</rasd:ResourceType>

-->       </Item>

-->       <Item>

-->         <rasd:AddressOnParent>0</rasd:AddressOnParent>

-->         <rasd:AutomaticAllocation>true</rasd:AutomaticAllocation>

-->         <rasd:ElementName>CD/DVD Drive 1</rasd:ElementName>

-->         <rasd:HostResource>ovf:/file/file2</rasd:HostResource>

-->         <rasd:InstanceID>7</rasd:InstanceID>

-->         <rasd:Parent>4</rasd:Parent>

-->         <rasd:ResourceType>15</rasd:ResourceType>

-->       </Item>

-->       <Item>

-->         <rasd:AddressOnParent>7</rasd:AddressOnParent>

-->         <rasd:AutomaticAllocation>true</rasd:AutomaticAllocation>

-->         <rasd:Connection>VM Network</rasd:Connection>

-->         <rasd:Description>E1000 ethernet adapter on "VM Network"</rasd:Descr

iption>

-->         <rasd:ElementName>Network adapter 1</rasd:ElementName>

-->         <rasd:InstanceID>8</rasd:InstanceID>

-->         <rasd:ResourceSubType>E1000</rasd:ResourceSubType>

-->         <rasd:ResourceType>10</rasd:ResourceType>

-->       </Item>

-->     </VirtualHardwareSection>

-->   </VirtualSystem>

--> </Envelope>

Opening OVA target: test.ova

2012-03-09T17:08:08.490-05:00 [08672 verbose 'Default'] Closing writer. Locator:

test.ovf (SHA1: 352f265785c162cd8bf180f257a7876dbacf34c4, Written bytes: 4962)

2012-03-09T17:08:08.491-05:00 [08672 verbose 'Default'] Closing writer. Locator:

test.mf (SHA1: 05aeacecbe7778a0bfa4bc10ab9f6e6fc713aaa9, Written bytes: 184)

Writing OVA package: test.ova

2012-03-09T17:08:08.492-05:00 [08672 verbose 'Default'] Using file size as progr

ess measure

Disk Transfer Failed

Error: Invalid access to memory location.

2012-03-09T17:08:08.495-05:00 [08672 verbose 'Default'] Backtrace:

--> backtrace[00] rip 000000000047693a (no symbol)

--> backtrace[01] rip 000000000034d008 (no symbol)

--> backtrace[02] rip 000000000034dc1e (no symbol)

--> backtrace[03] rip 00000000003011cb (no symbol)

--> backtrace[04] rip 0000000000475df3 (no symbol)

--> backtrace[05] rip 000000000048a2fc (no symbol)

--> backtrace[06] rip 000000014001d7ab (no symbol)

--> backtrace[07] rip 000000014009b945 (no symbol)

--> backtrace[08] rip 000000014009ce71 (no symbol)

--> backtrace[09] rip 0000000140022137 (no symbol)

--> backtrace[10] rip 0000000140049b91 (no symbol)

--> backtrace[11] rip 000000014007e8b2 (no symbol)

--> backtrace[12] rip 000000014007ed6d (no symbol)

--> backtrace[13] rip 000000014001af6f (no symbol)

--> backtrace[14] rip 000000014001b76a (no symbol)

--> backtrace[15] rip 000000014025f62e (no symbol)

--> backtrace[16] rip 0000000076d9652d (no symbol)

--> backtrace[17] rip 00000000770dc521 (no symbol)

-->

2012-03-09T17:08:08.496-05:00 [08672 verbose 'Default'] Deleting file: test.ova

Completed with errors

E:\ESX\OVA's>

Hi Everyone,

I was trying to deploy a VM using the ovftool, I thought I would use the properties which are thrown from a "probe" of the OVA file.

ovftool http://server/files/builds/vpas/6.0.0/latest/vPAS-installer.ova

Properties:

  ClassId:     vami

  Key:         gateway

  InstanceId   vPAS

  Category:    Networking Properties

  Label:       Default Gateway

  Type:        string

  Description: The default gateway address for this VM. Leave blank if DHCP is

               desired.

  ClassId:     vami

  Key:         DNS

  InstanceId   vPAS

  Category:    Networking Properties

  Label:       DNS

  Type:        string

  Description: The domain name servers for this VM (comma separated). Leave

               blank if DHCP is desired.

  ClassId:     vami

  Key:         ip0

  InstanceId   vPAS

  Category:    Networking Properties

  Label:       Network 1 IP Address

  Type:        string

  Description: The IP address for this interface. Leave blank if DHCP is

               desired.

  ClassId:     vami

  Key:         netmask0

  InstanceId   vPAS

  Category:    Networking Properties

  Label:       Network 1 Netmask

  Type:        string

After having made sure that such properties exists from the probe, I tried to use them to give the VM a static IP post deployment, automatically.

ovftool --datastore="31_datastore" --acceptAllEulas --ipAllocationPolicy=fixedPolicy --name="vPAS_31_1" --powerOn --prop:ip0="172.16.121.115" --prop:netmask0="255.255.0.0" --prop:DNS="172.16.1.10" --prop:gateway="172.16.1.1" http://server/vpas/6.0.0/latest/vPAS-installer.ova vi://root:password@172.16.121.31/

Opening OVA source: http://server/files/builds/vpas/6.0.0/latest/vPAS-installer.ova

The manifest validates

Opening VI target: vi://root@172.16.121.31:443/

Deploying to VI: vi://root@172.16.121.31:443/

Transfer Completed                   

Powering on VM: vPAS_31_1

Warning:

- OVF property with key: 'DNS' does not exists.

- OVF property with key: 'gateway' does not exists.

- OVF property with key: 'ip0' does not exists.

- OVF property with key: 'netmask0' does not exists.

Completed successfully

Can someone please explain me whether this is a common problem ( from VMware ) or something I am doing wrong?

Thanks,

From virtualmachine i have exported .ovf file from the following website http://www.techrepublic.com/blog/windows-and-office/how-do-i-convert-virtualbox-files-to-work-with-vmware-workstation/#.

and i recieved the following error in cmd prompt.

can anyone please help me to understand error line 84 and prove me solution .

........................................................................................

Error:

- Line 84: Could not parse the document: 'mismatched tag'

Warning:

- No manifest file found.

Completed with errors.

---------------------------------------------------------------------------------------

Steps followed:

Step 1: Export your virtual machine

The first step is to export your virtual machine from VirtualBox.

Step 2: Editing your .ovf file

The file you need to edit will be the .ovf file that serves as the descriptor for your virtual machine. You MUST open this in a text editor. Do NOT open it in a word processor as this will add extra characters to the file, which will render it unreadable by either VirtualBox or VMWare. The first section you need to edit is the format section. Look for a line of code (near the top) that contains this phrase:

ovf:format=

What follows that section needs to be changed to:

"http://www.vmware.com/interfaces/specifications/vmdk.html#streamOptimized"

The next edit (in the same file) is the Virtual SystemType, and it must be one of the following:

<vssd:VirtualSystemType>vmx-07</vssd:VirtualSystemType> (for a esx 4.0)

<vssd:VirtualSystemType>vmx-04</vssd:VirtualSystemType> (for esx 3.5.x and 4.0 hosts)

Believe it or not, the next item to edit is the rsad for the sound card. The section will look similar to:

<Item>

<rasd:Caption>sound</rasd:Caption>

<rasd:Description>Sound Card</rasd:Description>

<rasd:InstanceId>6</rasd:InstanceId>

<rasd:ResourceType>35</rasd:ResourceType>

<rasd:ResourceSubType>ensoniq1371</rasd:ResourceSubType>

<rasd:AutomaticAllocation>false</rasd:AutomaticAllocation>

<rasd:AddressOnParent>3</rasd:AddressOnParent>

</Item>

To the above section, add the following after the first <Item> tag:

<Item ovf:required="false">

Step 3: Using the OVF tool

This step requires you to download and install the VMWare OVF Tool (you will have to log in first). The OVF tool is command-line only, and it will convert your newly prepped .ovf file into a .vmx that VMWare can use. To do this, follow these steps:

• Click Start | Run.
• Type cmd.
• In the command window, change to the directory you installed the OVF Tool into and then issue the command:ovftool appliance.ovf new_appliance.vmx(Where appliance.ovf is the name of the appliance you exported from VirtualBox and new_appliance.vmx is the name you want to give the new virtual appliance. Depending on the size of your virtual appliance, this could take a while.)

Hi,

I am trying to deploy an. ova file using ovftool with the following command :

C:\Program Files (x86)\VMware\VMware OVF Tool>ovftool -ds=<datastore> --net:"VM Network
"=standard_trunk --net:"VM Network 2"=standard_trunk -n=g1 <<MYOVA.ova>> vi://username:password@<IPaddr>
Opening OVA source: vwlc.ova
The manifest validates
Opening VI target: vi://root@10.50.16.36:443/
Deploying to VI: vi://root@10.50.16.36:443/
Progress: 59%

Removing temporary objects and files

Transfer Failed

Error: Execution aborted

Error: Operation was canceled

Completed with errors

And it aborts with the above error.

Can anyone help me out.

Hi,

Can someone provide an indication on what is generating the following error when running ovftool to deploy a vm on a host in a vCenter?

Opening OVA source: /usr/local/path/to/ova/file.ova

The manifest validates

Opening VI target: vi://user@vCenter_ip:443/

Deploying to VI: vi://user@vCenter_ip:443/

^MTransfer Failed

^MTransfer Failed

Error: Failed to send http data

Completed with errors

The error reproduced on client setup to which I don't have access so I have no other additional logs.

Thanks.

Hi,

I am trying to deploy OVA using ovftool. I see the option --network and --net available for selecting the network by name, though I was not able to find a way to assign a static IP in the ovftool command itself. Something like --ip0=10.10.10.10. Is there a way we can do this? From UI when we deploy an OVA, we have provision to provide IP, Gateway, Netmask and DNS.

Thanks

Hi All,

I have just come across ovftool and was giving a try to it. I am fairly new to VMware world.

I have a  .OVF which I exported using vSphere client 4.0. This .OVF comprises of 3 Suse Linux based virtual machines. i.e. I created a vApp on ESX (4.1) host, in this vApp I put my 3 SLES VMs and then exported it as OVF.

It has a total size of around 4.5GB.

Now I ran this command to compress this .OVF as well as gave an option to create deltadisks.

C:\> ovftool --compress=9 --makeDeltaDisks --skipManifestCheck  MyVMCluster\MyVMCluster.ovf   E:\

output:

{{{

The manifest does not validate
Generating delta disks for 2 disks (capacity 40960 MB)
Reading disks
Disk Transfer Completed

Determining optimal configuration for capacity group
Writing configuration to disk
Disk Transfer Completed

Completed successfully

}}}

Now when I checked my E:\ It had created a folder with the same name and put related files there. I saw a significant reduction in the new vmdk size. ( around 2.3GB now )

Now when I manually deploy this new ovf on vSphere client, it goes till certain %age and then flags an error:

{{{

Error uploading file to server ( E:\MyVMCluster\disk3.vmdk.gz ) Not a supported disk format ( Invalid sparse vmdk header )

}}}

and then it stops and everything rolledback.

Any pointers ?

Thanks

Nikunj

Hi,

is it possible to include the nvram-file in the OVF-File oder how to tranport BIOS-Settings with OVF.

regards.

Hans-Peter

TAM, EMEA-Central

VMware

Hello

I installed ovftool on SLES 11 SP1 but when I try to use it....says Error: Locale Initialization Failed =(

Hi to all,

with a deploy of 5.90 GB ovf file I'm spending a lot of time. I'm using the ovftool.bin inside ESXi 6.5 and I would like to try the latest version of ovftool, where I can download it for ESXi OS?

Regards

I am trying to deploy OVA via OVF tool.

The OVA has two network mappings, Out of Band Management and Public.

I entered the following for the deployment.

ovftool --acceptAllEulas --name=test -dm=thin -ds="datastore1" --net: "Out of Band Management"="VM Network" --net: "Public"="VM Network" "C:\Users\ki\Downloads\Daily Downloads\xxx.ova" vi://root@135.27.x.x

Then the following error is thrown.

Error: Unexpected option: Public=VM Network

Completed with errors

I think I followed the rule for multiple network mapping in the OVF Tool User's Guide.

Sets a network assignment in the deployed OVF package. For example, --net:=. OVF packages contain symbolic names for network names which are assigned with this option. For multiple network mappings, repeat the option, separating them with a space for example, --net:s1=t1 --net:s2=t2 --net:s3=t3.

What might cause the error?

Please advise.

Is there a way to map multiple datastores when moving VMs with ovftool?   People have been asking for this for years:

https://www.reddit.com/r/vmware/comments/50zt10/deploy_ovf_in_multiple_datastores/

https://communities.vmware.com/message/1659941#1659941

https://www.reddit.com/r/vmware/comments/dysc0w/ovftool_with_multiple_datastores/

"I would have expected an ovftool option like --datastore:sourcename=targetname similar to --net:s1=t1"

Can someone from vmware make this a feature request?

Just doing some testing with ovftool 4.3 and vsphere 6.7 and I'm seeing a change in functionality compared with ovftool 4.1 and vsphere 6.0.

Previously we were able to import vms using indentical vm names by specifying the --vmFolder option on the import task, with 4.3 and 6.7 this doesnt appear to working and a duplicate vm warning is returned with a sugestion to user the --override switch, which if used then overwrites the existing vm.

Example:

ovftool --noImageFiles --acceptAllEulas --X:logFile=ovf.log --X:logLevel=verbose --noSSLVerify --allowExtraConfig --exportFlags=extraconfig,uuid,mac --I:morefArgs --datastore=vim.Datastore:datastore-126 --vmFolder=vim.Folder:group-v325 --diskMode=thin --net:vlan1310=vim.Network:network-142 --name=xyz /xyz.ova vi://user:password@VC/DC/host/CLUSTER

Error: Duplicate name 'xyz' on target. Use --overwrite option to delete it.

The first import does work correctly and the vm ends up in the specified vm folder object, its the subsequent imports using an indetically named vm to one that already exists in the inventory but targetting a different vm folder object then cause the issue.

After upgrading to ovftool v4.4, ovftool started breaking on a specific ExtraConfig parameter. It seems to be working correctly with all other ExtraConfigs, but adding a specific entry is causing it to break.

With a standard set of ExtraConfig parameters specified in envoy-proxy-bae.ovf. Conversion to OVA goes through perfectly.

<vmw:ExtraConfig ovf:required="true" vmw:key="guest.command.enabled" vmw:value="false"/>

```

ubuntu@cdm-node:~$ ovftool --allowAllExtraConfig envoy-proxy-base.ovf test.ova

Opening OVF source: envoy-proxy-base.ovf

The manifest validates

Opening OVA target: test.ova

Writing OVA package: test.ova

Transfer Completed

Warning:

- Wrong file size specified in OVF descriptor for 'envoy-proxy-base-1.vmdk' (specified: -1, actual 910012416).

Completed successfully

```

However, when we add the following entry to the list of ExtraConfigs, ovftool fails.

<vmw:ExtraConfig ovf:required="true" vmw:key="sched.mem.pin" vmw:value="true"/>

```

ubuntu@cdm-node:~$ ovftool --allowExtraConfig envoy-proxy-base.ovf test.ova

Opening OVF source: envoy-proxy-base.ovf

The manifest validates

Error: OVF Package is not supported by target:

- Line -1: Unsupported value 'sched.mem.pin' for attribute 'key' on element 'ExtraConfig'.

Completed with errors

```

Why is this specific ExtraConfig breaking ovftool? Is there something different about the naming that is causing the issue? Why do we only see this issue when this specific ExtraConfig is added to the ovf?

We have a specific folder used for certain vm's that I need to deploy to.


As an example I can view the current list of vm's with:


ovftool vi://myadmin:mypass@ourvcenter/DATACENTER/vm/myvms

Error: Found wrong kind of object (Folder). Possible completions are:
vmname1
vmname2
vmname3
　


Now let’s say I want to import an ovf to myvms/vmname4 I get a "Locator does not refer to an object" error.


ovftool --datastore=mydatastore --network=mynetwork vi://myadmin:mypass@ourvcenter/DATACENTER/vm/myvms/vmname4 newvm.ovf

Opening VI source: vi://myadmin:mypass@ourvcenter/DATACENTER/vm/myvms/vmname4
Error: Locator does not refer to an object: vi://myadmin:mypass@ourvcenter/DATACENTER/vm/myvms/vmname4
Completed with errors


I have tried variations of using —name and —vmfolder and changing the vi: path without success.


I can import directly to esxi and to host through vcenter but we are then having to go back into vcenter to move these vms to the correct folder.


Is there a way to get this into the "right" place up front?

Hi All,

Please help me as I am trying to deploy my OVF in an esxi and I get the following error

"Failed to deploy OVF package: File ds:///vmfs/volumes/546b400f-680d4bc0-11f7-001517d3b60c/_deviceImage-0.iso was not found"

I don't know if I am correct if i deduce that the export might have an iso image mounted on it and now it can't locate it?

I exported the OVF from esxi 5.5 and the destination esxi is also 5.5.

I have also attached the screenshot of the error mentioned above.

Please help

Appreciate all the help I could get and thank you in advance

Regards,

I have an OVA which when successfully deployed, comes up with 8 VMs.
I am able to deploy the OVA using vCenter web UI without any issues.
However, when I try and deploy the same OVA using OVFTool, across the exact same cluster using the same networks,
it just remains hung and gets timed out.
Here is the command I use for deployment using OVFTool:

ovftool --overwrite --powerOffTarget --acceptAllEulas --allowExtraConfig -ds=vsanDatastore -n=sros-testmvmgvmware02 --net:"net00"="NET0" --net:"net10"="NET1" --net:"net20"="Test" --net:"net30"="Test" --net:"net31"="Test" --net:"net32"="Test" /home/mvmgvmware02/ovfTemp/sros_vm.ova "vi://administrator@vsphere.local:p@ssW0rd@<IP OF VCENTER>/Comp-Datacenter/host/mvmgvmware02"

and here is the output:
Opening OVA source: /home/mvmgvmware02/ovfTemp/sros_vm.ova
The manifest validates
Opening VI target: vi://administrator%40vsphere.local@<IP>:443/Comp-Datacenter/host/mvmgvmware02
Deploying to VI: vi://administrator%40vsphere.local@<IP>:443/Comp-Datacenter/host/mvmgvmware02

it is stuck at this point.

OVFtool version used: VMware ovftool 4.3.0 (build-10104578)

I am running the OVFtool from a linux server, the version of which is: CentOS release 6.4 

The worse part is that the task of vApp deployment is stuck at 0% and the vApp is in a ghost state. The only way to do any operations, including deleting the entry of vApp in vCenter is to restart the vCenter services. 

Till now I have been using an OVA with 6 VMs, however, in this OVA I have 8 VMs.
Any idea as to why scaling this up by just 2 VMs is causing this problem and that too specifically with the OVFtool as such.

I have tried this with both vCenter 6.5 and 6.7 and the behavior is exactly the same. Is there any limitation on the number of VMs that can be deployed using OVFtool?

Has anyone else faced a similar issue. Any input with regards to this would be much appreciated.

Thanks and Regards,

Antony

Hello everyone, VMware is conducting our annual Developer Survey and we want to hear from YOU so we can assess and improve our developer program to better serve your needs. PLUS, we will be giving away a new Sonos Move smart speaker to one lucky participant! To take the survey, visit the link below:

http://www.vmware.com/go/developer-survey-2019

Thank you!

Hello Guys,

Please, could you help me if your experience in the case below?

I trying to do a deploy from OVF (Application Avaya Equinox), but it is very slow. Today I start the task at 06:06 pm. I checked the status now 10:00 pm and only 4% was completed. Can I do any process to improve it?

This environment is running as HA (3 servers HP).

Vsphere version: 6.5

Thanks,

Danilo Toledo