Our great sponsors
-
OSX-KVM
Run macOS on QEMU/KVM. With OpenCore + Monterey + Ventura + Sonoma support now! Only commercial (paid) support is available now to avoid spammy issues. No Mac system is required.
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
-
Take a look here https://github.com/kholia/OSX-KVM. Post install, I use the "Opencore-Boot.sh" script to boot the machine and inside of it modify the cpu "Penryn" to Icelake one assuming you're running a Ryzen one.
I did get some warnings from QEMU along the lines of "X register doesnt exist" or something but the machine runs fine and geekbench runs fine as well. Play with the cores/threads settings as well. If you go too high (for me was around 8), it doesn't boot up and just hangs.
I've been using VFIO and maintaining a guide for a few years, then I've realized that VFIO kinda works, but it's not a reliable technolog, and I switched to dual boot.
There are very significant pain points, specifically:
1. if one reserves the video card for VFIO, it won't have any power management; this means that it will run hot while doing nothing; in order to work this around:
1a. first one has to battle with X, which has an option not-to-take-over-a-card-but-it-takes-it-over-nonetheless
1b. then one can give exclusive access to the graphic card driver, which then can be switched out/in when starting/stopping the VM; this unfortunately works, but not reliably
2. the points before apply to nvidia; AMD is worse, as it hasn't supported soft GPU reset until very recently (I think it was added on 5.19 or so)
2a. this means that one starts the VM, then stops it, and most of the times the card will hang
2b. there resize BAR functionality is not supported by VFIO (at least, last year it wasn't), which meant, one had to lose performance by virtualizing it
The problem is that all the points below are not in control of the user; the problems happen at driver level (if there is no reset support, one can't add it out of thin air).
Point 1 has been what lead me to abandon VFIO. It's fantastic, but finding that my card was running hot while doing nothing was really a showstopper; and the alternative of the card having a most-of-the-time-malfunctiong driver was not appealing, either.
Big shame! I loved VFIO :)
* https://github.com/64kramsystem/vga-passthrough
There's https://github.com/zsh-users/zsh-syntax-highlighting which does some parsing, but I never looked at the details of it (I just know it exists).