How to fix OVF Deployment Failed deviceImage-0.iso was not found error vmware

The error had me  troubleshooting for a  couple of hours. Every solution which  I tried finished with the same error which couldn’t find  ISO file named deviceImage. Then  I extract the OVA file with “7zip” on windows.

If  you check  your  OVF  file, you ‘ll  observe  these  lines;

<Item ovf:required=”false”>
<rasd:ElementName>CD/DVD drive 1</rasd:ElementName>

The problem when you import OVF file, It’ll check  vmware.cdrom.iso and it fails couldn’t find ISO.

I’ll describe  how to fix  this  problem  step by step;

Step 1:Uncompress OVA file using  TAR or  7zip  in windows

Step 2:Locate  your OVF file directory which contains the configuration of the  VM to deploy.

Step 3:Open <your_ovf_name>.ovf  file  and  replace  this line.



Replace  “vmware.cdrom.iso” to  “vmware.cdrom.remotepassthrough”

Last State:


Step 4:Save the  ovf  file and  copy  it  under  a linux server. 

I used linux server to create a manifest file but you can use online site to create SHA1.

For Linux   ;

# sha1sum test.ovf

da39a3ee5e6b4b0d3255bfef95601890afd80709 test.ovf
Copy  “da39a3ee5e6b4b0d3255bfef95601890afd80709”  and edit  MF  file  which  located  under your  OVF configuration folder.

Step 4: Open  <your_ovf_name>.mf  and edit first SHA1 lines which belongs  to the OVF configuration file. 

SHA1(PCI-DSS-RedHat-Server_Template_Last.ovf)= da39a3ee5e6b4b0d3255bfef95601890afd80709
SHA1(PCI-DSS-RedHat-Server_Template_Last-disk1.vmdk)= 264b91281b3adf4a6d6c584ed028d740facabc70
SHA1(PCI-DSS-RedHat-Server_Template_Last-disk2.vmdk)= 30040949162b4c9f3e9bc0352adfff578963184b

Tagged In:

I'm a IT Infrastructure and Operations Architect with extensive experience and administration skills and works for Turk Telekom. I provide hardware and software support for the IT Infrastructure and Operations tasks.

199 Total Posts
Follow Me


  1. забор из сетки рабица прайс лист металлопроката

Leave a Reply