gvisor VS UTM

Isn't gVisor kind of this as well?

"gVisor is an application kernel for containers. It limits the host kernel surface accessible to the application while still giving the application access to all the features it expects. Unlike most kernels, gVisor does not assume or require a fixed set of physical resources; instead, it leverages existing host kernel functionality and runs as a normal process. In other words, gVisor implements Linux by way of Linux."

https://github.com/google/gvisor

This sort of feels like seeing someone riding a bike and saying: why don’t they just get a car? The simple fact is that containers and VMs are quite different. Whether something uses VMX and friends or not is also a red herring, as gVisor also “rolls it own VMM” [1].

[1] https://github.com/google/gvisor/tree/master/pkg/sentry/plat...

There's two major production-ready Go-based operating system(-ish) projects:

- Google's gVisor[1] (a re-implementation of a significant subset of the Linux syscall ABI for isolation, also mentioned in the article)

- USBArmory's Tamago[2] (a single-threaded bare-metal Go runtime for SOCs)

Both of these are security-focused with a clear trade off: sacrifice some performance for memory safe and excellent readability (and auditability). I feel like that's the sweet spot for low-level Go - projects that need memory safety but would rather trade some performance for simplicity.

[1]: https://github.com/google/gvisor

[2]: https://github.com/usbarmory/tamago

It uses gVisor to create a TCP/IP stack in userspace, and starts a wireguard interface on it, which the HTTP server from http.Serve listens on. The library will print a URL after startup, where you can access your server. You can create multiple listeners in one binary.

The playground compiles the program with GOOS=linux, GOARCH=amd64 and runs the program with gVisor. Detailed documentation is available at the gVisor site.

You could use a container sandbox like gVisor, light virtual machines as containers (Kata containers, firecracker + containerd) or full virtual machines (virtlet as a CRI).

If you have TrollStore then install the HV version of UTM to try for yourself: https://github.com/utmapp/UTM/releases/latest/download/UTM.HV.ipa

Researching a little showed that this is basically what can be expected running x86 emulation and the systems will just be wonky and slow, although it was running flawlessly, just slow.

There seem to be ways to use Rosetta2 inside a VM [0] to then translate binaries but I found no official support or documentation (using UTM+QEMU that was), this would be such a cool feature, at least there are discussions about it [1,2]

- [0] https://mybyways.com/blog/using-rosetta-in-a-utm-linux-vm-wi...

- [1] https://github.com/utmapp/UTM/discussions/4939

- [2] https://github.com/utmapp/UTM/issues/5460

UTM is open source too though: https://github.com/utmapp/UTM#license

UTM makes it easy to set up and manage macOS and Windows virtual machines. This can be especially useful for developers such as Tauri contributors who need to test their applications across multiple platforms, or for those looking to experiment with different operating systems without affecting their primary system.

If you don't need high performance and want to use the OS only occasionally, check UTM.app, at https://mac.getutm.app/ (or https://github.com/utmapp/UTM ). Free, open source.