Both in a VM, with the same amount of cores/threads, and the same amount of RAM.
The funny thing is, macOS is on an external $30 SSD, in a qcow2 image file.
Windows is on an internal Samsung SSD, RAW, no image file.
Same video card too.
Would a MacBook Air be as fast? It has shitty integrated video. But you could use a external GPU.
No sound in the VM yet. Might be a pain to fix, I want to use the HDMI sound from the GPU.
Looks like reinstalling Clover, killed it. Clover won’t even boot. I’ll see if the Clover image will boot.
And copying the EFI from the Clover, didn’t fix it. Says something about dropping tail or something.
Ha, so macOS is faster on a mechanical drive then Windows. The old image was still being booted. That means, I have to redo everything, or better, just copy it to the SSD again, and copy EFI back to the old image.
The problem is most likely because there’s two memory fixes in the drivers folder, the old one, and it installed a new one.
And the copy gets slow once it says 100, don’t know if it’s the SSD or the other drive. The file is 60 GB.
Nope, looks like I need to copy Clover from the Clover image to it. After deleting the EFI folder.
Clover boots now, but macOS is taking a long ass time to boot. Not even to the Apple logo with the progress bar, just the garbled text.
To get rid of the garbled text, set the resolution to 1024×768 in config.plist. Somehow it finally booted. And I don’t think sleep works, it won’t wake up.
Do I need the DSDT patches? The ethernet is causing it to hang. Changed some stuff in config.plist to what this has. Now to copy the virtio-net-osx to a flash drive. Probably won’t work, it’s 5 years old.
Sleep might work now. Wasn’t sleeping long though. Going to try using vmxnet3 for the network. Thought I did shutdown in macOS, apparently not.
Maybe my router crapped itself.
Almost booted, booted to a black screen. Disabling reset HDA got it to boot.
That’s why a real Mac is nice, it just works.
Nope, virtio doesn’t work.