Hello, I'm using vagrant-libvirt to bring up a large number of machines. After 254, they all get stuck at "waiting for IP". I'm thinking it may be maxing out the management network. Any ideas on how to get around this?
All new ones after 254*
I was able to set the management_network_address to 188.8.131.52/16 and get it working if anybody wonders
What the difference between vagrant reload --provision and vagrant provision?
reload = "halt + up"
vagrant provision just re-runs the provisioning step only
I have made changes to Homestead.yaml
idk what that means
dealing with an issue, hoping you'll all know exactly what i'm doing wrong: https://gist.github.com/jblac/7f8e877a6aeb6d241ea0d4b34c89de8c
if i ssh in and run 'sudo salt-call state.highstate' it runs just fine however.
so, been away from vagrant for at least a couple of years, forgotten some things but I need a pointer on getting started again. Due to management/hardware constraints, I'm trying to run vagrant w/VirtualBox, inside of an ESXi6 VM.
I don't have XServer installed in the host VM so can't run the GUI, but I'm not sure if I've got the vbox networking setup that I need
I'm experimenting with the bento/centos-7.1 box. It seems to run but vagrant can't get an ssh connection.
I see no vmnics...
Does the VirtualBox RPM install on CentOS leave stuff that I need to configure before it will even do default NAT networking?
or should vagrant tack that on?
(the latter question being why I asked in here at all and not just in #vbox)