Thursday, December 17, 2015

ofa to ovf for vmware import follies

let's dance, shall we?

it all started out with:
ResourceType instance ID 3 no support ofr hardware device type 20

from: http://www.itsecurenet.com/virtualbox-ova-to-vsphere-ovf/

How to convert VirtualBox OVA to Vsphere OVF
2. Microsoft Checksum Verify utilityhttp://support.microsoft.com/kb/841290 (Need to check SHA1)
3. Text editor.

First of all, export your virtual machine from Virtualbox. Give the location for the file and save as ova file
VirtualBox Ova Export
After, Install the VMware OVF Tool. I am using the version 3.0.1
Once, the file has been created and the tool is installed.
Open the command line and navigate to the OVF tool folder.
Type the command below : ovftool.exe –lax <source.ova>  <destination.ovf> 
ovftool.exe –lax “C:\Users\ygotame\Desktop\Asterix Now.ova” “C:\Users\ygotame\Desktop\Asterix Now.ovf”
OVF Tool Export
Once the command is complete, you will see three files :
1. Asterix Now.mf  SHA1 Info File
2. Asterix Now.ovf   Configuration file
3. Asterix Now-disk.vmdk   Virtual Hard drive
Now open, Vsphere client and click to deploy ovf file.
vSphere OVF Deploy
Give the OVF file location and try to upload to the server.
You might this error : Unsupported hardware family virtualbox-2.2
Error: OVF Package is not supported by target:
 Line 25: Unsupported hardware family 'virtualbox-2.2'.
vSphere OVF Deploy Family 2.2 ErrorNote : The image is in French
If it is the case for you, open the ovf file with your favorite text editor.
And, change the line :
<vssd:VirtualSystemType>virtualbox-2.2</vssd:VirtualSystemType>
with this
<vssd:VirtualSystemType>vmx-07</vssd:VirtualSystemType>  
To avoid the error message : Line 66: OVF hardware element ‘ResourceType’ with instance ID ‘5’: No support for the virtual hardware device type ’20’
In the same file, modify the item Instance 5:
<Item>
<rasd:Address>0</rasd:Address>
<rasd:Caption>sataController0</rasd:Caption>
<rasd:Description>SATA Controller</rasd:Description>
<rasd:ElementName>sataController0</rasd:ElementName>
<rasd:InstanceID>5</rasd:InstanceID>
<rasd:ResourceSubType>AHCI</rasd:ResourceSubType>
<rasd:ResourceType>20</rasd:ResourceType>
</Item>
With this
<Item>
<rasd:Address>0</rasd:Address>
<rasd:Caption>SCSIController</rasd:Caption>
<rasd:Description>SCSI Controller</rasd:Description>
<rasd:ElementName>SCSIController</rasd:ElementName>
<rasd:InstanceID>5</rasd:InstanceID>
<rasd:ResourceSubType>lsilogic</rasd:ResourceSubType>
<rasd:ResourceType>6</rasd:ResourceType>
</Item>
Save the change and try again to deploy
At this time, you will get the error saying the file fail the control of integrity and could be corrupted. As the vpshere sever check the <file>.mf to verify the integrity. We will modify that to make sure the correct information is enter.
Integrity Error Vsphere
For that, download the Microsoft toll that I mention above and extract the file where you prepare. I will dump it at C:\Temp
Now, we need to find out new SHA1 key for <file>.ovf because we made some change.  Therefore, open command line and navigate to the place where you had extracted the Microsoft tool.
Execute the command : fciv.exe -sha1 <filename.ovf>
fciv.exe C:\Users\ygotame\Desktop\ItSecure\OVF file new SHA1.png
OVF file new SHA1
Now, copy the new SHA1 key 51bd98… and open <filename>.mf
Paste the new value in the file and save it.
Modify SHA1 Key

Once that has been done,  try one more time to deploy the vm machine. This time, it should be working without any issue.
Deploy Finish Step

Post a Comment