> ## Documentation Index
> Fetch the complete documentation index at: https://docs.macstadium.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Set VM CPU and memory explicitly

> Set CPU and memory for Orka VMs in a VM config instead of relying on defaults. macOS 27 VMs need at least 4 vCPU to render web content.

If you don't set CPU or memory when you deploy a VM, Orka uses defaults: 3 vCPU, and memory from your cluster's configuration or calculated from the CPU count. The defaults let a VM boot. They aren't sized for your builds. Set CPU and memory yourself, ideally in a VM config, so every job gets the same resources and you change them in one place.

## Put the sizes in a VM config

```bash theme={null}
orka vm-config create <VM_CONFIGURATION_NAME> --image <IMAGE> --cpu <CPU_COUNT> --memory <MEMORY>
orka vm deploy <VM_NAME> --config <VM_CONFIGURATION_NAME>
```

`--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:

```bash theme={null}
orka vm deploy <VM_NAME> --image ghcr.io/macstadium/orka-images/golden-gate:latest --cpu 4 --memory 8
```

MacStadium has verified 4 vCPU with 8 GB of memory. Smaller memory sizes with 4 vCPU haven't been tested.

## 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?](https://docs.macstadium.com/orka/orka-overview/how-orka-manages-vms.md#where-does-a-vm-run-and-how-many-fit-on-a-node).

Check what a running VM actually got with `orka vm list -o wide`, which shows its CPU and memory.

## Related pages

* [Orka CLI VM config templates and deployment](https://docs.macstadium.com/orka/orka-cli-reference/vm-deployment-and-configuration.md)
* [How Orka manages VMs](https://docs.macstadium.com/orka/orka-overview/how-orka-manages-vms.md)
* [Orka compatibility matrix for macOS and hardware](https://docs.macstadium.com/orka/orka-overview/compatibility-matrix.md)


## Related topics

- [Orka known issues and fixes by version](https://docs.macstadium.com/orka/orka-upgrades-and-release-notes/known-issues-by-version.md)
- [Orka compatibility matrix for macOS and hardware](https://docs.macstadium.com/orka/orka-overview/compatibility-matrix.md)
- [How Orka manages VMs](https://docs.macstadium.com/orka/orka-overview/how-orka-manages-vms.md)
- [Advanced configuration](https://docs.macstadium.com/remote-desktop-vdi/configuration/advanced-configuration.md)
- [Orka Engine standalone macOS VM management](https://docs.macstadium.com/orka/orka-engine/orka-engine-30.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.