5 ms·
I'm posting this because I've just found it. I'm trying to boot a custom toy kernel that I'm developing (with virtio support). Wish me good luck! OSDEV rocks!
by serhack_ 3y ago
I'm posting this because I've just found it. I'm trying to boot a custom toy kernel that I'm developing (with virtio support). Wish me good luck!
OSDEV rocks!
- serhack_ 3y agoJust a question: would anyone be interested in a good blog post explaining my journey with OSDEV and Virtualization.framework ?
- mike_hearn 3y agoSure, the collective internet programming community can always use good blog posts, especially on relatively obscure topics!
- mactunes 3y agoAbsolutely, that would be great!
- aa-jv 3y agoDon't ask, do. This is a fascinating subject. I'd be quite happy to see how a fat MacOS machine is being used as a build-server for multiple generations of MacOS versions, as well as how it could be used (via Linux VM's) to also build for Android, Linux, Windows, etc. Essentially, this subject is all about the build server destination; there is an award for how many different targets you can get from the same code-base, and being able to load up a fat Mac that approaches the nexus, is certainly of interest to us developers. VM's are key tools in modern build environments. Having a fat Mac running multiple VM's to solve the target/build infrastructure problem is fascinating on all fronts..
- sroussey 3y agoWould be great to run GitHub actions locally that use whichever VM is required.
- rtpg 3y agoMost definitely
- andyjohnson0 3y agoYes!
- serhack_ 3y agoyay! Understood
- sweetjuly 3y agoFair warning, you might be better suited by QEMU since debug support in Virtualization.framework is not great. QEMU has support for debug stubs out of the box. QEMU does support Hypervisor.framework so your performance should still be good through it, assuming you're using a matching architecture as your host (i.e. don't build an x64 kernel for your ARM Mac)