Search "install Kali Linux Proxmox" and you'll find a pile of forum threads, half of them arguing about display drivers and the other half arguing about whether you even need a full desktop install. If you're new to both Kali and Proxmox, that noise isn't helpful. This guide skips the debate and walks you through the part that actually matters: getting a working Kali Linux VM running on Proxmox VE, configured sensibly, with the handful of gotchas that trip up first-timers already handled.

Kali is a bit different from the Ubuntu or Debian VMs you might have built already. It's not a general-purpose server or desktop OS — it's a toolkit. That changes a few of the decisions you'll make along the way, from how much disk you give it to how you isolate its network. We'll cover all of that.

What You Will Learn

  • What Kali Linux actually is, and why people run it as a VM instead of on bare metal
  • How to download the right Kali image (there are more options than you'd expect)
  • How to configure a new Proxmox VM specifically for Kali
  • How to get through the Kali installer without losing your bootloader
  • The post-install steps that make the VM actually usable — guest agent, updates, display fixes
  • How to avoid the most common ways people trip over their own network setup on this one

What Is This Feature?

Kali Linux is a Debian-based Linux distribution built and maintained by Offensive Security, aimed squarely at penetration testing, digital forensics, and security research. Instead of the usual grab-bag of office software and media players, Kali ships with hundreds of security tools pre-installed — network scanners, password crackers, wireless auditing tools, exploit frameworks like Metasploit, and so on. You could install most of these tools individually on a regular Debian box, but Kali saves you the afternoon of dependency-chasing.

A Proxmox VM, if you haven't built one yet, is a full virtual computer running on your Proxmox host. It gets its own virtual disk, its own virtual network card, and its own slice of CPU and RAM, and Proxmox uses KVM (the Linux kernel's built-in virtualization system) to run it at close to native speed. From inside the VM, Kali has no idea it isn't running on a physical laptop.

Running Kali as a VM rather than installing it directly onto a laptop is the normal way most people use it today. It's disposable, snapshot-able, and doesn't demand a dedicated machine.

Why Would You Use It?

The honest answer: because you want to test something, and you don't want the mess of that testing sitting on your daily-driver machine.

A few concrete reasons people spin up Kali on Proxmox specifically:

  • Isolation. Security tools do things you don't want happening on your main network segment by accident — ARP spoofing, aggressive scans, rogue DHCP servers. A VM behind its own bridge or VLAN keeps that contained.
  • Snapshots. Before you run something destructive or experimental, you take a snapshot. If it breaks the VM, you roll back in seconds instead of reinstalling.
  • Disposability. Finish a course, a CTF, or an engagement, and you can just delete the VM. No leftover tool debris on a physical machine.
  • Resource flexibility. Give it 2 CPU cores and 4 GB of RAM for casual use, or scale it up temporarily for something that needs more horsepower, without touching hardware.

One thing worth saying plainly: only run these tools against systems you own or have explicit written permission to test. Scanning or attacking networks you don't control is illegal in most places, full stop, regardless of what OS you're running it from.

Prerequisites

Before you start, make sure you've got:

  • A working Proxmox VE install (this guide applies to 8.x and 9.x — the VM creation steps haven't changed meaningfully between them).
  • At least 20 GB of free storage for the VM's virtual disk, plus a few GB more for the ISO itself.
  • A minimum of 2 vCPU cores and 4 GB of RAM to assign — Kali's Xfce desktop runs fine on this, though 8 GB feels noticeably smoother if you can spare it.
  • The Kali Linux installer ISO downloaded from the official site at kali.org/get-kali — grab it from the "Bare Metal" installer images, not the pre-built virtual machine images, since we're installing from scratch.
  • Network access from your Proxmox host to upload the ISO (or a way to copy it in via SCP or the web UI).

A quick note on which image to grab: Kali's download page lists an "Installer" image (the full offline installer, several GB) and a "NetInstaller" (small, downloads packages during setup). For a first VM, the full Installer image is the less fiddly choice — it doesn't depend on your VM having working internet access partway through setup.

Step-by-Step Tutorial

1. Upload the Kali ISO to Proxmox

In the Proxmox web interface, click your storage (usually local) in the left-hand tree, open the ISO Images tab, and click Upload. Point it at the Kali ISO you downloaded. Depending on your connection, this takes anywhere from a couple of minutes to fifteen or so — Kali's installer image is usually in the 3–4 GB range.

2. Start the Create VM wizard

Click Create VM in the top-right corner. On the General tab, give it a name like kali-vm and leave the VM ID at the next available number unless you have a numbering scheme already.

3. OS tab

Select the ISO you just uploaded. For Guest OS Type, choose Linux, and for the version pick 6.x - 2.6 Kernel (or whatever the newest Linux option is in your Proxmox version). This just tells Proxmox which sane defaults to apply elsewhere — it doesn't restrict anything.

4. System tab

The defaults here are fine for most people: SeaBIOS for the BIOS type keeps things simple, since Kali doesn't need UEFI or Secure Boot for anything security-related. If you'd rather use OVMF (UEFI), that works too, but remember it needs an EFI disk added on the same tab — easy to forget, and the VM won't boot without it if you pick OVMF.

Tick Qemu Agent here. It won't do anything until you install the agent package inside the VM later, but enabling it now saves you a trip back to this screen.

5. Disks tab

Set the bus to VirtIO SCSI single — it's noticeably faster than the default IDE emulation and is well-supported by Kali's kernel out of the box. Give it at least 20 GB; Kali's tool set alone eats a few gigabytes, and you'll want headroom for wordlists, captured traffic, and whatever else you download during actual use. 40–60 GB is a more comfortable number if your storage allows it.

6. CPU and Memory tabs

Set CPU Type to host rather than the default kvm64. This passes your physical CPU's actual instruction set through to the VM, which matters for some cryptography and hashing tools that can use AES-NI or AVX acceleration. Give it 2 cores to start. For memory, 4096 MB is a working minimum; 8192 MB is more comfortable if the tool you're running (Burp Suite, a big Metasploit session, several browser tabs) tends to be memory-hungry.

7. Network tab

Use the VirtIO (paravirtualized) model for the network card. For the bridge, this is the one decision worth pausing on: if you're planning to do any kind of network scanning or attack simulation, don't just drop this VM onto the same bridge as your other VMs and your home network. Create a separate bridge (or VLAN) for it, or at minimum be aware that an aggressive scan will hit everything on that segment.

8. Confirm and start

Review the summary screen, click Finish, then start the VM and open its console.

9. Run through the Kali installer

You'll be dropped into Kali's Debian-based installer. It's a graphical installer by default (choose Graphical install at the boot menu rather than the text-mode option — it's easier to navigate on a first attempt). The flow is standard Debian:

  • Pick your language, location, and keyboard layout.
  • Set a hostname (anything works — kali is the usual default).
  • Create a regular user account. Kali has used a non-root default user since the 2020.1 release, so you'll sudo for anything privileged rather than logging in as root directly.
  • Partition the disk. For a VM, "Guided - use entire disk" is the right call unless you specifically need custom partitioning. Don't overthink this part.
  • When asked about the software selection, the default Xfce desktop plus the standard Kali tool metapackage is the safe choice for a first install.
  • Install the GRUB bootloader when asked, and double-check it's installing to your virtual disk (usually shown as /dev/sda) and not anywhere else. This is the single step most likely to leave you with a VM that boots straight to a black screen if you get it wrong.

The whole install takes roughly 15–25 minutes depending on your storage speed, most of which is unattended package installation you can walk away from.

10. First boot and cleanup

Once it reboots into the login screen, log in with the user you created, open a terminal, and run the post-install commands covered next.

Commands Explained

A few commands you'll actually type during and after setup, and what each one is doing:

sudo apt update && sudo apt full-upgrade -y

Refreshes the package list and upgrades everything. Kali is a rolling release, meaning there's no fixed "Kali 2025.2" you stay on forever — packages update continuously. Use full-upgrade rather than plain upgrade here, because it's willing to remove or replace packages if that's what's needed to resolve a dependency change. Plain upgrade will sometimes silently refuse to install an update because it won't remove anything, which leaves you on stale, occasionally broken packages.

sudo apt install -y qemu-guest-agent
sudo systemctl enable --now qemu-guest-agent

Installs the QEMU Guest Agent and starts it immediately, plus enables it so it survives a reboot. Once this is running, Proxmox can see the VM's actual IP address in the summary panel, and it can request a clean shutdown instead of just cutting power to the VM when you click Shutdown.

ip a

Shows the VM's network interfaces and IP addresses. Useful right after first boot to confirm the VirtIO network card came up and got an address from DHCP.

Common Errors

A short list of the problems people actually hit, in roughly the order they show up:

  • "No bootable device" right after creating the VM. Almost always means the ISO wasn't attached correctly, or the boot order under Options > Boot Order doesn't have the CD-ROM drive checked and above the (still empty) hard disk.
  • Black screen after the GRUB menu, or the VM boots straight to a GRUB rescue prompt. This is the bootloader-installed-to-the-wrong-device problem from step 9. Reboot the install, and if it happens again, reinstall GRUB manually from a live session pointed at /dev/sda.
  • Xfce loads but the display is choppy, wrong resolution, or won't resize with the console window. The default Proxmox display adapter doesn't always play nicely with Kali's graphics stack. Switch the VM's Display setting (under Hardware) from the default to VirtIO-GPU, then reboot.
  • The Summary tab shows no IP address even though the VM is clearly online. The guest agent either isn't installed yet or isn't running. Go back and run the two commands from the Commands Explained section above.

Troubleshooting

If the VM won't boot at all, start by opening the console and reading the actual error rather than guessing. A GRUB error naming a specific device or partition tells you exactly where the bootloader thinks its files are versus where they actually are — that mismatch is what needs fixing, usually by reinstalling GRUB from a Kali live boot with grub-install /dev/sda followed by update-grub.

If networking seems broken inside the VM but the interface shows as up, check that the VM's bridge in Proxmox is actually attached to a physical NIC that has a path to your router or DHCP server — this is a common trap if you've set up a dedicated isolated bridge for this VM (which, as mentioned above, is a good idea) but forgot it needs its own path to the internet if you want updates to work.

For anything tool-specific — say, a wireless adapter not being detected for Wi-Fi auditing — remember you're in a VM, and most built-in laptop Wi-Fi cards can't be passed through cleanly to a guest. That's a USB passthrough problem, not a Kali problem, and it's a separate rabbit hole from basic VM setup.

Best Practices

A handful of habits worth building in from day one:

  • Take a snapshot right after the initial setup and updates are done, before you install or run anything else. That gives you a clean baseline to roll back to.
  • Keep this VM on its own bridge or VLAN, separate from anything else on your network you care about.
  • Run apt update && apt full-upgrade regularly — a stale Kali install with months-old tool versions is a common source of confusing "why isn't this working" moments.
  • Don't disable the non-root user setup Kali gives you by default. Working as root full-time is an old Kali habit from years ago that the project deliberately moved away from, and there's no good reason to go back to it.
  • Size the disk generously up front. Wordlists, packet captures, and downloaded tools add up fast, and resizing a VM disk later, while doable, is an extra step you can just avoid.

Frequently Asked Questions

Do I need a powerful Proxmox host to run Kali as a VM?

No. 2 vCPUs and 4 GB of RAM handles normal use fine. You'd only need more if you're running something CPU-heavy like large-scale password cracking.

Should I use the pre-built Kali VM image instead of installing from ISO?

You can — Kali does publish ready-made virtual machine images. But they're built for VMware/VirtualBox import formats, and converting them for Proxmox adds its own set of conversion steps. Installing from the ISO, as covered here, is more predictable for a first Proxmox VM.

Is it legal to run Kali Linux?

Yes, Kali itself is just a Linux distribution and is completely legal to install and run. What's not legal is using its tools against networks or systems you don't own or don't have explicit permission to test.

Can I passthrough a USB Wi-Fi adapter for wireless testing?

Yes, Proxmox supports USB passthrough for VMs, which is the usual way to give a Kali VM access to a Wi-Fi card capable of monitor mode. That's a separate configuration step from the VM setup covered in this guide.

Why does Kali ask me to create a regular user instead of setting a root password?

Since the 2020.1 release, Kali installs with a standard non-root user by default, matching normal Debian and Ubuntu behavior. You still have full root access via sudo; it's just no longer the default login.

Conclusion

Once it's up, a Kali VM on Proxmox is genuinely low-maintenance — snapshot it before anything risky, keep it updated, and keep it off the network segments you don't want scanned. The setup itself is maybe twenty minutes of actual hands-on time once the ISO is uploaded, and after that it behaves like any other VM on your node: something you can clone, snapshot, resize, or throw away without touching physical hardware at all.