Put the sizes in a VM config
--memory is in GB. Point your CI integration at the VM config rather than repeating sizes in each pipeline. To change a size, deploy new VMs from an updated config: CPU and memory are fixed for the life of a VM.
Give macOS 27 VMs at least 4 vCPU
On macOS 27, a VM with 3 vCPU or fewer can show blank web content. Safari and Web Inspector draw their window and toolbar but no page content, and tests that render web views are affected the same way. The same VM with 4 or more vCPU renders normally. Adding memory doesn’t fix it. Since the default is 3 vCPU, a macOS 27 VM deployed without--cpu is affected. Set --cpu 4 or more for VMs from ghcr.io/macstadium/orka-images/golden-gate and images built from it:
Size for the node
Each node runs at most two macOS VMs, so a VM that asks for most of a node’s CPU or memory leaves less room for the second one. Size VMs so two fit on the nodes you deploy to, unless you want one VM per node. See Where does a VM run, and how many fit on a node?. Check what a running VM actually got withorka vm list -o wide, which shows its CPU and memory.

