If you are thinking of installing macOS Mojave on Windows 10 with VirtualBox, the instructions in this link worked for me.

These are links to the VB and mac files:
VirtualBox executable 6.1.32 for Windows
VirtualBox Extension Pack
Mojave ISO file download (about 7GB)
Windows commands to set up VirtualBox

Suggested macOS VM settings: Disc (SSD) = 100GB. Memory = 16GB. CPU = 4. Be patient at Step 7 (9) when you install the macOS, it took a lot longer than the suggested 15-29 minutes. I don’t know exactly how long, as I left it running after 60 minutes, with the timer countdown still saying 14 minutes. It was all done when I came back next morning.

Good luck.

---

Going to try on Linux with VB instead of the instructions I didn't get it to work with with KVM.

If you are thinking of installing macOS Mojave on Windows 10 with VirtualBox, the instructions in this link worked for me.

These are links to the VB and mac files:
VirtualBox executable 6.1.32 for Windows
VirtualBox Extension Pack
Mojave ISO file download (about 7GB)
Windows commands to set up VirtualBox

Suggested macOS VM settings: Disc (SSD) = 100GB. Memory = 16GB. CPU = 4. Be patient at Step 7 (9) when you install the macOS, it took a lot longer than the suggested 15-29 minutes. I don’t know exactly how long, as I left it running after 60 minutes, with the timer countdown still saying 14 minutes. It was all done when I came back next morning.

Good luck.

Well, I did it. Quite the series of steps to go through. Mohave is now running in VirtualBox.

@wateroakley
I'm used to pretty good performance of Linux VMware guests on this PC (4 threads of an i7 7700HQ, 16 MB of RAM allocated to VM, 100 GB fixed HD space in VM). I'm noticing considerable mouse lag as I move the cursor around in the VM window. Are you noticing the same thing too? I did perform some of the MacOS tweaks for VM performance listed at https://github.com/sickcodes/osx-optimizer.

I see your CPU is listed as having a boinc benchmark FP score of 1 billion ops/sec. It might be good to get a better initial estimate of task time by running a manual benchmark in boinc.

At the end of the instructions for the VirtualBox VM, I see it links to similar instructions for VMWare. :-) I may give that a go as I'm very used to using that hypervisor, and it would allow me to run both Linux and Mac VMs at the same time (although that i7 doesn't have very many threads for doing that).

Thanks for posting links to the instructions!

Well, I did it. Quite the series of steps to go through. Mohave is now running in VirtualBox.

Congratulations!
.
@wateroakley
I'm used to pretty good performance of Linux VMware guests on this PC (4 threads of an i7 7700HQ, 16 MB of RAM allocated to VM, 100 GB fixed HD space in VM). I'm noticing considerable mouse lag as I move the cursor around in the VM window. Are you noticing the same thing too? I did perform some of the MacOS tweaks for VM performance listed at https://github.com/sickcodes/osx-optimizer.
The mouse does not lag on this macOS VM. Did you enable the guest additions, which provide better integration for mouse and keyboard ?

I see your CPU is listed as having a boinc benchmark FP score of 1 billion ops/sec. It might be good to get a better initial estimate of task time by running a manual benchmark in boinc.
The mac VM is running at 1.08 s/TS with four HADCM3s, about 4.6 days run time (calculated). I see that your mac VM task is about 15% faster, which is expected for an i7-7700 vs i7-3770.

At the end of the instructions for the VirtualBox VM, I see it links to similar instructions for VMWare. :-) I may give that a go as I'm very used to using that hypervisor, and it would allow me to run both Linux and Mac VMs at the same time (although that i7 doesn't have very many threads for doing that).
Let us know how you get on with the VMWare VM.

Thanks for posting links to the instructions!
You're welcome.

---

@wateroakley
I'm used to pretty good performance of Linux VMware guests on this PC (4 threads of an i7 7700HQ, 16 MB of RAM allocated to VM, 100 GB fixed HD space in VM). I'm noticing considerable mouse lag as I move the cursor around in the VM window. Are you noticing the same thing too? I did perform some of the MacOS tweaks for VM performance listed at https://github.com/sickcodes/osx-optimizer.
The mouse does not lag on this macOS VM. Did you enable the guest additions, which provide better integration for mouse and keyboard ?

Yep, I did that.

I see your CPU is listed as having a boinc benchmark FP score of 1 billion ops/sec. It might be good to get a better initial estimate of task time by running a manual benchmark in boinc.
The mac VM is running at 1.08 s/TS with four HADCM3s, about 4.6 days run time (calculated). I see that your mac VM task is about 15% faster, which is expected for an i7-7700 vs i7-3770.

I think my PC is only faster because I'm only running 1 task at a time as opposed to the 4 you appear to be running at the same time. I didn't mean that the benchmark thing would improve your PC's performance, or that it's only capable of such low FP performance that is represented by 1 billion ops/sec, I meant that boinc uses the benchmark to estimate how long the task will take in boinc manager tasks tab and getting a realistic benchmark gives a more reasonable estimate of time to completion (still too long though).

At the end of the instructions for the VirtualBox VM, I see it links to similar instructions for VMWare. :-) I may give that a go as I'm very used to using that hypervisor, and it would allow me to run both Linux and Mac VMs at the same time (although that i7 doesn't have very many threads for doing that).
Let us know how you get on with the VMWare VM.

Upon further review, I would have to load an old version of VMWare Workstation, then hope my current VMWare VMs still work. Also, according to the comments, the convoluted instructions may include files that no long work with Mohave. Still, I may give it a try after I complete this task in VirtualBox.

Nice! Glad to see the 32-bit MacOS love extended to Windows.

You don't need 4GB per CPU core, though. The current MacOS tasks only use a few hundred meg per task, tops. I only see ~150MB working set size per task running in my "Mojave on Linux" VMs. I'm running 4C/4GB VMs without any issues at all.

Those remaining tasks aren't long for the queue, for sure!

Nice! Glad to see the 32-bit MacOS love extended to Windows.

You don't need 4GB per CPU core, though. The current MacOS tasks only use a few hundred meg per task, tops. I only see ~150MB working set size per task running in my "Mojave on Linux" VMs. I'm running 4C/4GB VMs without any issues at all.

Those remaining tasks aren't long for the queue, for sure!

Well you are the one burning through them with your 4 Penryns. :-) There aren't really any others with "Macs" on the computer stats leader boards. Of course the hadcm3s is really under performing in the credits per compute time as it has always been.

I'm not burning through that many of them. No idea who is, or if they're just failing quickly with CPU-type errors on other Macs with newer OSes. I can't see that.

My AMD grid powered (solar net-metered) box can chew through a set of 8 every 2 days or so, the rest are taking longer, and my other boxes are solar powered, so only run during the day - they take a week or so to chew through four units, though the longer solar days here mean I can probably let them go to sleep later. I've debated running the office systems with the solar trailer overnight, it could handle it, but possibly not the air conditioning as well. I'm not responsible for the thousand units chewed up. I've only chewed 80-100 of them. I'd throw a bit more cloud compute at them, but it's just not worth it - the performance is poor and the cost is significant.

I do have this 12C/24T old Xeon I could throw at them, but I don't think they'd be very quick on it.

I'm not burning through that many of them. No idea who is, or if they're just failing quickly with CPU-type errors on other Macs with newer OSes. I can't see that.

Looking at the workunits for the four cm3s tasks I picked up, these users (computers) have crashed over 1,000 cm3s.

546: https://www.cpdn.org/results.php?hostid=1368852
362: https://www.cpdn.org/results.php?hostid=1492772
93: https://www.cpdn.org/results.php?hostid=1489800
87: https://www.cpdn.org/results.php?hostid=1368870

---

That makes sense. :/ I was afraid that was the case.

There's no way to blacklist hosts who are just endlessly erroring tasks?

I suppose those of us with working systems can try to queue up a bunch of work ahead of time and try to claim more of the WUs that way. I normally feel bad about doing that since I'm not sharing, but if the alternative is WUs getting not processed at all...

There's no way to blacklist hosts who are just endlessly erroring tasks?.

This is the THREAD to report misconfigured hosts. It relies on the mods and project team to blacklist them.

---

Nice! Glad to see the 32-bit MacOS love extended to Windows.
You don't need 4GB per CPU core, though. The current MacOS tasks only use a few hundred meg per task, tops. I only see ~150MB working set size per task running in my "Mojave on Linux" VMs. I'm running 4C/4GB VMs without any issues at all.

Thanks for the mac VM core/memory guide. I might even try the mac VM on a retired headless QuadCore with 8GB RAM.

---

Thanks for reporting those - I'm still learning my way around the project/forum. I've been running it for a while, but it's generally been the long running Linux tasks on machines I've got set up to do specifically that.

Quad core/8GB? It should be totally fine! Put it to work! I've got a M1 Mini laying around doing nothing, but I don't know of a good way to run it for these tasks, so it's just my other compute boxes VMing away... which will end in a week or two, unless they get those task-swallowers taken care of. WCG is down, CPDN is running out of WUs... my computers are going to be bored! And my office will be cold, I actually heat mostly on work units out here...

Got Mojave installed on Ryzen9 5900x Windows10 VirtualBox but tasks are erroring out with

<message>process got signal 4</message>

From what I found signal 4 means the code contains illegal instructions the CPU can't understand. Here's an example task https://www.cpdn.org/result.php?resultid=22194689. Has anyone seen this type of error before?

The KVM/QEMU scripts add a number of flags for CPU instruction extensions.

MY_OPTIONS="+ssse3,+sse4.2,+popcnt,+avx,+aes,+xsave,+xsaveopt,check"

I'm not sure how to add all those in VirtualBox. I'm running with KVM/QEMU on an AMD box, but that's over on the Linux side of things.

I'll try to find a way to see what CPU features the macOS says are supported/enabled. What CPU features are required for CPDN?

I'll try to find a way to see what CPU features the macOS says are supported/enabled. What CPU features are required for CPDN?

SSE2 is the base requirement, so any PC made after 2003 should have it.

It does say that SSE2 is available. I changed another setting that might make a difference but work fetch is on the 1 hour delay so I'll try it later tonight.

Your computer details say 5 processors. I've read elsewhere that Macs require processors to be in "powers of 2". Set it to 4 instead of 5 in VirtualBox and see if it makes any difference.

Unfortunately neither changing a VBox setting nor changing the number of CPUs to 4 worked.