creating vms on standalone esxi host

[Andrew Meyer]

I am having some issues getting packer to create VMs on my single ESX host.  Everything I have found requires the vsphere appliance.  I have enabled all the changes for this to work on the host itself.

Here is my config

{

  "builders": [

    { 

      "type": "vsphere-iso",

      "vcenter_server": "10.150.1.35",

      "insecure_connection": "true",

      "username": "root",

      "password": "",

      "host": "10.150.1.35",

      "vm_name":  "centos7base",

      "convert_to_template": "false",

      "cpu": "1",

      "ram": "2048",

      "network": "v10101-prod",

      "network_adapter": "vmxnet3",

      "guest_os_type": "centos7_64Guest",

      "datastore": "datastore-nas",

      "disk_size": "60GB",

      "iso": "/vmfs/volumes/datastore02/ISO/CentOS-7-x86_64-DVD-1810.iso",

      "iso_datastore": "datastore02"

    }

  ]

}

Here is the output I get when I try to run it:

packer build new-centos1.json

vsphere-iso output will be in this color.

==> vsphere-iso: Creating VM...

Build 'vsphere-iso' errored: resource pool '/ha-datacenter/host//Resources/' not found

==> Some builds didn't complete successfully and had errors:

--> vsphere-iso: resource pool '/ha-datacenter/host//Resources/' not found

==> Builds finished but no artifacts were created.

What am I doing wrong?

[Rickard von Essen]

The vsphere-iso builder will only work against the vSphere API. If you want to build on a single ESXi server you should use vmware-iso (with remote_XX options set).

--
This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list.
 
GitHub Issues: https://github.com/mitchellh/packer/issues
IRC: #packer-tool on Freenode
---
You received this message because you are subscribed to the Google Groups "Packer" group.
To unsubscribe from this group and stop receiving emails from it, send an email to packer-tool...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/packer-tool/5167c411-a6e8-4afd-95ab-aba0ed4059b7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Andrew Meyer]

So now I'm getting this:

Template validation failed. Errors are shown below.

Errors validating build 'vsphere-iso'. 6 errors occurred:

* unknown configuration key: "keep_registered"
* unknown configuration key: "remote_datastore"
* unknown configuration key: "remote_host"
* unknown configuration key: "remote_password"
* unknown configuration key: "remote_type"
* unknown configuration key: "remote_username"

I made the following changes:

{
  "builders": [
    {
      "type": "vsphere-iso",


      "remote_type": "esx5",
      "remote_host": "{{user `esxi_host`}}",
      "remote_datastore": "{{user `esxi_datastore`}}",
      "remote_username": "{{user `esxi_username`}}",
      "remote_password": "{{user `esxi_password`}}",
      "keep_registered": true,
      "insecure_connection": "true",
      "username": "username",
      "password": "password",

[Rickard von Essen]

Your type is still vsphere-iso. 

To view this discussion on the web visit https://groups.google.com/d/msgid/packer-tool/f5b697d7-fe85-4ec8-a302-616cd47034ea%40googlegroups.com.

[Andrew Meyer]

Can I not use variables with this?  Can I not have a separate variables.json file?  Or should this all be monolithic?

[Andrew Meyer]

Also,

Now I am getting this error:

 packer validate vmware/new-centos2.json

Template validation failed. Errors are shown below.

Errors validating build ''. 1 error(s) occurred:

* ovftool validation error: fork/exec : no such file or directory;

[Pietto Vasco]

I am trying to do the same thing. I have a packer test later today  I'll update you 

To view this discussion on the web visit https://groups.google.com/d/msgid/packer-tool/1e60d8e9-2efd-4d2e-9701-ff0cc04028fe%40googlegroups.com.

[Rickard von Essen]

You can use variables for almost everything. And you need to have the ovftool installed and on the path for the vmware-iso builder. 

To view this discussion on the web visit https://groups.google.com/d/msgid/packer-tool/CAC0gkf0v0918m8gqSt_V2cyYEgfwSdN204scbEySDr8beyVDQw%40mail.gmail.com.

[Andrew Meyer]

Ok so I downloaded the ovftool bundle, but I'm still seeing this in the logs:

2019/01/22 09:46:48 Preparing build: 

2019/01/22 09:46:48 Build '' prepare failure: 1 error(s) occurred:

* ovftool validation error: fork/exec : no such file or directory; 

2019/01/22 09:46:48 ui error: Template validation failed. Errors are shown below.

2019/01/22 09:46:48 ui error: Errors validating build ''. 1 error(s) occurred:

* ovftool validation error: fork/exec : no such file or directory; 

2019/01/22 09:46:48 [INFO] (telemetry) Finalizing.

2019/01/22 09:46:49 waiting for all plugin processes to complete...

2019/01/22 09:46:49 /usr/local/bin/packer_1.3.3: plugin process exited

Do I need to install or download something else?

[Andrew Meyer]

nevermind I got it working.  on to the next issue.

TY!

[Andrew Meyer]

Ok so I'm not understanding the syntax for the ovftool in the json file.  Here is the error i'm getting:

Template validation failed. Errors are shown below.

Errors validating build ''. 1 error(s) occurred:

* ovftool validation error: signal: killed; Accept SSL fingerprint (EF:5E:1D:73:3D:31:88:D0:B2:A7:8F:8B:F9:2A:FC:03:CB:A5:23:FC) for host 10.150.1.35 as source type.

Fingerprint will be added to the known host file

Write 'yes' or 'no'

Here is the line in the json file

      "ovftool_options": "--noSSLVerify=yes",

[Andrew Meyer]

Nm, got further on this.  but still complaining about SSL verification.

[Andrew Meyer]

Ok so I got much further.  I fixed the problems I was seeing w/ the ovftool.

However now I am getting this error message:

packer build vmware/new-centos2.json
centos7base output will be in this color.

==> centos7base: Retrieving ISO
1 items:  918.00 MiB / 918.00 MiB [========================================================================================================] 1m46s
    centos7base: Transferred: http://10.150.1.9/CentOS-7-x86_64-Minimal-1810.iso
==> centos7base: Uploading ISO to remote machine...
==> centos7base: Creating required virtual machine disks
==> centos7base: Building and writing VMX file
==> centos7base: Registering remote VM...
==> centos7base: Starting virtual machine...
    centos7base: The VM will be run headless, without a GUI. If you want to
    centos7base: view the screen of the VM, connect via VNC with the password "66nhCBkk" to
    centos7base: vnc://10.150.1.35:5900
==> centos7base: Error starting VM: Retry limit exceeded
==> centos7base: Destroying virtual machine...
Build 'centos7base' errored: Error starting VM: Retry limit exceeded

==> Some builds didn't complete successfully and had errors:
--> centos7base: Error starting VM: Retry limit exceeded

[Rickard von Essen]

Rerun with env var PACKER_LOG=1 packer build template.json... And post the logs here. 

To view this discussion on the web visit https://groups.google.com/d/msgid/packer-tool/abc87b54-6b99-4ab1-827a-44e30ce88fad%40googlegroups.com.

[JP Toto]

Out of curiosity, which version of VMWare ESXi are you using?

To view this discussion on the web visit https://groups.google.com/d/msgid/packer-tool/CALz9Rt-1p0OhNoOwgJYtiHbqPfDQYuH83U9Vs9xuZx7Y1BS3ZA%40mail.gmail.com.

For more options, visit https://groups.google.com/d/optout.

--

JP Toto   |   james....@gmail.com   |   http://jptoto.jp   |   @jptoto

[Andrew Meyer]

6.5

[Stan Dorsett]

Have you enabled the ESXi firewall to allow inbound VNC connections?

# open inbound VNC connections on the firewall

esxcli network firewall ruleset set -e true -r gdbserver

Stan.

[Andrew Meyer]

Here are the logs:

2019/01/24 13:36:34 [INFO] Packer version: 1.3.3
2019/01/24 13:36:34 Packer Target OS/Arch: linux amd64
2019/01/24 13:36:34 Built with Go Version: go1.11.2
2019/01/24 13:36:34 [DEBUG] Discovered plugin: vsphere-iso = /usr/local/bin/packer-builder-vsphere-iso.linux
2019/01/24 13:36:34 Detected home directory from env var: /home/andrew.meyer
2019/01/24 13:36:34 [DEBUG] Discovered plugin: vsphere-iso = /home/andrew.meyer/.packer.d/plugins/packer-builder-vsphere-iso.linux
2019/01/24 13:36:34 Using internal plugin for hyperv-iso
2019/01/24 13:36:34 Using internal plugin for hyperv-vmcx
2019/01/24 13:36:34 Using internal plugin for vmware-iso
2019/01/24 13:36:34 Using internal plugin for amazon-chroot
2019/01/24 13:36:34 Using internal plugin for lxd
2019/01/24 13:36:34 Using internal plugin for oneandone
2019/01/24 13:36:34 Using internal plugin for vmware-vmx
2019/01/24 13:36:34 Using internal plugin for profitbricks
2019/01/24 13:36:34 Using internal plugin for triton
2019/01/24 13:36:34 Using internal plugin for virtualbox-ovf
2019/01/24 13:36:34 Using internal plugin for amazon-ebs
2019/01/24 13:36:34 Using internal plugin for digitalocean
2019/01/24 13:36:34 Using internal plugin for hcloud
2019/01/24 13:36:34 Using internal plugin for parallels-pvm
2019/01/24 13:36:34 Using internal plugin for virtualbox-iso
2019/01/24 13:36:34 Using internal plugin for alicloud-ecs
2019/01/24 13:36:34 Using internal plugin for file
2019/01/24 13:36:34 Using internal plugin for lxc
2019/01/24 13:36:34 Using internal plugin for oracle-oci
2019/01/24 13:36:34 Using internal plugin for qemu
2019/01/24 13:36:34 Using internal plugin for amazon-ebsvolume
2019/01/24 13:36:34 Using internal plugin for openstack
2019/01/24 13:36:34 Using internal plugin for oracle-classic
2019/01/24 13:36:34 Using internal plugin for amazon-ebssurrogate
2019/01/24 13:36:34 Using internal plugin for amazon-instance
2019/01/24 13:36:34 Using internal plugin for azure-arm
2019/01/24 13:36:34 Using internal plugin for parallels-iso
2019/01/24 13:36:34 Using internal plugin for scaleway
2019/01/24 13:36:34 Using internal plugin for cloudstack
2019/01/24 13:36:34 Using internal plugin for docker
2019/01/24 13:36:34 Using internal plugin for googlecompute
2019/01/24 13:36:34 Using internal plugin for ncloud
2019/01/24 13:36:34 Using internal plugin for null
2019/01/24 13:36:34 Using internal plugin for breakpoint
2019/01/24 13:36:34 Using internal plugin for chef-client
2019/01/24 13:36:34 Using internal plugin for powershell
2019/01/24 13:36:34 Using internal plugin for puppet-masterless
2019/01/24 13:36:34 Using internal plugin for shell-local
2019/01/24 13:36:34 Using internal plugin for ansible
2019/01/24 13:36:34 Using internal plugin for salt-masterless
2019/01/24 13:36:34 Using internal plugin for windows-restart
2019/01/24 13:36:34 Using internal plugin for chef-solo
2019/01/24 13:36:34 Using internal plugin for puppet-server
2019/01/24 13:36:34 Using internal plugin for shell
2019/01/24 13:36:34 Using internal plugin for ansible-local
2019/01/24 13:36:34 Using internal plugin for converge
2019/01/24 13:36:34 Using internal plugin for file
2019/01/24 13:36:34 Using internal plugin for windows-shell
2019/01/24 13:36:34 Using internal plugin for googlecompute-import
2019/01/24 13:36:34 Using internal plugin for vagrant
2019/01/24 13:36:34 Using internal plugin for alicloud-import
2019/01/24 13:36:34 Using internal plugin for docker-push
2019/01/24 13:36:34 Using internal plugin for docker-save
2019/01/24 13:36:34 Using internal plugin for manifest
2019/01/24 13:36:34 Using internal plugin for shell-local
2019/01/24 13:36:34 Using internal plugin for vagrant-cloud
2019/01/24 13:36:34 Using internal plugin for vsphere
2019/01/24 13:36:34 Using internal plugin for artifice
2019/01/24 13:36:34 Using internal plugin for docker-import
2019/01/24 13:36:34 Using internal plugin for googlecompute-export
2019/01/24 13:36:34 Using internal plugin for vsphere-template
2019/01/24 13:36:34 Using internal plugin for amazon-import
2019/01/24 13:36:34 Using internal plugin for checksum
2019/01/24 13:36:34 Using internal plugin for compress
2019/01/24 13:36:34 Using internal plugin for docker-tag
2019/01/24 13:36:34 Detected home directory from env var: /home/andrew.meyer
2019/01/24 13:36:34 Attempting to open config file: /home/andrew.meyer/.packerconfig
2019/01/24 13:36:34 [WARN] Config file doesn't exist: /home/andrew.meyer/.packerconfig
2019/01/24 13:36:34 Packer config: &{DisableCheckpoint:false DisableCheckpointSignature:false PluginMinPort:10000 PluginMaxPort:25000 Builders:map[vmware-vmx:/usr/local/bin/packer_1.3.3-PACKERSPACE-plugin-PACKERSPACE-packer-builder-vmware-vmx vsphere-iso:/home/andrew.meyer/.packer.d/plugins/packer-builder-vsphere-iso.linux scaleway:/usr/local/bin/packer_1.3.3-PACKERSPACE-plugin-PACKERSPACE-packer-builder-scaleway googlecompute:/usr/local/bin/packer_1.3.3-PACKERSPACE-plugin-PACKERSPACE-packer-builder-googlecompute triton:/usr/local/bin/packer_1.3.3-PACKERSPACE-plugin-PACKERSPACE-packer-builder-triton hcloud:/usr/local/bin/packer_1.3.3-PACKERSPACE-plugin-PACKERSPACE-packer-builder-hcloud virtualbox-iso:/usr/local/bin/packer_1.3.3-PACKERSPACE-plugin-PACKERSPACE-packer-builder-virtualbox-iso amazon-ebsvolume:/usr/local/bin/packer_1.3.3-PACKERSPACE-plugin-PACKERSPACE-packer-builder-amazon-ebsvolume docker:/usr/local/bin/packer_1.3.3-PACKERSPACE-plugin-PACKERSPACE-packer-builder-docker alicloud-ecs:/usr/local/bin/packer_1.3.3-PACKERSPACE-plugin-PACKERSPACE-packer-builder-alicloud-ecs lxc:/usr/local/bin/packer_1.3.3-PACKERSPACE-plugin-PACKERSPACE-packer-builder-lxc amazon-ebssurrogate:/usr/local/bin/packer_1.3.3-PACKERSPACE-plugin-PACKERSPACE-packer-builder-amazon-ebssurrogate parallels-iso:/usr/local/bin/packer_1.3.3-PACKERSPACE-plugin-PACKERSPACE-packer-builder-parallels-iso vmware-iso:/usr/local/bin/packer_1.3.3-PACKERSPACE-plugin-PACKERSPACE-packer-builder-vmware-iso amazon-chroot:/usr/local/bin/packer_1.3.3-PACKERSPACE-plugin-PACKERSPACE-packer-builder-amazon-chroot oneandone:/usr/local/bin/packer_1.3.3-PACKERSPACE-plugin-PACKERSPACE-packer-builder-oneandone virtualbox-ovf:/usr/local/bin/packer_1.3.3-PACKERSPACE-plugin-PACKERSPACE-packer-builder-virtualbox-ovf oracle-oci:/usr/local/bin/packer_1.3.3-PACKERSPACE-plugin-PACKERSPACE-packer-builder-oracle-oci qemu:/usr/local/bin/packer_1.3.3-PACKERSPACE-plugin-PACKERSPACE-packer-builder-qemu lxd:/usr/local/bin/packer_1.3.3-PACKERSPACE-plugin-PACKERSPACE-packer-builder-lxd digitalocean:/usr/local/bin/packer_1.3.3-PACKERSPACE-plugin-PACKERSPACE-packer-builder-digitalocean openstack:/usr/local/bin/packer_1.3.3-PACKERSPACE-plugin-PACKERSPACE-packer-builder-openstack amazon-instance:/usr/local/bin/packer_1.3.3-PACKERSPACE-plugin-PACKERSPACE-packer-builder-amazon-instance azure-arm:/usr/local/bin/packer_1.3.3-PACKERSPACE-plugin-PACKERSPACE-packer-builder-azure-arm null:/usr/local/bin/packer_1.3.3-PACKERSPACE-plugin-PACKERSPACE-packer-builder-null hyperv-iso:/usr/local/bin/packer_1.3.3-PACKERSPACE-plugin-PACKERSPACE-packer-builder-hyperv-iso hyperv-vmcx:/usr/local/bin/packer_1.3.3-PACKERSPACE-plugin-PACKERSPACE-packer-builder-hyperv-vmcx profitbricks:/usr/local/bin/packer_1.3.3-PACKERSPACE-plugin-PACKERSPACE-packer-builder-profitbricks ncloud:/usr/local/bin/packer_1.3.3-PACKERSPACE-plugin-PACKERSPACE-packer-builder-ncloud amazon-ebs:/usr/local/bin/packer_1.3.3-PACKERSPACE-plugin-PACKERSPACE-packer-builder-amazon-ebs parallels-pvm:/usr/local/bin/packer_1.3.3-PACKERSPACE-plugin-PACKERSPACE-packer-builder-parallels-pvm file:/usr/local/bin/packer_1.3.3-PACKERSPACE-plugin-PACKERSPACE-packer-builder-file oracle-classic:/usr/local/bin/packer_1.3.3-PACKERSPACE-plugin-PACKERSPACE-packer-builder-oracle-classic cloudstack:/usr/local/bin/packer_1.3.3-PACKERSPACE-plugin-PACKERSPACE-packer-builder-cloudstack] PostProcessors:map[googlecompute-import:/usr/local/bin/packer_1.3.3-PACKERSPACE-plugin-PACKERSPACE-packer-post-processor-googlecompute-import docker-save:/usr/local/bin/packer_1.3.3-PACKERSPACE-plugin-PACKERSPACE-packer-post-processor-docker-save manifest:/usr/local/bin/packer_1.3.3-PACKERSPACE-plugin-PACKERSPACE-packer-post-processor-manifest artifice:/usr/local/bin/packer_1.3.3-PACKERSPACE-plugin-PACKERSPACE-packer-post-processor-artifice vsphere-template:/usr/local/bin/packer_1.3.3-PACKERSPACE-plugin-PACKERSPACE-packer-post-processor-vsphere-template compress:/usr/local/bin/packer_1.3.3-PACKERSPACE-plugin-PACKERSPACE-packer-post-processor-compress vagrant:/usr/local/bin/packer_1.3.3-PACKERSPACE-plugin-PACKERSPACE-packer-post-processor-vagrant vsphere:/usr/local/bin/packer_1.3.3-PACKERSPACE-plugin-PACKERSPACE-packer-post-processor-vsphere googlecompute-export:/usr/local/bin/packer_1.3.3-PACKERSPACE-plugin-PACKERSPACE-packer-post-processor-googlecompute-export alicloud-import:/usr/local/bin/packer_1.3.3-PACKERSPACE-plugin-PACKERSPACE-packer-post-processor-alicloud-import docker-push:/usr/local/bin/packer_1.3.3-PACKERSPACE-plugin-PACKERSPACE-packer-post-processor-docker-push docker-tag:/usr/local/bin/packer_1.3.3-PACKERSPACE-plugin-PACKERSPACE-packer-post-processor-docker-tag shell-local:/usr/local/bin/packer_1.3.3-PACKERSPACE-plugin-PACKERSPACE-packer-post-processor-shell-local vagrant-cloud:/usr/local/bin/packer_1.3.3-PACKERSPACE-plugin-PACKERSPACE-packer-post-processor-vagrant-cloud docker-import:/usr/local/bin/packer_1.3.3-PACKERSPACE-plugin-PACKERSPACE-packer-post-processor-docker-import amazon-import:/usr/local/bin/packer_1.3.3-PACKERSPACE-plugin-PACKERSPACE-packer-post-processor-amazon-import checksum:/usr/local/bin/packer_1.3.3-PACKERSPACE-plugin-PACKERSPACE-packer-post-processor-checksum] Provisioners:map[powershell:/usr/local/bin/packer_1.3.3-PACKERSPACE-plugin-PACKERSPACE-packer-provisioner-powershell windows-restart:/usr/local/bin/packer_1.3.3-PACKERSPACE-plugin-PACKERSPACE-packer-provisioner-windows-restart puppet-server:/usr/local/bin/packer_1.3.3-PACKERSPACE-plugin-PACKERSPACE-packer-provisioner-puppet-server ansible-local:/usr/local/bin/packer_1.3.3-PACKERSPACE-plugin-PACKERSPACE-packer-provisioner-ansible-local shell-local:/usr/local/bin/packer_1.3.3-PACKERSPACE-plugin-PACKERSPACE-packer-provisioner-shell-local converge:/usr/local/bin/packer_1.3.3-PACKERSPACE-plugin-PACKERSPACE-packer-provisioner-converge windows-shell:/usr/local/bin/packer_1.3.3-PACKERSPACE-plugin-PACKERSPACE-packer-provisioner-windows-shell salt-masterless:/usr/local/bin/packer_1.3.3-PACKERSPACE-plugin-PACKERSPACE-packer-provisioner-salt-masterless chef-solo:/usr/local/bin/packer_1.3.3-PACKERSPACE-plugin-PACKERSPACE-packer-provisioner-chef-solo shell:/usr/local/bin/packer_1.3.3-PACKERSPACE-plugin-PACKERSPACE-packer-provisioner-shell file:/usr/local/bin/packer_1.3.3-PACKERSPACE-plugin-PACKERSPACE-packer-provisioner-file breakpoint:/usr/local/bin/packer_1.3.3-PACKERSPACE-plugin-PACKERSPACE-packer-provisioner-breakpoint chef-client:/usr/local/bin/packer_1.3.3-PACKERSPACE-plugin-PACKERSPACE-packer-provisioner-chef-client puppet-masterless:/usr/local/bin/packer_1.3.3-PACKERSPACE-plugin-PACKERSPACE-packer-provisioner-puppet-masterless ansible:/usr/local/bin/packer_1.3.3-PACKERSPACE-plugin-PACKERSPACE-packer-provisioner-ansible]}
2019/01/24 13:36:34 Detected home directory from env var: /home/andrew.meyer
2019/01/24 13:36:34 Setting cache directory: /home/andrew.meyer/Ops/packer/packer_cache
2019/01/24 13:36:34 Detected home directory from env var: /home/andrew.meyer
2019/01/24 13:36:34 Loading builder: vmware-iso
2019/01/24 13:36:34 Plugin could not be found. Checking same directory as executable.
2019/01/24 13:36:34 Current exe path: /usr/local/bin/packer_1.3.3
2019/01/24 13:36:34 Creating plugin client for path: /usr/local/bin/packer_1.3.3
2019/01/24 13:36:34 Starting plugin: /usr/local/bin/packer_1.3.3 []string{"/usr/local/bin/packer_1.3.3", "plugin", "packer-builder-vmware-iso"}
2019/01/24 13:36:34 Waiting for RPC address for: /usr/local/bin/packer_1.3.3
2019/01/24 13:36:35 packer_1.3.3: 2019/01/24 13:36:35 [INFO] Packer version: 1.3.3
2019/01/24 13:36:35 packer_1.3.3: 2019/01/24 13:36:35 Packer Target OS/Arch: linux amd64
2019/01/24 13:36:35 packer_1.3.3: 2019/01/24 13:36:35 Built with Go Version: go1.11.2
2019/01/24 13:36:35 packer_1.3.3: 2019/01/24 13:36:35 Detected home directory from env var: /home/andrew.meyer
2019/01/24 13:36:35 packer_1.3.3: 2019/01/24 13:36:35 Attempting to open config file: /home/andrew.meyer/.packerconfig
2019/01/24 13:36:35 packer_1.3.3: 2019/01/24 13:36:35 [WARN] Config file doesn't exist: /home/andrew.meyer/.packerconfig
2019/01/24 13:36:35 packer_1.3.3: 2019/01/24 13:36:35 Packer config: &{DisableCheckpoint:false DisableCheckpointSignature:false PluginMinPort:10000 PluginMaxPort:25000 Builders:map[] PostProcessors:map[] Provisioners:map[]}
2019/01/24 13:36:35 packer_1.3.3: 2019/01/24 13:36:35 Detected home directory from env var: /home/andrew.meyer
2019/01/24 13:36:35 packer_1.3.3: 2019/01/24 13:36:35 Setting cache directory: /home/andrew.meyer/Ops/packer/packer_cache
2019/01/24 13:36:35 packer_1.3.3: 2019/01/24 13:36:35 args: []string{"packer-builder-vmware-iso"}
2019/01/24 13:36:35 packer_1.3.3: 2019/01/24 13:36:35 Plugin minimum port: 10000
2019/01/24 13:36:35 packer_1.3.3: 2019/01/24 13:36:35 Plugin maximum port: 25000
2019/01/24 13:36:35 packer_1.3.3: 2019/01/24 13:36:35 Plugin address: unix /tmp/packer-plugin236427144
2019/01/24 13:36:35 packer_1.3.3: 2019/01/24 13:36:35 Waiting for connection...
2019/01/24 13:36:35 packer_1.3.3: 2019/01/24 13:36:35 Detected home directory from env var: /home/andrew.meyer
2019/01/24 13:36:35 packer_1.3.3: 2019/01/24 13:36:35 Serving a plugin connection...
2019/01/24 13:36:35 ui: centos7base output will be in this color.
2019/01/24 13:36:35 ui:
2019/01/24 13:36:35 Build debug mode: false
2019/01/24 13:36:35 Force build: false
2019/01/24 13:36:35 On error:
2019/01/24 13:36:35 Preparing build: centos7base
2019/01/24 13:36:37 Waiting on builds to complete...
2019/01/24 13:36:37 Starting build run: centos7base
2019/01/24 13:36:37 Running builder: vmware-iso
2019/01/24 13:36:37 [INFO] (telemetry) Starting builder vmware-iso
2019/01/24 13:36:37 packer_1.3.3: 2019/01/24 13:36:37 [DEBUG] reconnecting to TCP connection for SSH
2019/01/24 13:36:37 packer_1.3.3: 2019/01/24 13:36:37 [DEBUG] handshaking with SSH
2019/01/24 13:36:37 packer_1.3.3: 2019/01/24 13:36:37 Keyboard interactive challenge:
2019/01/24 13:36:37 packer_1.3.3: 2019/01/24 13:36:37 -- User:
2019/01/24 13:36:37 packer_1.3.3: 2019/01/24 13:36:37 -- Instructions:
2019/01/24 13:36:37 packer_1.3.3: 2019/01/24 13:36:37 -- Question 1: Password:
2019/01/24 13:36:37 packer_1.3.3: 2019/01/24 13:36:37 Keyboard interactive challenge:
2019/01/24 13:36:37 packer_1.3.3: 2019/01/24 13:36:37 -- User:
2019/01/24 13:36:37 packer_1.3.3: 2019/01/24 13:36:37 -- Instructions:
2019/01/24 13:36:37 packer_1.3.3: 2019/01/24 13:36:37 [DEBUG] handshake complete!
2019/01/24 13:36:37 packer_1.3.3: 2019/01/24 13:36:37 [INFO] no local agent socket, will not connect agent
2019/01/24 13:36:37 packer_1.3.3: 2019/01/24 13:36:37 [DEBUG] Opening new ssh session
2019/01/24 13:36:37 packer_1.3.3: 2019/01/24 13:36:37 [DEBUG] starting remote command: esxcli --formatter csv system version get
2019/01/24 13:36:38 packer_1.3.3: 2019/01/24 13:36:38 Connected to VMware ESXi 6.5.0 Releasebuild-8294253
2019/01/24 13:36:38 packer_1.3.3: 2019/01/24 13:36:38 [DEBUG] Opening new ssh session
2019/01/24 13:36:38 packer_1.3.3: 2019/01/24 13:36:38 [DEBUG] starting remote command: esxcli --formatter csv system settings advanced list -o /Net/GuestIPHack
2019/01/24 13:36:38 ui: ==> centos7base: Retrieving ISO
2019/01/24 13:36:38 packer_1.3.3: 2019/01/24 13:36:38 Testing vmware driver *common.ESX5Driver. Success: true
2019/01/24 13:36:38 packer_1.3.3: 2019/01/24 13:36:38 Acquiring lock to download: http://10.150.1.9/CentOS-7-x86_64-Minimal-1810.iso
2019/01/24 13:36:38 packer_1.3.3: 2019/01/24 13:36:38 Verifying checksum of /home/andrew.meyer/Ops/packer/packer_cache/023fa9ff27f042b15d49d1e36548666368c552bc7f19f0e4463cefd4cf57bfe3.iso
2019/01/24 13:36:53 ui:     centos7base: Found already downloaded, initial checksum matched, no download needed: http://10.150.1.9/CentOS-7-x86_64-Minimal-1810.iso
2019/01/24 13:36:53 packer_1.3.3: 2019/01/24 13:36:53 [DEBUG] Opening new ssh session
2019/01/24 13:36:53 packer_1.3.3: 2019/01/24 13:36:53 [DEBUG] starting remote command: test -e "/vmfs/volumes/datastore-nas/centos7base"
2019/01/24 13:36:53 packer_1.3.3: 2019/01/24 13:36:53 [ERROR] Remote command exited with '1': test -e "/vmfs/volumes/datastore-nas/centos7base"
2019/01/24 13:36:53 packer_1.3.3: 2019/01/24 13:36:53 [DEBUG] Opening new ssh session
2019/01/24 13:36:53 packer_1.3.3: 2019/01/24 13:36:53 [DEBUG] starting remote command: mkdir -p "/vmfs/volumes/datastore-nas/centos7base"
2019/01/24 13:36:53 packer_1.3.3: 2019/01/24 13:36:53 No floppy files specified. Floppy disk will not be made.
2019/01/24 13:36:53 packer_1.3.3: 2019/01/24 13:36:53 [DEBUG] Opening new ssh session
2019/01/24 13:36:53 packer_1.3.3: 2019/01/24 13:36:53 [DEBUG] starting remote command: sha256sum -c
2019/01/24 13:38:09 ui: ==> centos7base: Remote cache was verified skipping remote upload...
2019/01/24 13:38:09 ui: ==> centos7base: Creating required virtual machine disks
2019/01/24 13:38:09 packer_1.3.3: 2019/01/24 13:38:09 [INFO] Creating disk with Path: centos7base/disk.vmdk and Size: 61440M
2019/01/24 13:38:09 packer_1.3.3: 2019/01/24 13:38:09 [DEBUG] Opening new ssh session
2019/01/24 13:38:09 packer_1.3.3: 2019/01/24 13:38:09 [DEBUG] starting remote command: vmkfstools -c 61440M -d thin -a lsilogic "/vmfs/volumes/datastore-nas/centos7base/disk.vmdk"
2019/01/24 13:38:10 ui: ==> centos7base: Building and writing VMX file
2019/01/24 13:38:10 packer_1.3.3: 2019/01/24 13:38:10 Writing VMX to: /tmp/packer-vmx016406855/centos7base.vmx
2019/01/24 13:38:10 packer_1.3.3: 2019/01/24 13:38:10 Configuring VMX...
2019/01/24 13:38:10 packer_1.3.3: 2019/01/24 13:38:10 Writing VMX to: /tmp/packer-vmx016406855/centos7base.vmx
2019/01/24 13:38:10 packer_1.3.3: 2019/01/24 13:38:10 Suppressing messages in VMX
2019/01/24 13:38:10 packer_1.3.3: 2019/01/24 13:38:10 Looking for available port between 5900 and 6000
2019/01/24 13:38:10 packer_1.3.3: 2019/01/24 13:38:10 [DEBUG] Opening new ssh session
2019/01/24 13:38:10 packer_1.3.3: 2019/01/24 13:38:10 [DEBUG] starting remote command: esxcli --formatter csv network ip connection list
2019/01/24 13:38:11 packer_1.3.3: 2019/01/24 13:38:11 ESXi listening on address 0.0.0.0:22, port 22 unavailable for VNC
2019/01/24 13:38:11 packer_1.3.3: 2019/01/24 13:38:11 ESXi listening on address 0.0.0.0:8000, port 8000 unavailable for VNC
2019/01/24 13:38:11 packer_1.3.3: 2019/01/24 13:38:11 ESXi listening on address 10.150.1.35:427, port 427 unavailable for VNC
2019/01/24 13:38:11 packer_1.3.3: 2019/01/24 13:38:11 ESXi listening on address 0.0.0.0:443, port 443 unavailable for VNC
2019/01/24 13:38:11 packer_1.3.3: 2019/01/24 13:38:11 ESXi listening on address 0.0.0.0:80, port 80 unavailable for VNC
2019/01/24 13:38:11 packer_1.3.3: 2019/01/24 13:38:11 ESXi listening on address 0.0.0.0:9080, port 9080 unavailable for VNC
2019/01/24 13:38:11 packer_1.3.3: 2019/01/24 13:38:11 ESXi listening on address 0.0.0.0:902, port 902 unavailable for VNC
2019/01/24 13:38:11 packer_1.3.3: 2019/01/24 13:38:11 ESXi listening on address 0.0.0.0:8300, port 8300 unavailable for VNC
2019/01/24 13:38:11 packer_1.3.3: 2019/01/24 13:38:11 Trying address: 10.150.1.35:5900...
2019/01/24 13:38:11 ui: ==> centos7base: Registering remote VM...
2019/01/24 13:38:11 packer_1.3.3: 2019/01/24 13:38:11 Found available VNC port: 5900
2019/01/24 13:38:11 packer_1.3.3: 2019/01/24 13:38:11 Writing VMX to: /tmp/packer-vmx016406855/centos7base.vmx
2019/01/24 13:38:11 packer_1.3.3: 2019/01/24 13:38:11 [DEBUG] Opening new ssh session
2019/01/24 13:38:11 packer_1.3.3: 2019/01/24 13:38:11 [DEBUG] Starting remote scp process:  scp -vt /vmfs/volumes/datastore-nas/centos7base
2019/01/24 13:38:11 packer_1.3.3: 2019/01/24 13:38:11 [DEBUG] Started SCP session, beginning transfers...
2019/01/24 13:38:11 packer_1.3.3: 2019/01/24 13:38:11 [DEBUG] Copying input data into temporary file so we can read the length
2019/01/24 13:38:11 packer_1.3.3: 2019/01/24 13:38:11 [DEBUG] scp: Uploading centos7base.vmx: perms=C0644 size=2915
2019/01/24 13:38:11 packer_1.3.3: 2019/01/24 13:38:11 [DEBUG] SCP session complete, closing stdin pipe.
2019/01/24 13:38:11 packer_1.3.3: 2019/01/24 13:38:11 [DEBUG] Waiting for SSH session to complete.
2019/01/24 13:38:11 packer_1.3.3: 2019/01/24 13:38:11 [DEBUG] scp stderr (length 33): Sink: C0644 2915 centos7base.vmx
2019/01/24 13:38:11 packer_1.3.3: 2019/01/24 13:38:11 [DEBUG] Opening new ssh session
2019/01/24 13:38:11 packer_1.3.3: 2019/01/24 13:38:11 [DEBUG] starting remote command: vim-cmd solo/registervm "/vmfs/volumes/datastore-nas/centos7base/centos7base.vmx"
2019/01/24 13:38:11 ui: ==> centos7base: Starting virtual machine...
2019/01/24 13:38:11 ui:     centos7base: The VM will be run headless, without a GUI. If you want to
    centos7base: view the screen of the VM, connect via VNC with the password "s1r04yDe" to
    centos7base: vnc://10.150.1.35:5900
2019/01/24 13:38:11 packer_1.3.3: 2019/01/24 13:38:11 [DEBUG] Opening new ssh session
2019/01/24 13:38:11 packer_1.3.3: 2019/01/24 13:38:11 [DEBUG] starting remote command: vim-cmd vmsvc/power.on 39
2019/01/24 13:38:13 packer_1.3.3: 2019/01/24 13:38:13 [ERROR] Remote command exited with '1': vim-cmd vmsvc/power.on 39
2019/01/24 13:38:13 packer_1.3.3: 2019/01/24 13:38:13 [DEBUG] Opening new ssh session
2019/01/24 13:38:13 packer_1.3.3: 2019/01/24 13:38:13 [DEBUG] starting remote command: vim-cmd vmsvc/power.getstate 39
2019/01/24 13:38:14 packer_1.3.3: 2019/01/24 13:38:14 [DEBUG] Opening new ssh session
2019/01/24 13:38:14 packer_1.3.3: 2019/01/24 13:38:14 [DEBUG] starting remote command: vim-cmd vmsvc/power.on 39
2019/01/24 13:38:15 packer_1.3.3: 2019/01/24 13:38:15 [ERROR] Remote command exited with '1': vim-cmd vmsvc/power.on 39
2019/01/24 13:38:16 packer_1.3.3: 2019/01/24 13:38:16 [DEBUG] Opening new ssh session
2019/01/24 13:38:16 packer_1.3.3: 2019/01/24 13:38:16 [DEBUG] starting remote command: vim-cmd vmsvc/power.getstate 39
2019/01/24 13:38:17 packer_1.3.3: 2019/01/24 13:38:17 [DEBUG] Opening new ssh session
2019/01/24 13:38:17 packer_1.3.3: 2019/01/24 13:38:17 [DEBUG] starting remote command: vim-cmd vmsvc/power.on 39
2019/01/24 13:38:18 packer_1.3.3: 2019/01/24 13:38:18 [ERROR] Remote command exited with '1': vim-cmd vmsvc/power.on 39
2019/01/24 13:38:20 packer_1.3.3: 2019/01/24 13:38:20 [DEBUG] Opening new ssh session
2019/01/24 13:38:20 packer_1.3.3: 2019/01/24 13:38:20 [DEBUG] starting remote command: vim-cmd vmsvc/power.getstate 39
2019/01/24 13:38:21 packer_1.3.3: 2019/01/24 13:38:21 [DEBUG] Opening new ssh session
2019/01/24 13:38:21 packer_1.3.3: 2019/01/24 13:38:21 [DEBUG] starting remote command: vim-cmd vmsvc/power.on 39
2019/01/24 13:38:23 packer_1.3.3: 2019/01/24 13:38:23 [ERROR] Remote command exited with '1': vim-cmd vmsvc/power.on 39
2019/01/24 13:38:26 packer_1.3.3: 2019/01/24 13:38:26 [DEBUG] Opening new ssh session
2019/01/24 13:38:26 packer_1.3.3: 2019/01/24 13:38:26 [DEBUG] starting remote command: vim-cmd vmsvc/power.getstate 39
2019/01/24 13:38:26 packer_1.3.3: 2019/01/24 13:38:26 [DEBUG] Opening new ssh session
2019/01/24 13:38:26 packer_1.3.3: 2019/01/24 13:38:26 [DEBUG] starting remote command: vim-cmd vmsvc/power.on 39
2019/01/24 13:38:28 packer_1.3.3: 2019/01/24 13:38:28 [ERROR] Remote command exited with '1': vim-cmd vmsvc/power.on 39
2019/01/24 13:38:32 packer_1.3.3: 2019/01/24 13:38:32 [DEBUG] Opening new ssh session
2019/01/24 13:38:32 packer_1.3.3: 2019/01/24 13:38:32 [DEBUG] starting remote command: vim-cmd vmsvc/power.getstate 39
2019/01/24 13:38:32 packer_1.3.3: 2019/01/24 13:38:32 [DEBUG] Opening new ssh session
2019/01/24 13:38:32 packer_1.3.3: 2019/01/24 13:38:32 [DEBUG] starting remote command: vim-cmd vmsvc/power.on 39
2019/01/24 13:38:34 packer_1.3.3: 2019/01/24 13:38:34 [ERROR] Remote command exited with '1': vim-cmd vmsvc/power.on 39
2019/01/24 13:38:39 packer_1.3.3: 2019/01/24 13:38:39 [DEBUG] Opening new ssh session
2019/01/24 13:38:39 packer_1.3.3: 2019/01/24 13:38:39 [DEBUG] starting remote command: vim-cmd vmsvc/power.getstate 39
2019/01/24 13:38:39 packer_1.3.3: 2019/01/24 13:38:39 [DEBUG] Opening new ssh session
2019/01/24 13:38:39 packer_1.3.3: 2019/01/24 13:38:39 [DEBUG] starting remote command: vim-cmd vmsvc/power.on 39
2019/01/24 13:38:41 packer_1.3.3: 2019/01/24 13:38:41 [ERROR] Remote command exited with '1': vim-cmd vmsvc/power.on 39
2019/01/24 13:38:47 packer_1.3.3: 2019/01/24 13:38:47 [DEBUG] Opening new ssh session
2019/01/24 13:38:47 packer_1.3.3: 2019/01/24 13:38:47 [DEBUG] starting remote command: vim-cmd vmsvc/power.getstate 39
2019/01/24 13:38:48 packer_1.3.3: 2019/01/24 13:38:48 [DEBUG] Opening new ssh session
2019/01/24 13:38:48 packer_1.3.3: 2019/01/24 13:38:48 [DEBUG] starting remote command: vim-cmd vmsvc/power.on 39
2019/01/24 13:38:49 packer_1.3.3: 2019/01/24 13:38:49 [ERROR] Remote command exited with '1': vim-cmd vmsvc/power.on 39
2019/01/24 13:38:56 packer_1.3.3: 2019/01/24 13:38:56 [DEBUG] Opening new ssh session
2019/01/24 13:38:56 packer_1.3.3: 2019/01/24 13:38:56 [DEBUG] starting remote command: vim-cmd vmsvc/power.getstate 39
2019/01/24 13:38:57 packer_1.3.3: 2019/01/24 13:38:57 [DEBUG] Opening new ssh session
2019/01/24 13:38:57 packer_1.3.3: 2019/01/24 13:38:57 [DEBUG] starting remote command: vim-cmd vmsvc/power.on 39
2019/01/24 13:38:59 packer_1.3.3: 2019/01/24 13:38:59 [ERROR] Remote command exited with '1': vim-cmd vmsvc/power.on 39
2019/01/24 13:39:07 packer_1.3.3: 2019/01/24 13:39:07 [DEBUG] Opening new ssh session
2019/01/24 13:39:07 packer_1.3.3: 2019/01/24 13:39:07 [DEBUG] starting remote command: vim-cmd vmsvc/power.getstate 39
2019/01/24 13:39:07 packer_1.3.3: 2019/01/24 13:39:07 [DEBUG] Opening new ssh session
2019/01/24 13:39:07 packer_1.3.3: 2019/01/24 13:39:07 [DEBUG] starting remote command: vim-cmd vmsvc/power.on 39
2019/01/24 13:39:09 packer_1.3.3: 2019/01/24 13:39:09 [ERROR] Remote command exited with '1': vim-cmd vmsvc/power.on 39
2019/01/24 13:39:18 packer_1.3.3: 2019/01/24 13:39:18 [DEBUG] Opening new ssh session
2019/01/24 13:39:18 packer_1.3.3: 2019/01/24 13:39:18 [DEBUG] starting remote command: vim-cmd vmsvc/power.getstate 39
2019/01/24 13:39:19 packer_1.3.3: 2019/01/24 13:39:19 [DEBUG] Opening new ssh session
2019/01/24 13:39:19 packer_1.3.3: 2019/01/24 13:39:19 [DEBUG] starting remote command: vim-cmd vmsvc/power.on 39
2019/01/24 13:39:21 packer_1.3.3: 2019/01/24 13:39:21 [ERROR] Remote command exited with '1': vim-cmd vmsvc/power.on 39
2019/01/24 13:39:31 packer_1.3.3: 2019/01/24 13:39:31 [DEBUG] Opening new ssh session
2019/01/24 13:39:31 packer_1.3.3: 2019/01/24 13:39:31 [DEBUG] starting remote command: vim-cmd vmsvc/power.getstate 39
2019/01/24 13:39:31 packer_1.3.3: 2019/01/24 13:39:31 [DEBUG] Opening new ssh session
2019/01/24 13:39:31 packer_1.3.3: 2019/01/24 13:39:31 [DEBUG] starting remote command: vim-cmd vmsvc/power.on 39
2019/01/24 13:39:33 packer_1.3.3: 2019/01/24 13:39:33 [ERROR] Remote command exited with '1': vim-cmd vmsvc/power.on 39
2019/01/24 13:39:44 packer_1.3.3: 2019/01/24 13:39:44 [DEBUG] Opening new ssh session
2019/01/24 13:39:44 packer_1.3.3: 2019/01/24 13:39:44 [DEBUG] starting remote command: vim-cmd vmsvc/power.getstate 39
2019/01/24 13:39:44 packer_1.3.3: 2019/01/24 13:39:44 [DEBUG] Opening new ssh session
2019/01/24 13:39:44 packer_1.3.3: 2019/01/24 13:39:44 [DEBUG] starting remote command: vim-cmd vmsvc/power.on 39
2019/01/24 13:39:46 packer_1.3.3: 2019/01/24 13:39:46 [ERROR] Remote command exited with '1': vim-cmd vmsvc/power.on 39
2019/01/24 13:39:58 packer_1.3.3: 2019/01/24 13:39:58 [DEBUG] Opening new ssh session
2019/01/24 13:39:58 packer_1.3.3: 2019/01/24 13:39:58 [DEBUG] starting remote command: vim-cmd vmsvc/power.getstate 39
2019/01/24 13:39:58 packer_1.3.3: 2019/01/24 13:39:58 [DEBUG] Opening new ssh session
2019/01/24 13:39:58 packer_1.3.3: 2019/01/24 13:39:58 [DEBUG] starting remote command: vim-cmd vmsvc/power.on 39
2019/01/24 13:40:00 packer_1.3.3: 2019/01/24 13:40:00 [ERROR] Remote command exited with '1': vim-cmd vmsvc/power.on 39
2019/01/24 13:40:13 packer_1.3.3: 2019/01/24 13:40:13 [DEBUG] Opening new ssh session
2019/01/24 13:40:13 packer_1.3.3: 2019/01/24 13:40:13 [DEBUG] starting remote command: vim-cmd vmsvc/power.getstate 39
2019/01/24 13:40:14 packer_1.3.3: 2019/01/24 13:40:14 [DEBUG] Opening new ssh session
2019/01/24 13:40:14 packer_1.3.3: 2019/01/24 13:40:14 [DEBUG] starting remote command: vim-cmd vmsvc/power.on 39
2019/01/24 13:40:16 packer_1.3.3: 2019/01/24 13:40:16 [ERROR] Remote command exited with '1': vim-cmd vmsvc/power.on 39
2019/01/24 13:40:30 packer_1.3.3: 2019/01/24 13:40:30 [DEBUG] Opening new ssh session
2019/01/24 13:40:30 packer_1.3.3: 2019/01/24 13:40:30 [DEBUG] starting remote command: vim-cmd vmsvc/power.getstate 39
2019/01/24 13:40:30 packer_1.3.3: 2019/01/24 13:40:30 [DEBUG] Opening new ssh session
2019/01/24 13:40:30 packer_1.3.3: 2019/01/24 13:40:30 [DEBUG] starting remote command: vim-cmd vmsvc/power.on 39
2019/01/24 13:40:33 packer_1.3.3: 2019/01/24 13:40:33 [ERROR] Remote command exited with '1': vim-cmd vmsvc/power.on 39
2019/01/24 13:40:48 packer_1.3.3: 2019/01/24 13:40:48 [DEBUG] Opening new ssh session
2019/01/24 13:40:48 packer_1.3.3: 2019/01/24 13:40:48 [DEBUG] starting remote command: vim-cmd vmsvc/power.getstate 39
2019/01/24 13:40:48 packer_1.3.3: 2019/01/24 13:40:48 [DEBUG] Opening new ssh session
2019/01/24 13:40:48 packer_1.3.3: 2019/01/24 13:40:48 [DEBUG] starting remote command: vim-cmd vmsvc/power.on 39
2019/01/24 13:40:50 packer_1.3.3: 2019/01/24 13:40:50 [ERROR] Remote command exited with '1': vim-cmd vmsvc/power.on 39
2019/01/24 13:41:06 packer_1.3.3: 2019/01/24 13:41:06 [DEBUG] Opening new ssh session
2019/01/24 13:41:06 packer_1.3.3: 2019/01/24 13:41:06 [DEBUG] starting remote command: vim-cmd vmsvc/power.getstate 39
2019/01/24 13:41:07 packer_1.3.3: 2019/01/24 13:41:07 [DEBUG] Opening new ssh session
2019/01/24 13:41:07 packer_1.3.3: 2019/01/24 13:41:07 [DEBUG] starting remote command: vim-cmd vmsvc/power.on 39
2019/01/24 13:41:09 packer_1.3.3: 2019/01/24 13:41:09 [ERROR] Remote command exited with '1': vim-cmd vmsvc/power.on 39
2019/01/24 13:41:26 packer_1.3.3: 2019/01/24 13:41:26 [DEBUG] Opening new ssh session
2019/01/24 13:41:26 packer_1.3.3: 2019/01/24 13:41:26 [DEBUG] starting remote command: vim-cmd vmsvc/power.getstate 39
2019/01/24 13:41:26 packer_1.3.3: 2019/01/24 13:41:26 [DEBUG] Opening new ssh session
2019/01/24 13:41:26 packer_1.3.3: 2019/01/24 13:41:26 [DEBUG] starting remote command: vim-cmd vmsvc/power.on 39
2019/01/24 13:41:28 packer_1.3.3: 2019/01/24 13:41:28 [ERROR] Remote command exited with '1': vim-cmd vmsvc/power.on 39
2019/01/24 13:41:46 packer_1.3.3: 2019/01/24 13:41:46 [DEBUG] Opening new ssh session
2019/01/24 13:41:46 packer_1.3.3: 2019/01/24 13:41:46 [DEBUG] starting remote command: vim-cmd vmsvc/power.getstate 39
2019/01/24 13:41:46 packer_1.3.3: 2019/01/24 13:41:46 [DEBUG] Opening new ssh session
2019/01/24 13:41:46 packer_1.3.3: 2019/01/24 13:41:46 [DEBUG] starting remote command: vim-cmd vmsvc/power.on 39
2019/01/24 13:41:48 packer_1.3.3: 2019/01/24 13:41:48 [ERROR] Remote command exited with '1': vim-cmd vmsvc/power.on 39
2019/01/24 13:42:07 packer_1.3.3: 2019/01/24 13:42:07 [DEBUG] Opening new ssh session
2019/01/24 13:42:07 packer_1.3.3: 2019/01/24 13:42:07 [DEBUG] starting remote command: vim-cmd vmsvc/power.getstate 39
2019/01/24 13:42:08 ui error: ==> centos7base: Error starting VM: Retry limit exceeded
2019/01/24 13:42:08 packer_1.3.3: 2019/01/24 13:42:08 [DEBUG] Opening new ssh session
2019/01/24 13:42:08 packer_1.3.3: 2019/01/24 13:42:08 [DEBUG] starting remote command: vim-cmd vmsvc/power.getstate 39
2019/01/24 13:42:08 ui: ==> centos7base: Destroying virtual machine...
2019/01/24 13:42:08 packer_1.3.3: 2019/01/24 13:42:08 [DEBUG] Opening new ssh session
2019/01/24 13:42:08 packer_1.3.3: 2019/01/24 13:42:08 [DEBUG] starting remote command: vim-cmd vmsvc/destroy 39
2019/01/24 13:42:10 packer_1.3.3: 2019/01/24 13:42:10 [DEBUG] Opening new ssh session
2019/01/24 13:42:10 packer_1.3.3: 2019/01/24 13:42:10 [DEBUG] starting remote command: test ! -e "/vmfs/volumes/datastore-nas/centos7base"
2019/01/24 13:42:10 packer_1.3.3: 2019/01/24 13:42:10 [DEBUG] Opening new ssh session
2019/01/24 13:42:10 packer_1.3.3: 2019/01/24 13:42:10 [DEBUG] starting remote command: test -e "/vmfs/volumes/datastore-nas/centos7base"
2019/01/24 13:42:10 [INFO] (telemetry) ending vmware-iso
2019/01/24 13:42:10 ui error: Build 'centos7base' errored: Error starting VM: Retry limit exceeded
2019/01/24 13:42:10 Builds completed. Waiting on interrupt barrier...
2019/01/24 13:42:10 machine readable: error-count []string{"1"}
2019/01/24 13:42:10 ui error:
==> Some builds didn't complete successfully and had errors:
2019/01/24 13:42:10 machine readable: centos7base,error []string{"Error starting VM: Retry limit exceeded"}
2019/01/24 13:42:10 ui error: --> centos7base: Error starting VM: Retry limit exceeded
2019/01/24 13:42:10 ui:

==> Builds finished but no artifacts were created.

2019/01/24 13:42:10 [INFO] (telemetry) Finalizing.
2019/01/24 13:42:10 packer_1.3.3: 2019/01/24 13:42:10 [ERROR] Remote command exited with '1': test -e "/vmfs/volumes/datastore-nas/centos7base"
2019/01/24 13:42:11 waiting for all plugin processes to complete...
2019/01/24 13:42:11 /usr/local/bin/packer_1.3.3: plugin process exited

[Andrew Meyer]

I don't think I did that one.  But I know I enabled esxupdate.

[Stan Dorsett]

I also just noticed the 'connect via VNC with the password' in the logs. I typically use '"vnc_disable_password": true' to disable vnc passwords like in this example:
https://github.com/sdorsett/packer-centos7-esxi/blob/master/templates/centos-7-1708.01.json#L28

Stan

[Andrew Meyer]

Good to know, trying that now.

[Andrew Meyer]

Got the same retry limit exceeded error.

[Rickard von Essen]

Could you start a VM with the same configuration manualy on the ESXi? 

To view this discussion on the web visit https://groups.google.com/d/msgid/packer-tool/61d27175-cb05-4c34-b5c2-2e98b237419d%40googlegroups.com.

[Andrew Meyer]

Yes, I can create a new VM with the same specs manually.

[Andrew Meyer]

Got it working!  It was my guest_os_type.

[Jp Toto]

Would you mind providing your full Packer file for the working config?

JP Toto

 

---

From: packe...@googlegroups.com on behalf of Andrew Meyer <andre...@gmail.com>
Sent: Thursday, January 24, 2019 8:50 PM
To: Packer
Subject: Re: [packer] creating vms on standalone esxi host

 

To view this discussion on the web visit https://groups.google.com/d/msgid/packer-tool/cc201589-df82-4ea1-9dcd-d39e11996c50%40googlegroups.com.