What is com.apple.Virtualization.VirtualMachine, and why does it use so much memory?
Last reviewed: 19 November 2026. Path, bundle ID and XPC service settings checked on macOS 26.3.1.
com.apple.Virtualization.VirtualMachine is the process that runs a virtual machine created with Apple's Virtualization framework, which apps such as Docker Desktop, UTM and Lima use to run Linux or macOS guests. Its memory is the guest's memory and its CPU is the guest's work, so a busy container or VM shows up here. To reduce it, lower the memory and CPUs given to the VM in the app that created it, or stop the VM when you do not need it.
com.apple.Virtualization.VirtualMachine at a glance
| com.apple.Virtualization.VirtualMachine | |
|---|---|
| Made by | Apple (part of macOS, Virtualization framework) |
| Type | XPC service (one virtual machine) |
| Location | /System/Library/Frameworks/Virtualization.framework/Versions/A/XPCServices/com.apple.Virtualization.VirtualMachine.xpc/Contents/MacOS/com.apple.Virtualization.VirtualMachine |
| Runs as | your user |
| Bundle ID | com.apple.Virtualization.VirtualMachine |
| Can you quit it? | Force quitting it is like pulling the power on that virtual machine. Shut the guest down from inside it or from the app that started it. |
What is com.apple.Virtualization.VirtualMachine?
Apple's Virtualization framework provides APIs for creating and managing virtual machines on Apple silicon and Intel Macs, to boot macOS or Linux guests. The framework runs each VM in an XPC service inside Virtualization.framework; the service is marked to allow multiple instances, so you can see one process per running VM.
The process belongs to whichever app started the VM. Docker Desktop's settings mention the Apple Virtualization framework as a virtual machine manager option, UTM offers an Apple Virtualization backend, and Lima uses its VZ mode by default on macOS 13.5 and later for new instances.
Is com.apple.Virtualization.VirtualMachine safe?
Yes. It is part of macOS, in /System/Library/Frameworks, signed by Apple, and runs only while an app has a virtual machine running.
Why does com.apple.Virtualization.VirtualMachine use so much memory, CPU, disk and network?
- Memory assigned to the VM. The guest uses the memory you configured for it. Docker Desktop's memory limit, for example, defaults to 50% of the Mac's memory.
- Work inside the guest. Builds, databases and services running in containers or the guest system count as this process's CPU on the Mac.
- Virtual disk activity. Reads and writes inside the guest go to its disk image file on your Mac, so heavy disk work in containers shows as disk activity here.
- Downloads in the guest. Pulling container images and package installs inside the VM pass through this process's virtual network device.
How much memory is normal for com.apple.Virtualization.VirtualMachine?
Memory close to what you assigned the VM, once the guest has been running a while, is normal. An idle Linux VM with no busy containers uses little CPU.
One process per running virtual machine is expected.
How do you reduce a virtual machine's memory and CPU?
- Find which app started it. Double-click the process in Activity Monitor to see its parent, or run
ps -o ppid= -p <PID>. Docker Desktop, UTM, Lima or another VM app will be the source. - Lower the VM's limits. In Docker Desktop, open Settings > Resources and lower the CPU limit and memory limit. In UTM or Lima, edit the VM's memory and CPU settings while it is stopped.
- Let idle VMs stop. Docker Desktop's Resource Saver turns off the Linux VM when Docker is idle and restarts it when containers run. Stop VMs in other apps when you are done.
- Stop busy containers or services. Use
docker statsor the guest's own tools to see which container or process inside the VM is using the CPU, and stop it.
When should you worry about com.apple.Virtualization.VirtualMachine?
Memory that grows well beyond the VM's configured size, or a VM process left running after you quit the app that created it, are reasons to check that app.
A process with this name outside the Virtualization framework path is not Apple's.
How do you check com.apple.Virtualization.VirtualMachine in Activity Monitor and Terminal?
Open Activity Monitor (Applications > Utilities), and type com.apple.Virtualization.VirtualMachine in the search field. The Memory tab shows its Memory. The CPU tab shows its % CPU. The Disk tab shows its Bytes Written and Bytes Read. The Network tab shows its Sent Bytes and Rcvd Bytes. Double-click the row for its parent process, memory details and open files.
In Terminal, the first command lists every com.apple.Virtualization.VirtualMachine process with its PID, user, CPU and memory (RSS is resident memory in kilobytes). fs_usage prints each file it reads or writes until you press Control-C; it needs an administrator password. nettop shows its live network traffic.
ps -axo pid,user,%cpu,%mem,rss,command | grep -F 'com.apple.Virtualization.VirtualMachine' | grep -v grep
sudo fs_usage -w -f filesys <PID> # PID from the ps line above
nettop -p <PID> # PID from the ps line above
How can Thrum help with com.apple.Virtualization.VirtualMachine?
Thrum's Memory tab shows memory pressure, swap, and the eight processes using the most memory, so you can see how much com.apple.Virtualization.VirtualMachine holds and whether the Mac is short of memory. An optional alert tells you when memory pressure turns critical. Click com.apple.Virtualization.VirtualMachine in the list for its PID, threads and memory, and Quit or Force Quit it after a confirmation.
Thrum is $4.99 once with a 14-day free trial and no account. It requires macOS 26 Tahoe on Apple silicon or Intel.
Questions about com.apple.Virtualization.VirtualMachine
Why does Activity Monitor show so much memory for this process?
It holds the virtual machine's RAM. The guest operating system uses that memory for its own apps and caches, so from the Mac it looks like one process with a large footprint.
Is com.apple.Virtualization.VirtualMachine the same as qemu?
No. It runs VMs through Apple's framework; QEMU is a separate emulator and virtualizer whose processes are named qemu-system-aarch64 or similar.