this was done a few years ago. dont know if this method still works. http://www.jedi.be/blog/2011/11/04/vagrant-virtualbox-hostonly-pxe-vlans/
also found this, but havent had time to try it. https://github.com/dsbaars/vagrant-pxe On Friday, February 26, 2016 at 1:06:53 PM UTC-8, Charles Llewellyn wrote: > > Hi All, > > I'm trying to use vagrant to mock our bare-metal provisioning > configuration. We use razor and PXE to build our hypervisors and puppet to > manage their configuration. I am trying to create a Vagrant setup so we can > test stuff locally. > > We are using the VMware provider. > > The best solution would be to have an option to specify PXE boot of some > VMs in a multi VM deployment. > > Failing this I have got it working so that Vagrant deploys a blank VM and > have reduced the timeout so it fails fast. The issue is the failure to boot > causes Vagrant to exit, stopping me deploy multiple PXE machines. > > My questions are: > > 1. Is there a way a supported way to deploy "blank" VMs with Vagrant for > PXE (with the VMware provider) > 2. Is there a way to ignore boot errors/timeouts and continue to deploy > the next machine with "vagrant up" > > Cheers > > Charlie > -- 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/vagrant/issues IRC: #vagrant on Freenode --- You received this message because you are subscribed to the Google Groups "Vagrant" 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/vagrant-up/bb261127-d7e9-4e2e-ae64-ac0cacbe9dcb%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
