[vagrant-up] Vagrant and Vcenter: direct workflow

2020-02-12 Thread dragon788
I believe the vSphere provider supports this, you may still use a connector labeled ESXi but it can be given the cluster address instead of a node address. -- This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior

[vagrant-up] Re: Vagrant and Vcenter: direct workflow

2020-02-12 Thread Mariusz
Nice! Thanks a lot, just searched for this and looks like your are right. In the documentation it says: "ESXi is not supported. Make sure to connect to a vCenter server and not directly to an ESXi host. ESXi vs vCenter "

[vagrant-up] vagrant up error

2020-02-12 Thread Robert McDougal
I am new to using vagrant, when I try to run the vagrant up command after doing the vagrant init, after following the tutorial directly from vagrants website, I keep getting the error saying "The virtual machine 'vagrant_1_default_1581565348939_70941' has terminated unexpectedly during startup

Re: [vagrant-up] Re: Vagrant and Vcenter: direct workflow

2020-02-12 Thread JP Toto
If you're trying to create instances on a remote server, like ESXi, Packer would be a better tool as it's purpose-built for the task. This https://nickcharlton.net/posts/using-packer-esxi-6.html is a good blog post for configuring ESXi to accept Packer commands and there is a link to a Github repo