What is com.apple.Virtualization.VirtualMachine on Mac, and why is it using so much CPU?

By Anil Gautam · Updated

com.apple.Virtualization.VirtualMachine is a virtual computer run by an app like Docker, OrbStack, UTM or Parallels.

Virtual machine · Review
com.apple.Virtualization.VirtualMachine at a glance
Shown in Activity Monitor ascom.apple.Virtualization.VirtualMachine
Runs from/System/Library/Frameworks/Virtualization.framework/
Made byApple, part of macOS (works for an app)
WhySlow's verdictReview

See what’s slowing your Mac right now: download WhySlow free. One-click fixes cost $10, once or yearly.

WhySlow explaining com.apple.Virtualization.VirtualMachine on a real Mac: verdict, CPU, memory and why it gets busy
Real screenshot: WhySlow explaining com.apple.Virtualization.VirtualMachine on a MacBook Pro.

Measured on a MacBook Pro (M4 Max, 128 GB) on 4 October 2026: A Docker virtual machine used 140 to 165% CPU and 7.95 GB of memory, the biggest single load on the Mac during these checks.

Why is com.apple.Virtualization.VirtualMachine using so much CPU?

Busy whenever the virtual machine is working. Quit the app that runs it when you don't need it.

What com.apple.Virtualization.VirtualMachine does

Docker Desktop, OrbStack, UTM, Parallels and similar apps can run Linux or macOS in a virtual machine using Apple's Virtualization framework. Activity Monitor shows that whole virtual computer as one process, so its CPU and memory figures include everything happening inside the VM. If your Mac struggles, give the VM less memory and fewer CPU cores in its app's settings.

Should you quit com.apple.Virtualization.VirtualMachine?

Maybe, but quit the app instead. com.apple.Virtualization.VirtualMachine is part of macOS, but it does its work for an app you opened. Close the page, window or app that started it rather than the process itself.

Is com.apple.Virtualization.VirtualMachine a virus?

The name com.apple.Virtualization.VirtualMachine alone can't prove a process is genuine, and this page isn't a security scan. Check where it runs from: the genuine one runs from /System/Library/Frameworks/Virtualization.framework/. In Activity Monitor, double-click com.apple.Virtualization.VirtualMachine and choose Open Files and Ports to see its location. If it appeared right after you installed something unexpected, don't grant it more permissions, and ask the software vendor or Apple Support.

How to check com.apple.Virtualization.VirtualMachine on your Mac

Open Activity Monitor (Applications › Utilities), choose the CPU tab and type com.apple.Virtualization.VirtualMachine in the search field. The % CPU column shows how busy it is: 100% means one full processor core. Watch it for a minute while you repeat the task that felt slow.

What to do if com.apple.Virtualization.VirtualMachine stays busy

How WhySlow helps with com.apple.Virtualization.VirtualMachine

See what's slowing your Mac right now

Free to explain. One-click fixes cost $10, once or yearly.

Download free

Sources

The process description comes from WhySlow’s app catalog. Diagnosis depends on your workload and the version of macOS or the app you use. For an unfamiliar process, start with Apple’s guide to inspecting processes and reading CPU activity.

Need a broader starting point? Follow the slow Mac checklist or learn about memory pressure.

Related processes