Re: [packer] Re: Packer v1.2.1 - WinRM communicator timeout
Thanks, Jon. Just out of curiosity, what version of Windows was your template? I have tried the code from the website and am still having no luck. However, I will double-check that WinRM is firing up on the VM before raising an issue. Cheers all, Dave. On Friday, April 13, 2018 at 4:54:38 PM UTC+1, j.r.haw...@googlemail.com wrote: > > Thanks for this, I hit the same thing with a template which had previously > worked. > I got rid of quickconfig and used the code from the windows example and > template works again. > > If you get stuck at this point if you can connect to the temp vm and poke > around you may well find like I did that winrm wasn't running and firewall > wouldn't allow winrm. > > Jon > > On Thursday, April 12, 2018 at 5:25:39 PM UTC+1, Megan Marsh wrote: >> >> One thing jumps immediately to mind. You're using quickconfig, which some >> users have found causes a race condition with Packer. Normally I find this >> issue to be only sporadic, but it's something to try. We have an example in >> our docs of a winrm config script that doesn't use quickconfig. >> >> >> https://www.packer.io/intro/getting-started/build-image.html#a-windows-example >> >> If that doesn't do it, I'd like you to open an issue on the Packer github >> for me, if you don't mind. >> >> Thanks! >> > -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/packer-tool/b2fdb5d4-2d04-4a30-bed9-5ad648edcce4%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[packer] Re: Packer v1.2.1 - WinRM communicator timeout
Hi Megan, Just to let you know that I have tried with Packer version 1.2.2 and still get the same issue. Cheers, Dave. On Friday, April 6, 2018 at 1:44:11 PM UTC+1, Dave Nelson wrote: > > Hey all, > > Am using the WinRM communicator with Packer 1.2.1 using the vmware-iso > builder. > > I get the WinRM timeout unless I specify the IP address of the target VM > using "winrm_host". My packer exe is on a different subnet to the target > VM but there is routing in place, as demonstrated that it works with > the winrm_host setting. > > When i run a 'netstat -ano | findstr "5985"' on my test machine (where > Packer is running) I can see that there is no attempt by the test machine > to 'talk' to the target VM. However, if I specify the winrm_host setting, > I see the test PC trying to connect on 5985 to the target VM's IP. > > I hope I am doing something glaringly wrong and you can tell me to stop > being daft. I have checked a fair few docks, example JSON files, etc, and > can't get a working solution. Any help would be gratefully received. > > Cheers, > > Dave. > > > -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/packer-tool/78927b48-3953-482c-929b-73384dc39047%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [packer] Packer v1.2.1 - WinRM communicator timeout
Hi Megan, No worries at all. Thanks for getting back to me :o) The test JSON file and WinRM config files are here: https://github.com/DaveDingle75/packer-windows If you need anything else, let me know. Cheers, Dave. On Friday, April 6, 2018 at 5:17:27 PM UTC+1, Megan Marsh wrote: > > Sorry to hear you're having trouble :( . Can you share the relevant parts > of your Packer config? It'll make it a lot easier to troubleshoot. > -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/packer-tool/42731364-fa71-4d4b-91fe-8d549e997d13%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[packer] Packer v1.2.1 - WinRM communicator timeout
Hey all, Am using the WinRM communicator with Packer 1.2.1 using the vmware-iso builder. I get the WinRM timeout unless I specify the IP address of the target VM using "winrm_host". My packer exe is on a different subnet to the target VM but there is routing in place, as demonstrated that it works with the winrm_host setting. When i run a 'netstat -ano | findstr "5985"' on my test machine (where Packer is running) I can see that there is no attempt by the test machine to 'talk' to the target VM. However, if I specify the winrm_host setting, I see the test PC trying to connect on 5985 to the target VM's IP. I hope I am doing something glaringly wrong and you can tell me to stop being daft. I have checked a fair few docks, example JSON files, etc, and can't get a working solution. Any help would be gratefully received. Cheers, Dave. -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/packer-tool/e706dcf4-e791-4b30-8f49-b66675c1430e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[packer] Packer - virtualHW.version
Hey all, Am using Packer version 1.2.1 Host Platform - ESXi 5.0 Am using Packer to create a Windows 7 image against one of our ESXi 5.0 hosts. Now, as the remote_type is esxi5, I didn't perceive any issues. However, as the default virtualHW.version is 9, I have specified "virtualHW.version": "8" in the "vmx_data" section of my JSON file. I also specified "version": 8 in the Builders section of the JSON file. When Packer tries building and writing the VMX file, the VM is registered on the ESXi host as 'unknown'. The VM fails to start and is then deleted as part of the clean-up process. Before the VM is deleted, I downloaded the VMX file and noted that virtualhw.version = "9". Does anyone know why? I am explicitly setting the virtual hardware version to 8 in the JSON file but it is being ignored. The ESXi host is being managed by a vCenter server (I am targeting the ESXi host directly) but is not part of any cluster so wondering if this is anything to do with it. Any clues as to why I am seeing this issue would be gratefully received. Cheers, Dave. -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/packer-tool/031bc20c-7701-4e77-b906-852eb6740c4c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
