Error OVF Deployment Failed: File ds:

Estaba teniendo un error en la exportación de una maquina virtual. El error se origina cuando esta instalado el vmware tools en la maquina virtual, o esta montada la unidad instaladora de vmware tools (Una iso en el cdrom de la maquina virtual).

Entonces lo que hay que hacer según la kb de vmware, es lo siguiente:
https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2034422

1. Editar la maquina virtual, clic derecho -> Edit Settings. 
2. Clic en CD/DVD drive 1, y en el apartado Device Type seleccionar Client Device. 
3. Clic en Ok.
4. Exportar la maquina virtual. Seleccionar la maquina virtual y clic en File -> Export -> Export OVF template.
5. Guardarla en algún lugar.
6. Ir a la carpeta guardada. Abra el archivo OVF en un editor de texto y confirme que la entrada ResourceSubType CD-ROM está configurado vmware.cdrom.remotepassthrough .
7. Despues para importarla, clic en File -> Deploy OVF Template.
8. Seleccionas la ubicacion del OVF y le das import.

Deploying an OVF fails on vCenter Server 5.1/5.5 when VMware tools are installed(2034422)

Symptoms

• Deploying an OVF fails on vCenter Server 5.1/5.5 when VMware Tools are installed.
• When deploying an OVF from a virtual machine that has VMware Tools installed, you see the error:
  
  OVF Deployment Failed: File ds:///vmfs/volumes/uuid/_deviceImage-0.iso was not found
  
  Where uuid is the datastore ID where the OVF is being deployed.

Cause

This issue occurs when the VMware Tools installation task is not finished. The guest operating system may already have the Tools successfully installed and running, but the ESX task for installing the tools has not finished.

In vSphere 5.0 and earlier, device backings (what the device is connected to) were not exported. OVF files generated on ESX 5.0 and earlier do not contain the device backing information and therefore do not encounter this issue when importing on ESX 5.1/5.5.

In vSphere 5.1/5.5, virtual machines device backing information is exported. When the Tools install task has not finished it leaves the virtual machine's CD-ROM device connected to a datastore ISO image that cannot be accessed upon re-deployment of the OVF to a new virtual machine, which causes the error.

Resolution

To resolve this issue,  modify the SHA1 checksum value in the MyVM.mf file to match the SHA1 checksum value in the MyVM.ovf file.

To modify the SHA1 checksum value in the MyVM.mf file to match the SHA1 checksum value in the MyVM.ovf file:

1. Right-click the virtual machine and click Guest > End VMware Tools Install.
2. Export the virtual machine to a new OVF file.
3. Open the OVF file in a text editor and confirm that the CD-ROM ResourceSubType entry is set to vmware.cdrom.remotepassthrough.
   
   For example:
   
   <Item ovf:required="false">
   <rasd:AddressOnParent>0</rasd:AddressOnParent>
   <rasd:AutomaticAllocation>false</rasd:AutomaticAllocation>
   <rasd:ElementName>CD-ROM 1</rasd:ElementName>
   <rasd:InstanceID>9</rasd:InstanceID>
   <rasd:Parent>4</rasd:Parent>
   <rasd:ResourceSubType>vmware.cdrom.remotepassthrough</rasd:ResourceSubType><rasd:ResourceType>15</rasd:ResourceType>
   <vmw:Config ovf:required="false" vmw:key="backing.exclusive" vmw:value="false" />
   <vmw:Config ovf:required="false" vmw:key="connectable.allowGuestControl" vmw:value="true" />
   </Item>
   
   Note: When the ResourceSubType value is set to vmware.cdrom.iso, deploying the OVF fails and you see the error. Also, verify that the CD-ROM device is disconnected under the virtual machine settings.
4. To view the SHA1 checksum value in the MyVM.ovf file, run the command:
   
   sha1sum MyVM.ovf
5. Modify the SHA1 checksum value in the MyVM.mf file to match the SHA1 checksum value in the MyVM.ovf file.