Posted on June 10, 2021 7:13 pm
 |  Asked by Dave Hill
Print Friendly, PDF & Email

My vEOS vagrant box VMs aren’t booting – the VM GUI displays ‘ISOLINUX 4.05 2011-12-09…” and that’s it.

Eventually vagrant gets bored ands prints an error message.

In another post a user suggested including an Aboot ISO in vb.customize but it gets rejected as a possible syntax error. I’ve played around with this command but no dice.

I’ve tested using a vagrant init generated Vagrantfile and the bowtie environment and get the same results each time.

I’ve tried vEOS 4.15, 4.17 and 4.19

I’m using Big Sur, vagrant 2.2.16 and VB 6.1.22

Any suggestions?

Posted by Shawn Rogers
Answered on July 2, 2021 10:01 pm

Hi David,

I was able to get vEOS working on Vagrant 2.2.16 and VB 6.1.22 performing the following steps:

1. Install VB 6.1.22
2. Install Vagrant 2.2.16
3. Create a directory name 4.19.10M
4. Within this directory, created a file name Vagrantfile
5. After creating the file, add the information below to the file
Vagrant.configure("2") do |config| = "keepworld/veos-lab-4.19"
config.vm.box_version = "0.1"

6. From the directory 4.19.10M run the command "vagrant box add keepworld/veos-lab-4.19"
7. Next run the command "vagrant up"
After the command "vagrant up" finished running I was able to access the vEOS instance via "vagrant ssh" and the VB console.

vagrant ssh
Arista Networks EOS shell


Thank you
Shawn Rogers

Post your Answer

You must be logged in to post an answer.