Security lab

Kali Linux on VMware Fusion, on a M4 MacBook

Apple Silicon killed the easy path: no x86 guests, and no prebuilt VMware image. The ARM64 installer ISO plus a free Fusion Pro still gets you a proper Kali lab on an M4 Mac — here's the route that works, and the M4 gotcha to watch for.

2 Nov 2026

Setting up a Kali lab used to be a ten-minute job: download the prebuilt VMware image, open it, log in as kali/kali, done. On an Apple Silicon Mac, that job no longer exists. Fusion on Apple Silicon runs ARM64 guests only — it does not emulate x86 — and Kali's prebuilt VMware images are amd64. Download one of those and Fusion will simply refuse it. The working route is the installer ISO, built by hand. It takes a little longer, and you end up with a cleaner VM for it.

1. The one rule: ARM64, nothing else

Go to kali.org/get-kali, open the Installer Images, and download the Apple Silicon (ARM64) installer ISO — not the amd64 installer, not any prebuilt VM image. Before you run it, verify it: Kali publishes a GPG-signed SHA256SUMS file next to the download, and checking the hash costs a minute. A security distribution is exactly the download you don't take on trust, and Kali's own docs warn against copies hosted anywhere unofficial.

Laptop downloading an install disc, verified checkmark, ARM chip, old grey box

2. Fusion Pro is free now

VMware Fusion Pro has been free for personal use since version 13.5.2, and the current 13.6.x releases carry that same deal. The catch is only administrative: you download it from Broadcom's Support Portal, which wants a free account, and at install time you pick the Personal Use option instead of entering a license key. Snapshots, cloning, and virtual networking are all included in the free Pro — snapshots matter here, as we'll get to.

A virtual machine window with a Linux desktop, snapshot camera above, gift box for free

3. Build the VM

In Fusion: File → New, drag the ARM64 ISO onto the window, and when it asks for the guest OS, pick a Debian 12 ARM64 guest — Kali is Debian-based, and that's the profile Fusion wants. Give it room to breathe: I run mine with 4 GB of RAM and a 40 GB disk rather than the 20 GB default. A Kali install with a real toolset grows, and resizing a virtual disk later is a chore you don't need. Leave networking on NAT for now — the guest gets out to the internet for updates, but it isn't sitting directly on your home network while you're still setting it up.

A VM build window with memory and disk sliders, install disc going in, network cable

4. The M4 gotcha

One honest warning, specific to M4 machines: at least one M4 guide reports that Fusion's new-VM wizard stumbles on M4 where it worked fine on M1–M3, mis-detecting the ISO or the guest type. If the wizard gives you trouble, don't fight it — create the VM manually and check the resulting .vmx file has guestOS = "arm-debian12-64". That single line is what tells Fusion it's an ARM Debian guest, and getting it wrong is the usual cause of a VM that refuses to boot the installer. If the wizard works first time, skip this section entirely.

A setup wizard window with a warning, and the config file with one line highlighted

5. Install it

Boot the VM and take the Graphical Install. The installer is Debian's, so it will feel familiar if you've ever installed Debian: language, location, keyboard, network, then a user account you create yourself — note that the famous kali/kali login belongs to the prebuilt images, not to this path, so pick a real password. For the desktop, Xfce is the sensible lab choice: light, fast in a VM, and it stays out of the tools' way. Guided partitioning with everything in one partition is fine for a lab VM; this isn't a machine you're dual-booting.

A virtual machine window showing an installation progress bar, install disc beside it

6. First boot: tools, updates, snapshot

Three things, in this order. First, update it: sudo apt update && sudo apt full-upgrade. Second, install the guest tools — sudo apt install open-vm-tools-desktop — then reboot. That's what gives you clipboard sharing, drag-and-drop, shared folders, and a desktop that resizes with the Fusion window. Third, and most important: take a snapshot of the clean, updated VM before you install anything else or run any tool against anything. A lab VM's whole job is to be broken and restored, and a snapshot turns "I broke it" into a two-minute rollback instead of a reinstall.

A virtual machine with update arrows, a snapshot camera, shared folder and clipboard

7. Know the limits before you plan around them

Two things this VM will not do, so don't discover them mid-experiment. First, the Mac's built-in Wi-Fi shows up in the guest as a wired connection — Fusion doesn't pass a real wireless adapter through. If your plan needs actual wireless testing, that's a USB adapter conversation, not a Fusion setting. Second, some older security tools only ship x86 builds; on an ARM64 guest those either don't run or need rebuilding. Check the tools you actually plan to use before assuming the whole Kali catalogue is available.

A laptop plugged into a cable, faded wireless symbol above, old grey chip set aside

And the standing rule for any lab, VM or not: point the tools only at systems you own or are authorized to test. The VM makes it easy to spin up a target range; it doesn't change whose permission you need.

That's the whole route: ARM64 ISO, verified, into a free Fusion Pro, with a snapshot taken while it's still clean. About half an hour, most of it waiting for the installer — and you end up with a Kali lab that survives your experiments, which is the entire point.