Thanks Rickard. I ended up creating the VM with a vmxnet3 adapter, installing the driver for that nic (inf file) on the VM so I could get network connectivity and then downloading and installing the vmware tools using chocolatey.
On Tuesday, 23 July 2019 08:48:55 UTC-7, Rickard von Essen wrote: > > iso_paths is for specifying multiple alternative urls for the same iso. > Instead put the tools iso in the http_directory or somewhere else where you > can reach it and download it to the VM. Then use the procedure used here *) > to install it. > > *) https://github.com/boxcutter/windows/blob/master/script/vmtool.bat > > On Tue, Jul 23, 2019 at 1:12 AM MTorres <[email protected] <javascript:>> > wrote: > >> Hi all, >> >> Having some issues using Packer and the vsphere-iso builder to create a >> Windows VM in vSphere. >> VM to be created: Windows 2019 STD >> vSphere version: 6.5 (vCenter and ESXi) >> Packer version: 1.3.5 >> vSphere-iso version: 2.3 >> >> The problem is, I need to load two ISO files: One for the Windows >> install and one for the VMWare tools install. >> If I load both from a datatore using "iso_paths" it works great, the >> first CD drive mounts the Windows iso and the second one mounts the VMware >> Tools iso and I get the VM created. >> >> If I load the Windows iso from a url using "iso_urls" and the VMware >> tools from the datastore using "iso_paths" then I get the VMware Tools >> loaded in the first CD drive and the Windows iso on the second CD drive and >> of course this doesn't work since the VM is trying to boot using the first >> drive. >> >> Is there a way to force the CDs to load in the correct order? or what >> other way can I install the VMware tools? If I don't install VMware tools >> the build never finishes because it either never gets an IP address (when >> using vmxnet3 adapter) or gets an IP but somehow doesn't report it back to >> Packer (when using e1000 adapter). >> >> Any help is appreciated, 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 [email protected] <javascript:>. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/packer-tool/e5d4148a-7c8a-4c36-85d0-fa470c341bbe%40googlegroups.com >> >> <https://groups.google.com/d/msgid/packer-tool/e5d4148a-7c8a-4c36-85d0-fa470c341bbe%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> > -- 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/6cfbcf36-31b9-46de-bde3-a79f41ba6d65%40googlegroups.com.
