macOS 26 introduces the Containerization Framework: "enables developers to create, download, or run Linux container images directly on Mac"
-
This post did not contain any content.
Proud of you!
-
This post did not contain any content.
Embrace <-- You are here
Extend
Extinguish
Fuck Apple
-
You're right. I wouldn't, but someone did for me!
If it's a work computer, tell your IT department it's getting in the way of your job.
-
You're doing it wrong. I want to run a macOS container on Linux
But why?
-
virtio-gpu with Vulkan pass through for the VM with a Vulkan to Metal translator in host user space. There are various talks about this including at KVM forum: https://kvm-forum.qemu.org/2024/The_many_faces_of_virtio-gpu_F4XtKDi.pdf
Is Apple’s tech going to be using KVM machinery then, or are you just saying that it’s possible in general?
-
Is Apple’s tech going to be using KVM machinery then, or are you just saying that it’s possible in general?
wrote last edited by [email protected]No the Apple hypervisor is called hvf, but projects like rust-vmm and QEMU can control and service guests run on that hypervisor. No KVM required.
-
No the Apple hypervisor is called hvf, but projects like rust-vmm and QEMU can control and service guests run on that hypervisor. No KVM required.
Oh that’s cool! I thought virtio and such were KVM-specific things. I have never been super clear on the relationship between QEMU and the hypervisor itself, like where one ends and the other begins.
-
This post did not contain any content.
When all you hire are web devs everything becomes a docker
-
But why?
Certain application only has Mac OS or Windows version.
-
This isn't a Linux post.
While I read the title I was thinking “that sounds like Linux with extra steps” - maybe that’s good enough for some discussion.
-
This post did not contain any content.
-
When all you hire are web devs everything becomes a docker
docker?! i hardly knew her!
-
This post did not contain any content.
Isn't it this one ?
https://github.com/apple/containerization -
Oh that’s cool! I thought virtio and such were KVM-specific things. I have never been super clear on the relationship between QEMU and the hypervisor itself, like where one ends and the other begins.
wrote last edited by [email protected]VirtIO was originally developed as a device para-virtualization as part of KVM but it is now an OASIS standard: https://docs.oasis-open.org/virtio/virtio/v1.3/virtio-v1.3.html which a number of hypervisors/VMM's support.
The line between what a hypervisor (like KVM) does and what is delegated to a Virtual Machine Monitor - VMM (like QEMU) is fairly blurry. There is always an additional cost to leaving the hypervisor to the VMM so it tends to be for configuration and lifetime management. However VirtIO is fairly well designed so the bulk of VirtIO data transactions can be processed by a dedicated thread which just gets nudged by the kernel when it needs to do stuff leaving the VM cores to just continue running.
I should add HVF tends to delegate most things to the VMM rather than deal with things in the hypervisor. It makes for a simpler hypervisor interface although not quite as performance tuned as KVM can be for big servers.
-
It supports Rosetta2, so yes.
However, with macOS 26 (Tahoe) being the final version for Intel-based Macs, Rosetta 2 will be on the chopping block afterwards.
-
Embrace <-- You are here
Extend
Extinguish
Fuck Apple
wrote last edited by [email protected]I'll believe it if I see it.
-
While I read the title I was thinking “that sounds like Linux with extra steps” - maybe that’s good enough for some discussion.
Not here, it's not.
