Ladar Levison

If anyone stumbles across the logs I attached to this issue, I decided to open up a separate issue detailing the cause. Unfortunately my attempt to make a quick, short...

The referenced log files. [vagrant-lockout-1.txt](https://github.com/hashicorp/vagrant/files/8428490/vagrant-lockout-1.txt) [vagrant-lockout-2.txt](https://github.com/hashicorp/vagrant/files/8428491/vagrant-lockout-2.txt)

@dragetd I've been pushing for this for years! My goal was to start embedding the signatures when the base box is built, by adding support to `packer` then focus on...

@federico-razzoli I meant to reply right away, and started to, but got pulled away. What I wanted to ask 3 weeks ago was whether you, or @ar @chrisroberts @azr @dragetd...

P.S. I still can't believe the great and powerful @SwampDragons are no longer committing to the packer repo. You will be missed.

@federico-razzoli I didn't know Vagrant was being refactored into Go, but I've spent all the time I have for the Robox project on maintaining/adding to the box configs. That takes...

@VincentSaelzler sorry for taking so long to get back to you. I think you just missed the last merge window, and I generally can't keep up with my GitHub issue...

@VincentSaelzler I added the existing test and check scripts to the project, in the aptly named `check` directory. Inside you'll find the `check.sh` script, which is similar to the `robox.sh`...

@VincentSaelzler the hardware requirements are relatively low. All you need is enough to run a single VM at a time. That said, the more resources you have, the more boxes...

> I believe they are Intel Xeon E5 2620 v2 Hi @VincentSaelzler those processor should be just fine. Most of my rackmount servers use the same, although the blade servers...