31–40 of 127 posts
Earlier quoted context omitted.
Virtualization is, of course, based on a very standard KVM-like API. There's not much Mach in its design at all.
Mach is down below. This is what Mach is for the BSD that was originally part of the DARPA deliverable was just to prove that Mach could run on OS.
^^ For the curious ones :)
More or less it's an abstraction on top of Hypervisor to make VMs much simpler in Swift.
From what I remember, Docker tried to use this but suffered greatly on disk performance.
Earlier quoted context omitted.
Well damn that is pretty cool. I’ve not used UTM or the Apple Virt Framework but gonna have to look into that now! Thank you for the link.
UTM also have their own docs on it: https://docs.getutm.app/advanced/rosetta/ And FYI, this is also available in Docker Desktop for macOS, which allows better performance when running x86_64 containers compared to the older solution where Docker was using qemu.
Last time I checked, Rosetta only worked for one-off binaries, wouldn’t really allow docker to run more x86 code inside.
Has there been a significant development? Been using it with https://mac.getutm.app/ for a while
The only thing I'd like to see added to the framework is the ability for nested virtualization (which is now available in the M2 chips, but isn't built into M1 chips).
Has there been a significant development? Been using it with https://mac.getutm.app/ for a while
I've also been using the Apple Virtualization option with Linux VMs in UTM and have had zero issues whatsoever. The biggest benefit to doing so in my opinion isn't necessarily the noticeably better performance, but the RAM usage. I've noticed that Linux VMs in UTM that run using the Apple Virtualization Framework use significantly less RAM compared to otherwise because the framework provides dynamic memory allocation…
Earlier quoted context omitted.
Well damn that is pretty cool. I’ve not used UTM or the Apple Virt Framework but gonna have to look into that now! Thank you for the link.
UTM also have their own docs on it: https://docs.getutm.app/advanced/rosetta/ And FYI, this is also available in Docker Desktop for macOS, which allows better performance when running x86_64 containers compared to the older solution where Docker was using qemu.
I'm curious whether someone has found a good option for running x86 images on m1 chips.
I'm generally happy with the multipass VMs I'm creating but they are arm architecture so then if i use docker images inside them I'm limited to arm images. Maybe I just haven't explored how to run x86 correctly within multipass?
I'm finding that usually arm images are a step behind the x86 images if they are official, or they are built by someone outside the organization, so I'm never sure I'm using a safe image.
Do any of the options here make it performant to run x86 on apple silicon? Some interesting comments on Rosetta that I don't fully understand.
Earlier quoted context omitted.
UTM also have their own docs on it: https://docs.getutm.app/advanced/rosetta/ And FYI, this is also available in Docker Desktop for macOS, which allows better performance when running x86_64 containers compared to the older solution where Docker was using qemu.
Do you have any sources for that? I basically gave up on Docker for M1 since the qemu performance is terrible. Last time I checked, Rosetta only worked for one-off binaries, wouldn’t really allow docker to run more x86 code inside.