There aren't any boot arguments
Packer template is:
{
"variables": {
"mydatastore": "xxxxx"
},
"builders": [
{
"iso_url" :"
http://care.dlservice.microsoft.com/dl/download/6/2/A/62A76ABB-9990-4EFC-A4FE-C7D698DAEB96/9600.17050.WINBLUE_REFRESH.140317-1640_X64FRE_SERVER_EVAL_EN-US-IR3_SSS_X64FREE_EN-US_DV9.ISO
",
"iso_checksum_type": "sha1",
"iso_checksum": "849734f37346385dac2c101e4aacba4626bb141c",
"communicator": "winrm",
"winrm_username": "testing",
"winrm_password": "mytest",
"boot_wait" : "6h",
"name": "kb-win-tst-{{isotime \"2006-01-02\"}}",
"floppy_files": [
"answer/Autounattend.xml",
"answer/PackerShutdown.bat",
],
"vmx_data": {
"ethernet0.networkName": "VM Network",
"ethernet0.present": "TRUE",
"ethernet0.virtualDev": "vmxnet3",
"cpuid.coresPerSocket": "1",
"memsize": "1024",
"numvcpus": "1",
"scsi0:0.fileName": "disk.vmdk",
"scsi0:0.present": "TRUE",
"scsi0:0.redo": "",
"disk_size" : "50000"
},
"type": "vmware-iso",
"winrm_timeout": "94h",
"shutdown_command": "a:/PackerShutdown.bat",
"shutdown_timeout": "72h"
}
],
"provisioners": [
],
"post-processors": [
{
"type": "vsphere",
"host": "xxxxx",
"username": "xxxxx",
"password": "xxxxx",
"datacenter": "xxxx",
"cluster": "xxxx",
"resource_pool": " ",
"datastore": "{{user `mydatastore`}}",
"vm_folder": "",
"vm_name": "xxxxxx",
"vm_network": "VM Network",
"insecure" : "true"
}
]
}
I've configured the boot wait to 6h there so i could see if it builds, (as
it happens I have another issue where win2012r2 doesn't like the SCSI
controller vmware player uses but that's another story) but if I remove
that line the output gives me:
==> kb-win-tst-2016-10-06: Deleting output directory...
Build 'kb-win-tst-2016-10-06' errored: Error connecting to VNC: dial tcp
127.0.0.1:5940: connectex: No connection could be made because the target
machine actively refused it.
==> Some builds didn't complete successfully and had errors:
--> kb-win-tst-2016-10-06: Error connecting to VNC: dial tcp 127.0.0.1:5940:
connectex: No connection could be made because the target machine actively
refused it.
==> Builds finished but no artifacts were created.
On Thu, Oct 6, 2016 at 10:21 AM, Alvaro Miranda Aguilera <[email protected]>
wrote:
> Hello
>
> My understanding is the VNC is used as console to send the commands for
> the boot.
>
> Can you share your packer template?
>
> Do you have boot arguments at all ?
>
> If your version of player is higher on whats in packer, then the issue is
> on the version check rather than VNC part.
>
> Alvaro.
>
> On Thu, Oct 6, 2016 at 9:37 AM, Keith Baker <[email protected]>
> wrote:
>
>> Hi,
>>
>> I'm running packer on VMWare player, and rather than hack the binary with
>> a hex editor, as I'm not running any boot commands and just running an
>> autounattend.xml (windows box) and then planning to connect with winRM
>> afterwards, is there a way to disable the VNC connection?
>>
>> My issue is that the machine starts to build and I can watch it building
>> but the VNC connection fails. As I don't need the VNC connection for this
>> build, I'd rather just turn it off than hack the binary.
>>
>> Thanks
>>
>> Keith
>>
>> --
>> 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 [email protected].
>> To view this discussion on the web visit https://groups.google.com/d/ms
>> gid/packer-tool/fbe27c17-2e2c-4daf-90a9-79932641465e%40googlegroups.com
>> <https://groups.google.com/d/msgid/packer-tool/fbe27c17-2e2c-4daf-90a9-79932641465e%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> --
> Alvaro
>
> --
> 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 a topic in the
> Google Groups "Packer" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/
> topic/packer-tool/l8knPkBJ5CM/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> [email protected].
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/packer-tool/CAHqq0ezY8AmECXaO8FtS8Yorkwb39
> KUCGSs-03hS9U87dbE5Mg%40mail.gmail.com
> <https://groups.google.com/d/msgid/packer-tool/CAHqq0ezY8AmECXaO8FtS8Yorkwb39KUCGSs-03hS9U87dbE5Mg%40mail.gmail.com?utm_medium=email&utm_source=footer>
> .
>
> For more options, visit https://groups.google.com/d/optout.
>
--
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 [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/packer-tool/CAGW2uWCnfsbxrvA0t94JViYNMv4AxOQGPeoSjwzCkAHB3qa77g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
