Well, I'm 90 minutes in, but it's unclear to me where jumpstart.sh and basic.sh come from. They're just used like they should be present, but from whence do they originate?
Certified Azure Solution Architect & DevOps expert with 20 years in software. Microsoft Press Author. CloudSkills Community Author. Also a bit of a data nerd.
The MacOS-Simple-KVM GitHub repo is linked from the original post. It is described as "set up a simple macOS VM in QEMU, accelerated by KVM
Has a link on the "MacOS-Simple-KVM" words taking you to a GitHub repo.
I then start talking about QEMU, move past that and you'll see this paragraph :-
The steps were followed as listed but with the following tweaks. First clone the git repo in, make sure to use the linux filesystem as it is faster at the moment on wsl2 than windows (/mnt).
This might be where there's some confusion. Once you clone the GitHub repo linked to off of "MacOS-Simple-KVM" using your wsl session you need to cd into it. The files you mention are in there.
I hope that is clearer, if so I'll update the post accordingly :)
Certified Azure Solution Architect & DevOps expert with 20 years in software. Microsoft Press Author. CloudSkills Community Author. Also a bit of a data nerd.
Certified Azure Solution Architect & DevOps expert with 20 years in software. Microsoft Press Author. CloudSkills Community Author. Also a bit of a data nerd.
I bought and installed the X server and got it as far as booting Clover and the original BaseImage.img, but it would hang a ways into the text boot at one of the meeting/rendezvous/sync points in startup. So close, but so far!
Appreciate the write-up! I may give it another shot on the AMD when it enters Beta... I've been waiting on AMD sub-virtualization just for WSL2 under HyperV for a while now!
I actually gave up on Clover and went with opencore with a different script
github.com/kholia/OSX-KVM
And THEN,
Using the config.plist that they provided ( and they admitted it needed work ) I spent a good hour getting it tweaked with: opencore.slowgeek.com/
After that it was a matter of selecting which virtual "CPU" I wanted and I think I selected Skylake-Client? mankier.com/7/qemu-cpu-models#Desc...
This list is to select what the cpu is that's being mimiced in the VM, and NOT what hardware model you have on your host machine.
Well, I'm 90 minutes in, but it's unclear to me where jumpstart.sh and basic.sh come from. They're just used like they should be present, but from whence do they originate?
Thanks for any help!
No problem! This bit of text from the post :-
The MacOS-Simple-KVM GitHub repo is linked from the original post. It is described as "set up a simple macOS VM in QEMU, accelerated by KVM
Has a link on the "MacOS-Simple-KVM" words taking you to a GitHub repo.
I then start talking about QEMU, move past that and you'll see this paragraph :-
The steps were followed as listed but with the following tweaks. First clone the git repo in, make sure to use the linux filesystem as it is faster at the moment on wsl2 than windows (/mnt).
This might be where there's some confusion. Once you clone the GitHub repo linked to off of "MacOS-Simple-KVM" using your wsl session you need to cd into it. The files you mention are in there.
I hope that is clearer, if so I'll update the post accordingly :)
Thanks! I did go back and spot it but appreciate the prompt followup!
I'm trying this on an i7-4770K before making the leap on the Ryzen 3970X!
Sounds like a plan :) glad you spotted it!
Found it! It's the KVM Repro mentioned about half way through...
How did you get on, did you get it up and running?
I bought and installed the X server and got it as far as booting Clover and the original BaseImage.img, but it would hang a ways into the text boot at one of the meeting/rendezvous/sync points in startup. So close, but so far!
Appreciate the write-up! I may give it another shot on the AMD when it enters Beta... I've been waiting on AMD sub-virtualization just for WSL2 under HyperV for a while now!
Did you ever get it past hang after clover?
It's 3am, and my eyes are getting blury.
And THEN,
Using the config.plist that they provided ( and they admitted it needed work ) I spent a good hour getting it tweaked with:
opencore.slowgeek.com/
After that it was a matter of selecting which virtual "CPU" I wanted and I think I selected Skylake-Client?
mankier.com/7/qemu-cpu-models#Desc...
This list is to select what the cpu is that's being mimiced in the VM, and NOT what hardware model you have on your host machine.
Not to brag, but it's freaking Blazing fast now.
wow awesome if u have a guid/gist please share