fbpx

Getting Started, Converting the OVF for VMware vCenter

By Mark Unwin - Open-AudIT Founder and Product Lead

Importing the OVA file to an ESXi Datacenter via vCenter using VMware OVF Tool

  • NOTE – We do not support OVA import to VMware ESXi directly or via VMware vCenter using a browser.
  • NOTE – We require the VMware OVF Tool if importing to VMware ESXi directly or via VMware vCenter.
    • Numerous attempts were made to import this OVA using the VMware vSphere HTML5 Client, with Chrome, Chromium and Firefox as browser: Every attempt timed out.
    • We have yet to experience a failed import of this OVF using VMware commandline tool ovftool: For this reason VMware commandline tool ovftool is recommended for importing OVAs’ via VMware vCenter

You can import the OVA file into a VMware ESXi Datacenter via VMware vCenter using VMware ovftool, from the PC or server you run ovftool.
Remember to set the Virtual Machine name you like, the datastore you want, the network you want, and point it at the server you want to deploy to.
Run commands like this:

  • In this example the VMware vCenter 6.5 install has created:

    • FQDN ‘photon-machine’ with

      • user ‘administrator,

      • sso domain name ‘vsphere.localdomain, and

      • sso password ‘Vagrant1!

        • which must be escaped when used in this context using ovftool:

          • escaped  password: ‘Vagrant1\!

  • VMware ovftool option that should be determined appropriate to this use case for this OVA import:
    • -ds=”datastore_name-number”
      • Required if the selected Datacenter has more than one datastore
    • -nw=”network_name-number”
      • Required if the selected Datacenter has more than one network
    • -dm
      –diskMode

      Specify the disk format. You can specify the following formats:

      • monolithicSparse
      • monolithicFlat
      • twoGbMaxExtentSparse
      • twoGbMaxExtentFlat
      • seSparse (vSphere target)
      • eagerZeroedThick (vSphere target)
      • thin(vSphere target)
      • thick (vSphere target)
      • sparse
      • flat
Determine the Datacenter name:
ovftool vi://administrator@vsphere.localdomain:Vagrant1\!@photon-machine
Error: Found wrong kind of object (Folder). Possible completions are:
Datacenter1/
Determine the Datacenter available options:
ovftool vi://administrator@vsphere.localdomain:Vagrant1\!@photon-machine/Datacenter1/
Error: Found wrong kind of object (Datacenter). Possible completions are:
vm/
host/

Determine the Datacenter host IP or FQDN:
ovftool vi://administrator@vsphere.localdomain:Vagrant1\!@photon-machine/Datacenter1/host/
Error: Found wrong kind of object (Folder). Possible completions are:
172.16.37.128/

Import Opmantek-20200708-VM9-Centos7.2003-3-64bit.ova which is in the current directory, in this example using vSphere option –diskMode=thin:
ls -la
-rw-rw-r– 1 user user 903864320 Jul 29 13:09 Opmantek-20200708-VM9-Centos7.2003-3-64bit.ova

ovftool –acceptAllEulas –name=”omk_vm9_centos7″ –diskMode=thin Opmantek-20200708-VM9-Centos7.2003-3-64bit.ova vi://administrator@vsphere.localdomain:Vagrant1\!@photon-machine/Datacenter1/host/172.16.37.128
Opening OVA source: Opmantek-20200708-VM9-Centos7.2003-3-64bit.ova
Opening VI target: vi://administrator%40vsphere.localdomain@172.16.37.130:443/Datacenter1/host/172.16.37.128
Deploying to VI: vi://administrator%40vsphere.localdomain@172.16.37.130:443/Datacenter1/host/172.16.37.128
Transfer Completed
Warning:
– No supported manifest(sha1, sha256, sha512) entry found for: ‘omk-vm9-centos7-disk001.vmdk’.
– No supported manifest(sha1, sha256, sha512) entry found for: ‘omk-vm9-centos7-disk002.vmdk’.
– No manifest file found.
Completed successfully

Pin It on Pinterest