First, the guide reminds you to make sure your Proxmox host has ample free disk space and enough RAM so the VM won’t fail during creation. Then it walks through logging into the web GUI, picking a node, launching the Create VM wizard where you give the machine a sensible name, select an ISO image, choose a qcow2 or raw disk format, set size and storage pool, allocate CPU cores and memory, enable ballooning if desired, and attach a virtio NIC to the proper bridge. After reviewing the summary you click Finish, start the new VM from the list, open its console via VNC or SPICE, run the OS installer, and when it’s up you can snapshot the machine or convert it into a template for future use. The final section lists quick fixes for typical problems like ISO boot failures, ballooning performance hits, and ZFS quota overruns, so you’re never left guessing why a VM might hang.

How to Create a New Virtual Machine on Proxmox

If you’re looking to spin up a fresh VM with Proxmox, this guide will get you from “What’s the first click?” to “I’m ready to install an OS” in less than ten minutes.

1. Make Sure Your Host is Ready

• Check for enough free disk: Proxmox likes to keep plenty of free space on the storage pool that will hold your VM images. If you’re using a ZFS pool, make sure it’s not over‑committed.
• Verify CPU and RAM availability: Even if your server has 64 GB of memory, you don’t want to assign more than you actually have, or your host could start swapping and kill performance.

Because Proxmox will silently allocate what you tell it. If the pool is full or the node runs out of RAM, the VM won’t even boot. I’ve seen this happen after a bad driver update left my node in a half‑hung state; the new VM would just hang on “Creating disk image”.

2. Log Into the Web GUI and Pick Your Node

1. Open https://<your-proxmox-ip>:8006.

2. Enter your credentials (root or a user with VM creation rights).

3. On the left pane, click the node name you want to host the VM.

Proxmox can run on multiple nodes; picking one determines where all resources come from and where the VM will live when you start it.

3. Start the “Create VM” Wizard

• Click Create VM in the top‑right corner.
• Give it a name that makes sense, like web‑server or k8s‑node.

Naming is more important than you think – I’ve seen people create dozens of VMs with identical names and end up editing the wrong one.

4. Choose Your ISO Image

1. In the OS tab, select “Use CD/DVD disc image file (iso)” and click Select.

2. Pick an ISO from your storage pool; if you haven’t uploaded one yet, do that first via Datacenter => Storage => ISO Images.

The wizard needs a bootable image to install the OS. Skipping this step leaves you with an empty VM that won’t do anything useful.

5. Set Up Disk and Storage

• Disk type: Use qcow2 for flexibility or raw for performance.

I’ve seen people get frustrated when a disk suddenly stops resizing; qcow2 keeps those options open.

• Size: Allocate more than you think you need – future updates can be brutal on space.
• Storage pool: Pick the same storage as your ISO if you want everything local and fast.

Proxmox will create the virtual disk image here. If you pick a shared networked pool that’s heavily used, the VM might suffer I/O lag.

6. Allocate CPU & Memory

• Cores: Start with at least one core per logical CPU you plan to give it.
• Memory: Assign enough for the OS and your workloads; remember that hyper‑threading doesn’t double real cores, so be conservative.
• Ballooning: Turn on the balloon device if you want the host to reclaim RAM when the VM isn’t busy.

I’ve used ballooning to keep a dozen small VMs running on a single node without overcommitting.

7. Network Settings

1. Choose virtio for best performance unless your OS only supports e1000.

2. If you need bridged networking, make sure the bridge (e.g., vmbr0) is already created and configured.

A mis‑configured network will leave your VM isolated. I’ve seen folks try to SSH into a machine that could never be reached because they forgot to attach it to the right bridge.

8. Review and Finish

• The wizard will show a summary; double‑check everything.
• Click Finish – Proxmox now builds the VM, mounts the ISO, and gets it ready for boot.

9. Start the VM and Install the OS

1. Select your new VM from the list on the left.

2. Hit Start in the toolbar.

3. Open the console (via Console => VNC or SPICE) to interact with the installer.

The console is your window into the freshly minted machine. I’ve had users think it was “stuck” when, in fact, they were just waiting for the installation screen to appear over VNC.

10. Snapshots and Templates (Optional but Useful)

• Once the OS is up and running, you can take a snapshot: Snapshots => Take Snapshot.
• If you plan on creating many similar VMs, convert this one into a template: More => Convert to Template.

Templates save time and keep your configuration consistent across dozens of nodes.

11. Common Pitfalls and Quick Fixes

• “VM cannot boot from ISO” – double‑check the storage path and that the ISO is readable by the node.
• “Memory ballooning kills performance” – disable ballooning if you’re running memory‑intensive workloads.
• “Disk quota exceeded” – if you used a ZFS pool with compression, it can shrink when data changes; monitor space usage with zfs list.

And that’s it. You’ve gone from zero to a working VM in Proxmox without chasing after obscure settings or waiting for someone on the forums to explain the wizard.