My issue is I'd like to run a Visual Studio development environment on an M1. This seems like an excellent way of getting the best of both worlds in the absence of being able to run a WinDOS VM on an M1. A picture, with M1 MBP for size reference, weight like 200 grams, don't even feel it in the bag.
#Vmware fusion mac m1 chip plus
Plus a handy, although slow, wireless data storage. Have it set as wifi access point (2.4 only) and just remote into it from Mac. No battery, needs 12V power supply, USB-C but no PD. Mind you, my VMs are not loaded, thats pre-deployment. Once created it boots VM in less than a minute and I can do my stuff without really noticing any slowdowns. My M1 MBP does the same in VMWare fusion with same fedora but ARM version in about 6 minutes.
#Vmware fusion mac m1 chip iso
Surprisingly snappy, spinning Fedora 34 on it in VMware Workstation from DVD iso took 13 minutes. It is about the size of 2.5'' external SSD enclosure. I got one of those from Amazon, for like $250, quad core Celeron, passive cooled, 8GB RAM, 256 eMMC + open nvme m.2 slot in which I have 4TB SSD. I travel a lot, so pulling 30-100GB from my server is not an option on hotel wifi. For a regular work I can do just fine in ARM VMs. **Describe alternatives you've considered**Ĭlear documentation mentioning the architecture issues.The only thing I can't do on M1 is x86 VMs, and sometimes I need to spin one, configure and load on customer site, check somebody's backup etc. When specifying `bionic64` in your Vagrantfile, and that box does not exist for _your_ architecture, you should be told through an error message. (from a list of enums) when searching for images. 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.
0 kommentar(er)
