Hacker News new | ask | show | jobs
by jsjohnst 3499 days ago
I thought the exact same thing. It's trivially simple to run custom kernels. Further, with currentish versions of OSX, you don't even need VMware/VB. The built-in hypervisor works good enough without crash prone kexts like in the alternative in my experience.

Not sure if you read the rest of the article, but it didn't do much to instill technical competence after that point either.

1 comments

Not claiming to be knowledgeable about OS X internals, but... it ships with a hypervisor now?

Is it at all similar to BSD jails?

Jails aren't a hypervisor. A jail is just a number in the process table. That's what the hipsters call "containers" these days :-)

FreeBSD's hypervisor is called bhyve (and it uses vmm.ko), and xhyve is a port of bhyve to macOS (uses Apple's Hypervisor.framework). There are other things that use Hypervisor.framework too.

Yeah, my bad, I was just short on sleep when I wrote that :P

Still nice to know about Hypervisor.framework. If I ever get back to OS X I'll have to check it out!

> There are other things that use Hypervisor.framework too.

Docker's macOS installer uses it rather than VirtualBox now if memory serves.

No, but there is a port of bhyve using the MacOS hypervisor.framework

https://github.com/mist64/xhyve

Or, if you want something with a GUI, there is Veertu:

https://veertu.com/