Four years on a shared remote machine before building the local backend is a good lesson in when to invest in dev tooling versus living with the workaround.
Virtualization.framework isn't particularly limited, for what it is... given they're using Firecracker on Linux, it makes sense to use a similarly high level API on macOS.
(One could add a Hypervisor.framework backend to Firecracker, though I'd be surprised if AWS accepted it.)
I just encountered the `com.apple.private.virtualization` entitlement limitation just last night, wanting to use VZVirtualMachine private AccessorEndpoint api. There's lot of useful stuff hidden in Apple's Private API space.
Great write up! I enjoy seeing others working in the same problem space.
(One could add a Hypervisor.framework backend to Firecracker, though I'd be surprised if AWS accepted it.)
Great write up! I enjoy seeing others working in the same problem space.
They are solving the wrong problem.