Reply to Message

View discussion in a popup

Replying to:
JohnMarkston
Contributor
Contributor

You can ignore my my question from last Thursday, I actually figured why I cannot deploy the appliance in vSphere.  The problem is that vSphere sees the value of ovf:capacity field in the DiskSection of the OVF and thinks that it is too small.  Oracle VM and VirtualBox are both ok with this field, maybe they don't even look at it.  I am not sure what vSphere is comparing ovf:capacity against in order to come to that conclusion though.  To work around this issue I was able to double the value of the ovf:capacity field and run OVF Tool against it.  And in fact, if I pass the --lax parameter to OVF Tool without your workaround on May 8 I am still able to deploy the OVF appliance.  I successfully tried this technique with both the PeopleSoft HCM and FSCM PUM OVAs.  (I think they call this revision of their OVAs 'PI 6')

In summary, here's what I did:

  1. Download the PI6 OVAs from MyOracleSupport.
  2. On Fedora extract the OVAs using tar:   tar xvf FSCMDB-SES-853-12.ova
  3. In vi edit the extracted .ovf file to replace  <OperatingSystemSection ovf:id="109">  with  <OperatingSystemSection ovf:id="36">
  4. Also in vi edit the.ovf file to replace all occurrences of Oracle_64 with Linux
  5. Still in vi double the values of all the ovf:capacity fields in the DiskSection element.  e.g:  increase the value of ovf:capacity="10092418560" to 20092418560
  6. Totally remove the System element from the VirtualHardwareSection element.
  7. Run ovftool, for example:  ovftool --lax --skipManifestGeneration FSCMDB-SES-853-12.ovf FSCMDB-SES-853-12-vmware.ovf
  8. Deploy OVF Appliance in vSphere.
  9. Go to the console of the VM and answer all the goofy questions that it prompts you with.

I have attached a copy of the OVF file that I edited as described above.

Reply
0 Kudos