3 ms·

I like Vagrant, but I don't know how I'm going to keep using it when I switch to Apple Silicon (M1 Macs). Vagrant wraps around Oracle VirtualBox; VirtualBox doe

I like Vagrant, but I don't know how I'm going to keep using it when I switch to Apple Silicon (M1 Macs). Vagrant wraps around Oracle VirtualBox; VirtualBox doesn't support M1 Macs, and Oracle has given no indication that they plan to start supporting Apple Silicon at all. Is there any working version of Vagrant that "just works" on M1 out of the box without paying for a VM provider? If not, would I have to pay for VMWare and then use Vagrant to wrap that? Would I use Vagrant to wrap Docker? (Why would I bother to use Vagrant if I'm using Docker?)

tmzt 5y ago
Packer and other Hashicorp products support alternative VM drivers including bhyve and support for hyperkit. The current ruby Vagrant supports plugins, but I'm not aware of bhyve or hyperkit support. I would assume rewriting in Go means the same VM drivers as packer will be supported.
mitchellh 5y ago
We just open sourced our VMware plugin so yes, we will support M1 there. Note that VMware Fusion for personal use is now free so you can get that whole setup completely free when its ready. Beyond that, we're looking into also writing a native Virtualization.framework implementation so you wouldn't need any 3rd party virtualization software at all. For headless Linux VMs we're confident this will work great. We're also looking at qemu as an option because qemu also offers emulation for x86. Being written in Go, we can bind to qemu natively much more easily. The point being: there will be multiple options!
- justinclift 5y ago
  Heh Heh Heh Might be time for getting that Vagrant-Libvirt link happening after all? ;)
  - zdw 5y ago
    This? https://github.com/vagrant-libvirt/vagrant-libvirt https://github.com/vagrant-libvirt/vagrant-libvirt It's been happening for a while now...
    - justinclift 5y ago
      Nah. Mitchell had been looking at leveraging Libvirt for vagrant a few years before that. ;)

tmzt 5y ago

Packer and other Hashicorp products support alternative VM drivers including bhyve and support for hyperkit. The current ruby Vagrant supports plugins, but I'm not aware of bhyve or hyperkit support. I would assume rewriting in Go means the same VM drivers as packer will be supported.

mitchellh 5y ago

We just open sourced our VMware plugin so yes, we will support M1 there. Note that VMware Fusion for personal use is now free so you can get that whole setup completely free when its ready. Beyond that, we're looking into also writing a native Virtualization.framework implementation so you wouldn't need any 3rd party virtualization software at all. For headless Linux VMs we're confident this will work great. We're also looking at qemu as an option because qemu also offers emulation for x86. Being written in Go, we can bind to qemu natively much more easily. The point being: there will be multiple options!

justinclift 5y ago
Heh Heh Heh Might be time for getting that Vagrant-Libvirt link happening after all? ;)
- zdw 5y ago
  This? https://github.com/vagrant-libvirt/vagrant-libvirt https://github.com/vagrant-libvirt/vagrant-libvirt It's been happening for a while now...
  - justinclift 5y ago
    Nah. Mitchell had been looking at leveraging Libvirt for vagrant a few years before that. ;)