Closed garrettr closed 7 years ago
Before merging, I want to make sure this doesn't break anyone else's workflow. Therefore, I expect vagrant up
from a fresh clone of this branch to work with the virtualbox
and libvirt
providers.
Tested libvirt functionality, and was able to create a new machine from scratch no problem. Loaded the port-forwarded interface in my web browser. So A-OK on the libvirt support. Can't comment on the virtualbox support, but I think it's fine to leave in there—it would still theoretically be useful for macOS users.
By the way, the initial migration took about a minute on my machine:
real 0m55.498s
user 0m11.060s
sys 0m0.332s
By the way, the initial migration took about a minute on my machine:
Cool, it consistently takes about 1m20s on my machine, which has identical hardware to yours but is running Qubes. Looks like the 20s overhead might be Qubes' fault, but since the same migration was taking about 10-15s on my MacBook Pro (with an SSD), I think it's safe to say that most of the overhead I've been encountering is due to HDD vs. SSD.
Damn, how did we even live before SSDs?
Provides a Qubes-compatible alternative for automatically provisioning a development environment for Secure The News.
Moves
config.vm.box
definition inside thevirtualbox
andvagrant
provider-specific configuration blocks, since it is only relevant to them and causes errors when used in conjunction with the Docker provider.