# VM Provision Steps

While many things can happen during an individual provisioning process, the basic order is:

- Look for the Virtual Image

  VM Essentials will check if the Virtual Image set on the Node Type or selected from a list of images during provisioning is already available to the HVM cluster or to a vCenter Cloud target. If not and it is an uploaded or local image, VM Essentials will attempt to upload the image to the HVM cluster or vCenter target.

  **Upload Image**

  For uploaded or local images that do not exist in the target, VM Essentials will need to upload the Image. Ensure the Virtual Image is valid for the target technology, the image meets the target upload requirements, and VM Essentials has network access and permissions to upload the image.

  NOTE

  When uploading an image to a VMware Cloud, the Virtual Image is copied directly to the target ESXi host, NOT through the vCenter server. Ensure the VM Essentials Appliance(s) can resolve target ESXi hostnames and connect on port 443 for successful vmdk/ova uploads.

  **Clone Image**

  Once the Image is confirmed available in the target cloud, VM Essentials will clone the Image to the target Datastore.

  NOTE

  The target host must have access to the target Datastore of the Image.
- Reconfigure Image

  Once cloned, VM Essentials will resize the Image based off provisioning parameters
- Cloud-init (if enabled)
  :   Attached cloud-init iso
      :   When using cloud-init, VM Essentials will attach a tiny metadata iso to the new VM. Network, Machine, User and any other cloud-init metadata will be sourced from this iso.

      VM Tools
      :   VM Essentials will run guest customizations via VMware VM Tools, including network config when assigning static IP addresses.
- Wait for Power On status and Network info

  VM Essentials will wait to hear back from the target that the VM has successfully started and has an IP address.

  NOTE

  If `VM TOOLS INSTALLED?` is NOT checked on the source Virtual Image configuration, VM Essentials will skip waiting for network.
- Finalize

  By default, this step will include Agent installation.

  IMPORTANT

  If the VM is stuck in finalize for long periods of time, this typically means the Agent cannot be installed or has not been heard back from. This will result in a ! warning Instance status upon provisioning completion.

  If agent installation is not possible or is not desired, uncheck “Install Agent” on the source Virtual Image configuration or select “Skip Agent Install” during provisioning to speed up provisioning completion.
