Vagrant Cloud should require an `architecture` field for new boxes and let users filter on `amd64` (`x86`?), `arm64`, etc. You cannot filter boxes on Vagrant Cloud by architecture, nor will you get a good error message if one does not run on your provider due to architecture mismatch.

Even if they should be able to to get VMWare Fusion playing nicely with Vagrant, the issue of finding boxes that runs on the right provider is left missing.

**Is your feature request related to a problem? Please describe.**Ī lot of dev … elopers are now on ARM architectures. can be found in the issue, if deemed relevant. I have no idea how running (a presumed) x86-64 image on ARM would work (if at all), or if Fusion on ARM is only capable of running ARM images on ARM.Īnyone had success with this or has any knowledge to share? This could of course be because almost every bit in this equation is bleeding edge (or at least pretty fresh):īut it could also be that I simply don’t know how one would use Vagrant on vmware. Vagrant encountered an unexpected communications error with the So I installed Vagrant, the VMWare utilities, the provider and whatnot and could see something happening, but ultimately failing (resulting in this bug report). Unfortunately, Virtualbox does not run on Apple Silicon (the M1 Macbook), so I thought I was out of luck, until I read that VMWare has its own provider and they just (September) released a Tech Preview of Fusion that runs on Apple Silicon! After seeing the abysmal I/O performance of Docker up close on macOS I decided to give Vagrant a go.

Vmware fusion macbook pro m1