ParallelsĪs mentioned above, Parallels does have support for M1 macs but only for ARM based operating systems. While Trellis defaults to VirtualBox (since it's open source and free), it's always supported other providers like VMWare and Parallels. It defeats the purpose of VirtualBox which is very tied, by design, to x86. There has been absolutely no movement on Virtualbox offering ARM support and I highly doubt there ever will be. They are the same as the original M1 in that regard. The new M1 Pro and M1 Max CPUs don't change anything virtualization wise unfortunately. I've been looking into this a bit more lately, and here's what I've found. Anyone running M1 chips is unfortunately out of luck running for Trellis for at least the short-term and almost certainly for the medium-term too. My stance for now is nothing will change for a while. there's still a lot of potential problems and big open questions. So even if Trellis found a way to migrate to Docker. I personally don't really know the implications of running difference architectures in dev/prod yet. or are people willing to run ARM in development and then deploy to x86 in production?.will it become more common place to run ARM on production servers?.Trellis already supports other Vagrant providers which some people use. I think the key point is that Trellis is coupled to x86 more so than VirtualBox itself. VirtualBox likely won't ever work on M* chips until/if the above happens.it seems like virtualization support won't come until the next gen M2 chips (and that's just people's hopes).I haven't looked into this enough yet, but my interpretation of the current state of things is:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |