Ignoring errors and PXE boot

[Charles Llewellyn]

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

[Alvaro Miranda Aguilera]

Hello,

Time by time people came with similar requests for PXE. 

The problem with Vagrant is its expect some OS and be able to ssh into the box. And the first nic will be NAT all the time.

So for Vagrant, if you add a private_network, or a public_network, it should do better for boot.

You may need to use VBoxManage to tell boot over PXE, etc.

My suggestion will be search on google groups for PXE to see past threads, and have a look at packer to create a VM. If you pass a non-bootable iso, it should go for PXE.

Other trick is on packer you have same access to VBoxManage, so any change you do, it should work.

--
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 vagrant-up+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/2b813ee2-062a-4793-96be-9670a2e9c22d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[pixel fairy]

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

[Charles Llewellyn]

Thanks both for spending the time to look at this.

I have seen http://www.jedi.be/blog/2011/11/04/vagrant-virtualbox-hostonly-pxe-vlans/ before however it appears to be centred around virtualbox and some of our team is using VMware, not a major issue but we are trying to remain agnostic.

The other post seems to just build a PXE server, not manage the deployment of blank nodes for PXE installations with Vagrant.

TBH just being able to continue on a provisioning error would be useful as I have a working PXE image deploying via Vagrant but it fails as it never "connects" successfully after deployment.

I'll do some more work to investigate the solutions you have mentioned and try to post what works for others.

Cheers again