Using accelorator tcg is very inefficient. But using hvf can cause bugs.
hvf is hyper visor technology built into mac. You can install it and if you can get qemu to boot with hvf instead. It is supposedly supposed to run much faster.
- (Official Github Repo) https://github.com/qemu/qemu
- (Other Useful Resource) https://github.com/macbian-admin/macos-subsystem-for-linux
A simple guide for running Ubuntu (or other Linux distributions) on macOS using QEMU.
brew update
brew install qemuCreate and navigate into a folder (e.g., ~/ubuntu):
mkdir ~/ubuntu
cd ~/ubuntuInside ~/ubuntu/, run:
qemu-img create -f qcow2 msl.qcow2 40GThis creates a 40 GB disk named msl.qcow2.
To see which accelerators your system supports (e.g., hvf or tcg):
qemu-system-x86_64 -accel help- Intel Macs often support
hvf. - Apple Silicon or unsupported setups may need
tcg(software emulation).
Example command (adjust ISO file name and memory as needed):
qemu-system-x86_64 -accel tcg \
-m 4096 \
-hda msl.qcow2 \
-cdrom ubuntu-24.04.1-desktop-amd64.iso \
-boot d \
-smp 2 \
-net nic \
-net user,hostfwd=tcp::4022-:22Tip: Replace
-accel tcgwith-accel hvfifhvfis supported. Increase-mto allocate more memory (e.g.,8192for 8 GB) but leave enough RAM for macOS.
Proceed with the installer. If prompted:
- Root Password: Leave blank (allows
sudoaccess). - Username: Match your macOS username if desired.
- Installation Options: For a minimal setup, uncheck desktop environments and include the SSH server.
After installation completes, remove the -cdrom and switch -boot d to -boot c:
qemu-system-x86_64 -accel tcg \
-m 4096 \
-hda msl.qcow2 \
-boot c \
-smp 2 \
-net nic \
-net user,hostfwd=tcp::4022-:22This boots from the installed disk rather than the ISO.
View Created VMs
QEMU doesn’t manage VMs like VirtualBox. You manually track disk files:
ls *.qcow2Remove a VM
Delete the .qcow2 file:
rm msl.qcow2Create a New VM
Create another disk image (e.g., 20 GB):
qemu-img create -f qcow2 newvm.qcow2 20GStart an Existing VM
qemu-system-x86_64 -accel tcg \
-m 4096 \
-hda newvm.qcow2 \
-boot c \
-smp 2Stop a Running VM
- Shutdown from inside the guest, or
killall qemu-system-x86_64- Hardware Acceleration: Use
-accel hvfif on an Intel Mac with HVF support. - Increase CPU Cores:
-smp 4or more if available. - Optimize Disk I/O: Try virtio drivers:
-drive file=msl.qcow2,if=virtio
- Allocate Adequate Memory:
-m 8192(8 GB) or more, but leave enough for macOS.
- On Apple Silicon, x86_64 guests must often use
-accel tcg, making performance slower. Tools like UTM may perform better by using Apple’s Virtualization.framework under the hood. - Always keep your QEMU and macOS updated to ensure the latest hardware-acceleration support.
Happy Virtualizing!
QEMU does not have a centralized location to "store installations" like WSL or VirtualBox. Instead, QEMU stores everything in the disk image file(s) you create (e.g., .qcow2), which you specify in the command when starting a VM.
Here’s a breakdown of where files are stored:
- When you create a disk image with
qemu-img, it is stored wherever you specify. - Example: If you run:
The disk image (
qemu-img create -f qcow2 ~/ubuntu/msl.qcow2 40Gmsl.qcow2) is saved in the~/ubuntudirectory.
This file contains the entire OS installation, including all its data.
QEMU doesn’t store configurations or metadata globally. Instead,
all configurations (e.g., RAM, CPU, accelerators) are provided as command-line arguments each time you run the VM.
To persist settings:
- Save your QEMU command to a script for reuse.
- The OS installation ISO is usually stored where you downloaded it. QEMU doesn’t copy the ISO;
it only references the file during installation. - Example: If your ISO is in
~/ubuntu, QEMU will read it directly from there.
- Snapshots: If you take snapshots, these may be stored alongside the
.qcow2file. - Temporary Files: QEMU may store temporary files in
/tmpor similar system directories, but these are cleared after shutdown.
- OS and data: Stored in the
.qcow2disk file you specify. - ISOs: Stored where you download them (not moved by QEMU).
- Configurations: Provided via commands/scripts (no centralized config).
- Temporary files: Stored in system temp directories during runtime.
If you’d like to explore the contents of your .qcow2 files, you can use QEMU tools like qemu-img to manage them.