Thrum

What is qemu-system-aarch64, and why is it using so much CPU?

Last reviewed: 19 November 2026. Behavior checked against QEMU, UTM and Lima documentation.

qemu-system-aarch64 is a QEMU process running a virtual 64-bit ARM machine, started by apps and tools such as UTM or Lima. Its CPU and memory are the guest system's, so work inside the VM shows up here, and it uses much more CPU when it has to emulate the processor in software instead of using the Mac's hypervisor. Giving the VM fewer cores and less memory, and stopping it when idle, keeps it in check.

qemu-system-aarch64 at a glance

qemu-system-aarch64
Made byThe QEMU project (open source), bundled by apps such as UTM
TypeVirtual machine and emulator process
Runs asyour user
Can you quit it?Force quitting it is like pulling the power on that virtual machine. Shut the guest down first.

What is qemu-system-aarch64?

QEMU's documentation describes system emulation as a virtual model of a machine, with CPU, memory and emulated devices, to run a guest operating system. On macOS it can use Apple's Hypervisor framework (the hvf accelerator) to run guests at near-native speed when the guest architecture matches the Mac, or its Tiny Code Generator (TCG), which is pure software emulation and is the default unless an accelerator is chosen.

The name tells you the guest architecture: qemu-system-aarch64 runs ARM64 guests, while qemu-system-x86_64 runs Intel guests, which on an Apple silicon Mac always means emulation. UTM is based on QEMU and uses it as its default backend, and Lima can use QEMU as its VM type.

Is qemu-system-aarch64 safe?

QEMU is open source and widely used. Check the path in the process's command line, which shows the app or tool folder it runs from, such as inside UTM.app.

Why does qemu-system-aarch64 use so much CPU, memory and disk?

How much CPU is normal for qemu-system-aarch64?

With hardware acceleration and an idle guest, CPU is low. Under emulation even an idle guest can keep a core busy.

Memory near the VM's configured size after it has been running a while is normal.

How do you make a QEMU virtual machine lighter?

  1. Find who started it. Run ps -o pid,ppid,args -p <PID>. The path shows the app or tool, and hvf or tcg among the arguments tells you whether it is using the hypervisor or emulating.
  2. Use virtualization, not emulation. On Apple silicon, use ARM64 guest systems so the hypervisor can be used. In Lima, the VZ VM type uses Apple's Virtualization framework instead of QEMU for new instances.
  3. Lower the VM's CPUs and memory. In UTM edit the VM's system settings while it is stopped; in Lima change the instance's CPU and memory settings.
  4. Stop VMs you are not using. Shut the guest down from inside, stop it in UTM, or run limactl stop for a Lima instance.

When should you worry about qemu-system-aarch64?

A qemu process you did not start and cannot link to UTM, Lima or another tool you use deserves a look at its path and parent.

Constant high CPU from an idle guest is a sign that it may be running under TCG emulation; check the arguments for hvf.

How do you check qemu-system-aarch64 in Activity Monitor and Terminal?

Open Activity Monitor (Applications > Utilities), and type qemu-system-aarch64 in the search field. The CPU tab shows its % CPU. The Memory tab shows its Memory. The Disk tab shows its Bytes Written and Bytes Read. Double-click the row for its parent process, memory details and open files.

In Terminal, the first command lists every qemu-system-aarch64 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.

ps -axo pid,user,%cpu,%mem,rss,command | grep -F 'qemu-system-aarch64' | grep -v grep
sudo fs_usage -w -f filesys <PID>    # PID from the ps line above

How can Thrum help with qemu-system-aarch64?

Thrum keeps a live CPU graph in the menu bar. One click shows the eight processes using the most CPU, so you can see when qemu-system-aarch64 is among them and how much it takes. An optional alert tells you when a process stays above a CPU level you choose (50 to 200% of one core) for 1 to 10 minutes. Click qemu-system-aarch64 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 qemu-system-aarch64

Why is qemu-system-aarch64 slow compared with Apple's Virtualization framework?

With the hvf accelerator QEMU also uses the Mac's hypervisor. The large difference comes when QEMU emulates the processor with TCG, which is its default when no accelerator is chosen.

Can QEMU run macOS on Apple silicon?

UTM's documentation says QEMU cannot run macOS virtualized on Apple silicon; its Apple Virtualization backend is the way to do that.

Sources