Hi there! I want to use Vagrant to create and deploy 5 different virtual machines. They use a custom box and some of them are on a different internal network, but when I run ‘vagrant up’, only the first VM is created, and the second one won’t be created until the first one is closed, and so on. It doesn’t let me execute either ‘vagrant ssh’ or any command, I have to press Ctrl-C every time. I’ve attached my Vagrantfile and I believe I haven’t made any mistake. I use Vagrant 2.2.16 on Windows. Thanks!
Vagrantfile.txt (2.5 KB)
but when I run ‘vagrant up’, only the first VM is created, and the second one won’t be created until the first one is closed, and so on.
This is expected behavior for the Virtualbox provider. From the linked docs
The Vagrant VirtualBox provider does not support parallel execution at this time. Specifying the
--paralleloption will have no effect.
About Vagrant being unresponsive
It doesn’t let me execute either ‘vagrant ssh’ or any command, I have to press Ctrl-C every time.
Could you provide debug log for this? That will help uncover what part Vagrant is getting stuck at. Thanks!
Hey, sorry for not answering earlier. The problem is produced by the command sudo ifconfig enp0s3 down, when provisioning. If I execute vagrant up --no-provision, it works perfectly, but if I run vagrant ssh and then that command, it also hangs. Here’s the debug log after executing vagrant provision --debug. If you need more info, I’ll try to provide it ASAP. Thanks!
provision.txt (240.7 KB)
Nevermind, I figured out where’s the problem: I can’t disable the NAT adapter because, if I do, the SSH connection hangs! I feel incredibly stupid right now hahaha. Thank you anyways!