Hmm, I see that the correct boot option is chosen now, but the device is immediately forcibly halted after the “boot_command” is executed:
...
==> vmware-iso: Creating required virtual machine disks
==> vmware-iso: Building and writing VMX file
==> vmware-iso: Starting virtual machine...
==> vmware-iso: Waiting 10s for boot...
==> vmware-iso: Connecting to VM via VNC (127.0.0.1:5927)
==> vmware-iso: Typing the boot command over VNC...
==> vmware-iso: Forcibly halting virtual machine...
vmware-iso: Waiting for VMware to clean up after itself...
==> vmware-iso: Deleting unnecessary VMware files...
vmware-iso: Deleting: output-vmware-iso/TW-Connect-2.0-packer-test.plist
vmware-iso: Deleting: output-vmware-iso/startMenu.plist
vmware-iso: Deleting: output-vmware-iso/vmware.log
==> vmware-iso: Compacting all attached virtual disks...
vmware-iso: Compacting virtual disk 1
==> vmware-iso: Cleaning VMX prior to finishing up...
vmware-iso: Detaching ISO from CD-ROM device ide0:0...
vmware-iso: Disabling VNC server...
==> vmware-iso: Skipping export of virtual machine (export is allowed only for ESXi)...
Build 'vmware-iso' finished.
Shouldn’t the “pause_before_connecting” command handle that?
"shutdown_command": "",
"pause_before_connecting": "5m",
"boot_command": [
"<down>",
"<down>",
"<down>",
"<enter>"
]
}]
}