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?

Post your Answer

You must be logged in to post an answer.