Closed karnold closed 8 years ago
+1 experiencing this issue. Although I'm not specifying vsphere.vlan, mac or data_store_name.
@karnold Give these instructions a try. I was able to get VM provisioning to work following these steps.
0) Convert your template to VM and power on. 1) Uninstall old vmware-tools 2) Uninstall any open-vm-tools packages 3) Install open-vm-tools and open-vm-tools-deploypkg 4) Make sure there are no startup errors waiting for user input. If so, resolve them. 5) Shutdown VM and convert to template 6) From vSphere/vCenter UI, make sure you can: A) Deploy VM from template WITHOUT customization spec B) Deploy VM from template WITH customization spec If network adapter is connected in A but disconnected in B, your open-vm-tools-debloypkg is missing or corrupt. Start over from top. 7) Launch your VM from Vangrant+vsphere WITHOUT customization spec and ensure network adapter is connected. If not, verify your Vagrantfile is using correct VM template. 8) Launch your VM from Vagrant+vsphere WITH customization spec and ensure network adapter is connected. If you're having issues on this step, enable open-vm-tools logging on template then re-launch VM using Vagrant+vpshere. http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1007873 (although it's written for old vmware-tools, it works under open-vm-tools).
Looks like that did the trick. I did not have open-vm-tools-deploypkg installed, only open-vm-tools. Thanks for your help!!!
Upon provisioning a new server, the vlan and mac address are set correctly, but the NIC is disabled and I have to enable it through vSphere Client before the network works