Re: [packer] Chef-solo provisioner very slow to upload cookbooks

2016-09-19 Thread James Bannan
Hi Sean, Sure, the template is this one, authored by Matt Wrock: https://github.com/mwrock/packer-templates/blob/master/vbox-2016.json Based on some additional research, it looks like this is a long-standing issue with the performance of the WinRM transport in Packer. However, I'm only trying

RE: [packer] Chef-solo provisioner very slow to upload cookbooks

2016-09-19 Thread Sean Farrow
Hi James, What template are you using, is it possible to provide a link? Cheers Sean. From: packer-tool@googlegroups.com [mailto:packer-tool@googlegroups.com] On Behalf Of James Bannan Sent: 20 September 2016 02:21 To: Packer Subject: [packer] Chef-solo provisioner very slow to upload cookbooks

[packer] Chef-solo provisioner very slow to upload cookbooks

2016-09-19 Thread James Bannan
Hi all, I'm using Packer 0.10.1 on Windows 10 to build a Windows 10 image on VirtualBox. The template uses the chef-solo provisioner, and i'm seeing that the upload of the cookbooks is extremely slow. Slow, as in, about 30 minutes to upload 4 cookbooks. It always works and never errors, but

[packer] Error exporting virtual machine: signal: trace/BPT trap

2016-09-19 Thread Ronnie
Hello, Can someone please explain why i am getting this error? 2016/09/19 16:39:59 ui: vmware-iso: Executing: ovftool --noSSLVerify=true --skipManifestCheck -tt=ovf vi://root:@8.1.132.86/packingtest packingtest/packingtest.ovf vmware-iso: Executing: ovftool --noSSLVerify=true -

[packer] Re: Error ovftool not found

2016-09-19 Thread Ronnie
Please find attached my packertest.json file. Please take a look at it and let me know where I am going wrong. Thanks On Monday, September 19, 2016 at 2:38:19 PM UTC-7, Rickard von Essen wrote: > > You don't have the executable ovftool on your path. I'm guessing you're > trying to run the vspher

[packer] Re: Error ovftool not found

2016-09-19 Thread Rickard von Essen
You don't have the executable ovftool on your path. I'm guessing you're trying to run the vsphere post-processor. On Monday, September 19, 2016 at 11:26:06 PM UTC+2, Ronnie wrote: > > Hello, > I get this error when I run my packer.json file. > > 2016/09/19 14:15:04 remote command exited with '0

Re: [packer] Re: Error ovftool not found

2016-09-19 Thread Alvaro Miranda Aguilera
hello if you are using vmware-iso remote to build in esx you shouldnt use vsphere post-processor. if you build locally, and you install ovftool vsphere post-processor can be used to upload to a remote esxi/vsphere box. not sure what will try to do if you build remote and try to use vsphere whic

[packer] Re: Error ovftool not found

2016-09-19 Thread Ronnie
vmware-iso: Error ovftool not found: exec: "ovftool": executable file not found in $PATH On Monday, September 19, 2016 at 2:26:06 PM UTC-7, Ronnie wrote: > > Hello, > I get this error when I run my packer.json file. > > 2016/09/19 14:15:04 remote command exited with '0': vim-cmd vmsvc/reload

[packer] Error ovftool not found

2016-09-19 Thread Ronnie
Hello, I get this error when I run my packer.json file. 2016/09/19 14:15:04 remote command exited with '0': vim-cmd vmsvc/reload 367 2016/09/19 14:15:04 ui error: ==> vmware-iso: Error ovftool not found: exec: "ovftool": executable file not found in $PATH 2016/09/19 14:15:04 packer: 2016/09/19

[packer] Re: Deploying a vm with packer with a static IP

2016-09-19 Thread Rjaydee
Can you please help me understand why this is happening? I have been trying for a while now, and I am still getting the same results On Friday, September 16, 2016 at 10:24:44 AM UTC-7, Rjaydee wrote: > > I am trying to deploy and set a vm using packer and a kickstart file. This > packer code: >

Re: [packer] EC2 Cloud Init / Networking

2016-09-19 Thread gorkhaan
I had the same "empty" /etc/resolv.conf as Matt had. Thanks for the official ks.cfg I will check it out when I have time and rebuild my AMI. For now I stick with the Official CentOS AMI. Thanks, G. On Thursday, September 15, 2016 at 11:06:27 PM UTC+1, Alvaro Miranda Aguilera wrote: > > hello >