How to Create an openSUSE VM in Proxmox VE (Step-by-Step Guide)

If you've been clicking through Proxmox's "Create VM" wizard trying to decide what to actually install, openSUSE is worth a second look. It's not as commonly covered as Ubuntu or Debian, but it's a solid, stable Linux distribution with a genuinely different philosophy: a rock-solid release cycle (Leap) built partly on SUSE Linux Enterprise, a rolling release (Tumbleweed) if you want the bleeding edge, and YaST — a system configuration tool that a lot of admins swear by once they've used it.

This guide walks you through building an openSUSE Leap 16.0 virtual machine on Proxmox VE from scratch: downloading the ISO, configuring the VM correctly the first time (so you're not fighting boot errors later), running through the installer, and getting the QEMU Guest Agent working so Proxmox can actually see what's going on inside the guest.

What You Will Learn

How to download and upload the openSUSE Leap 16.0 ISO to Proxmox VE
How to configure a new VM with settings that actually match openSUSE's requirements
How to get through the YaST installer without surprises
How to install and enable the QEMU Guest Agent so Proxmox reports the VM's IP address and can shut it down cleanly
What to do when the VM won't boot, the installer complains about disk space, or the network doesn't come up

What Is This Feature?

openSUSE is a Linux distribution maintained by the openSUSE Project, with backing from SUSE. It comes in two flavors that matter here. Leap is the fixed-release version — new major versions every year or two, long support windows, and a strong emphasis on not breaking things between updates. Tumbleweed is the rolling-release version, where you get new kernel and package versions constantly, tested by an automated QA pipeline before they ship.

For a Proxmox VM, Leap is almost always the better starting point. It behaves predictably, and you won't get a surprise kernel update that changes how your virtual NIC is detected right before you need the VM for something.

One thing that sets openSUSE apart from Ubuntu or Debian: it defaults to Btrfs as the root filesystem with automatic snapshots taken before and after package updates. Btrfs is a copy-on-write filesystem — if an update goes badly, you can boot into a previous snapshot from the GRUB menu and roll back, without touching Proxmox's own VM snapshot feature at all. It's a nice safety net that a lot of other distros don't give you out of the box.

Why Would You Use It?

A few reasons people actually reach for openSUSE in a homelab or test environment:

You want to learn YaST because you're working with SUSE Linux Enterprise Server professionally, and openSUSE is the closest free equivalent.
You want built-in Btrfs snapshots on the guest OS itself, as a second safety net alongside Proxmox backups.
You're testing software packaged specifically for openSUSE/SLES (RPM-based, using zypper instead of apt).
You just want a change from the usual Ubuntu/Debian homelab setup and Leap gives you a more "enterprise" feel without the enterprise price tag.

Honestly, if none of that applies to you and you just need a quick Linux box to run a container or two, Debian or Ubuntu will get you there with less to learn. But if you're already curious about openSUSE, running it as a VM is a low-risk way to try it.

Prerequisites

Before you start, make sure you have:

A working Proxmox VE 9.x host with a storage location for both ISO images and VM disks (local storage works fine for a single VM)
At least 40 GB of free space on the storage you'll use for the VM disk — openSUSE's own installer requirement, and Proxmox's wizard doesn't warn you if you go lower
At least 4 GB of RAM free on the host to spare for this VM (2 GB is openSUSE's stated minimum, but installation and desktop use are noticeably smoother with more)
A network bridge configured on the host, usually vmbr0, connected to your LAN
Access to the Proxmox web interface with permission to create VMs

Step-by-Step Tutorial

Step 1: Download the openSUSE Leap 16.0 ISO

Go to get.opensuse.org and grab the Leap 16.0 image for x86_64. You'll see two choices:

Offline (DVD) image — about 4.2 GiB. Contains the full package set, so the installer works even without internet access. This is the one to grab if you're not sure.
NET install image — about 712 MiB. Downloads packages during installation, so you need a working internet connection (and DHCP on the VM) partway through the install.

For a first attempt, use the offline DVD image. It removes one entire category of things that can go wrong.

Step 2: Upload the ISO to Proxmox

In the Proxmox web interface, click your storage (for example local) in the left-hand tree, open the ISO Images tab, and click Upload. Pick the ISO file you downloaded. Depending on your connection to the Proxmox host, a 4.2 GB upload can take anywhere from a couple of minutes to fifteen or twenty on a slower link — there's no shortcut here, it's just a file transfer.

Step 3: Start the New VM Wizard

Click Create VM in the top-right corner. Work through the tabs as follows.

General

Pick a VM ID (Proxmox suggests the next free one — leave it unless you have a numbering scheme), give it a name like opensuse-leap, and leave everything else default.

OS

Select the ISO you just uploaded. Under Type, choose Linux, and set the version to 6.x - 2.6 Kernel (this covers any modern kernel, including openSUSE Leap's). Setting this correctly matters more than it looks — it changes some low-level defaults, like using UTC for the hardware clock instead of local time.

System

This is where a few decisions actually matter:

Machine: leave it on q35. It's the modern chipset emulation with a real PCIe bus, and it's what you want if you ever plan to pass through a GPU or NIC to this VM later.
BIOS: SeaBIOS is fine for openSUSE. You only need OVMF (UEFI) if you specifically want Secure Boot inside the guest — Leap supports it, but it adds an EFI disk and extra steps that most homelab setups don't need.
SCSI Controller: VirtIO SCSI single. It's been the recommended default since Proxmox VE 7.3 and gives each disk its own IO thread, which is just better performance with no downside for a Linux guest.
Qemu Agent: check this box now. You'll still need to install the agent package inside the guest later, but ticking it here means Proxmox is ready for it from the start.

Disks

Set the disk size to at least 40 GB — openSUSE's installer explicitly wants "over 40 GB of free hard drive space," and the wizard's default of 32 GB will leave you short before you've installed anything extra. Keep the bus on VirtIO SCSI (it should already be set, matching your controller choice), and if your underlying storage supports thin provisioning (ZFS, LVM-thin, or similar), tick Discard so deleted blocks get reclaimed instead of the virtual disk quietly growing forever.

CPU

Leave Cores at 2 for a general-purpose VM. For Type, the Proxmox default of x86-64-v2-AES is worth keeping — openSUSE Leap 16.0 itself requires x86-64-v2 as a baseline, so the two line up nicely. If your Proxmox host's physical CPU is old enough to not support that (anything before roughly 2013's Haswell/Piledriver generation), switch to host instead.

Memory

4096 MB (4 GB) is a comfortable default. openSUSE will install and run in 2 GB, but you'll notice the difference in YaST responsiveness and package management with a bit more headroom.

Network

Bridge it to vmbr0, and leave the model on VirtIO (paravirtualized). It's the fastest option available and openSUSE Leap has the driver built into its installer kernel, so there's nothing extra to install for networking to work.

Finish the wizard, but don't start the VM from the confirmation screen just yet if you want to double check anything — you can also just hit Finish and start it from the VM's summary page.

Step 4: Boot the VM and Start the Installer

Select the VM, click Start, then open the Console tab. You should land in the openSUSE boot menu within a few seconds. Choose Installation (not "Rescue System" or "Boot from Hard Disk").

The installer will detect your language and keyboard layout first — confirm or change them, then move on.

Step 5: Walk Through YaST's Installation Steps

openSUSE's graphical installer is built on YaST, and it's more guided than most distro installers. You'll hit these screens in order:

License Agreement — accept it to continue.
Network Settings — with VirtIO networking and DHCP on your bridge, this should already show a valid IP. If it doesn't, see the Troubleshooting section below.
Registration — you can skip this; it's for registering against SUSE's update infrastructure, not required for openSUSE itself.
System Role — for a general server or test VM, pick Server (Text Mode) if you don't need a desktop, or Desktop with KDE Plasma/GNOME if you want a GUI. Text mode boots faster and uses less RAM, which is usually the right call for a VM you'll manage over SSH.
Suggested Partitioning — the installer proposes a Btrfs root with subvolumes and automatic snapshots, plus a swap partition. Unless you have a specific reason to change it, accept the suggestion. This is where that 40 GB minimum actually gets used.
Clock and Time Zone — set your time zone; the hardware clock setting should already be correct because you picked "Linux" in the OS tab back in Proxmox.
User Settings — create your local user account, and set a root password (or reuse the same password for both, if this is just a test box).
Installation Settings — a summary screen. Review it, then click Install to confirm.

The actual file copy and configuration typically takes somewhere between eight and fifteen minutes on the offline DVD image, depending on your storage speed. The VM reboots on its own when it's done — let it, and log in at the console or over SSH once it's back up.

Step 6: Install and Enable the QEMU Guest Agent

Ticking the "Qemu Agent" box in the System tab earlier told Proxmox to expect the agent — it doesn't install anything inside the guest. Log into your new openSUSE VM (console or SSH) and run:

sudo zypper refresh
sudo zypper install qemu-guest-agent
sudo systemctl enable --now qemu-guest-agent

Give it a few seconds, then check the VM's Summary tab in Proxmox. You should see an IP address show up under the guest's network info, confirming the agent is talking to the host.

Commands Explained

Command	What it does
`sudo zypper refresh`	Updates the local list of available packages from openSUSE's repositories. Equivalent to `apt update` on Debian/Ubuntu.
`sudo zypper install qemu-guest-agent`	Installs the QEMU Guest Agent package, which lets Proxmox query the guest for its IP address, trigger a clean shutdown, and freeze the filesystem for consistent snapshots.
`sudo systemctl enable --now qemu-guest-agent`	Enables the guest agent service to start on boot, and starts it immediately in the same command — no reboot required.
`qm set <vmid> --agent enabled=1`	The CLI equivalent of ticking the Qemu Agent checkbox in the System tab, run from the Proxmox host's shell instead of the web GUI.
`cat /etc/os-release`	Run inside the guest to confirm which openSUSE version actually installed — useful after any install where you want to double-check before relying on it.

Common Errors

"No bootable device" right after starting the VM usually means the ISO didn't attach the way you expected, or the VM tried the hard disk before the optical drive on a completely fresh install. Check the CD/DVD drive in the VM's Hardware tab — it should point at your uploaded ISO — and confirm boot order in the Options tab lists the CD-ROM ahead of the (still empty) disk.

Installer complains it doesn't have enough disk space, or the partitioning proposal looks cramped: this almost always traces back to leaving the Proxmox disk size at the wizard's 32 GB default. Shut the VM down, resize the disk from the Hardware tab (right-click the disk, Resize), then grow the partition inside the guest, or just delete the VM and recreate it with a 40+ GB disk from the start if you haven't installed anything important yet.

Network Settings screen shows no IP address during install: this points to the bridge not being connected properly, or DHCP not being available on that VLAN/network segment. Double check the VM's network device is attached to the right bridge (vmbr0, typically), and that your router or DHCP server is actually reachable from that bridge.

Troubleshooting

If the console shows a black screen after boot instead of the openSUSE login prompt, try switching the Display setting in the VM's Hardware tab from the default to Standard VGA or SPICE, then restart the VM. Some default virtual display types don't play well with every guest kernel's console driver right after installation.

If the Summary tab still won't show an IP address after installing the guest agent, confirm the service actually started: sudo systemctl status qemu-guest-agent. If it shows as inactive, check that you enabled the "Qemu Agent" checkbox in the VM's System settings — if you added it after installation, you'll need to fully stop and start the VM (a reboot from inside the guest isn't enough) for Proxmox to attach the virtual serial channel the agent uses.

If YaST's partitioner errors out or hangs when you accept the suggested Btrfs layout, it's occasionally a sign the virtual disk itself has an issue — check Datacenter → Storage to confirm the target storage still has free space, since a full storage pool causes strange partitioning failures that don't clearly say "disk full."

Best Practices

Give the VM disk real headroom — 50 to 60 GB rather than the bare 40 GB minimum, especially if you'll add a desktop environment or dev tools later.
Take a Proxmox snapshot right after the initial install and guest agent setup, before you start customizing anything. It's a five-second safety net if something later goes sideways.
Stick with VirtIO SCSI single and Discard if your storage backend supports it — there's no real reason to use SATA or IDE emulation for a Linux guest in 2026.
If you plan on cloning this VM to spin up several openSUSE instances, shut it down, remove machine-specific state (SSH host keys are the usual culprit people forget), and convert it to a template rather than repeatedly reinstalling from scratch.
Keep the offline DVD ISO around locally if you're going to build more than one openSUSE VM — it saves you from re-downloading it and skips any dependency on internet access during install.

Frequently Asked Questions

Should I use Leap or Tumbleweed for a Proxmox VM?

Leap, unless you specifically need the newest kernel or package versions. Tumbleweed updates constantly and occasionally needs manual intervention when something breaks — fine for a desktop you use daily, more friction for a VM you mostly leave alone.

Does openSUSE Leap 16.0 need UEFI/OVMF in Proxmox?

No. SeaBIOS boots it fine. You'd only reach for OVMF if you want Secure Boot enabled inside the guest specifically.

How much RAM does this VM actually need?

2 GB is the stated minimum and it will install and boot. 4 GB is a more realistic day-to-day amount if you're running anything beyond a bare server install.

Can I use the NET install ISO instead of the offline DVD?

Yes, and it's a smaller download, but it needs a working internet connection and DHCP partway through installation. If your network setup is anything other than straightforward, the offline DVD image avoids that dependency entirely.

Do I still need Proxmox VM snapshots if Btrfs already has its own?

Yes — they solve different problems. Btrfs snapshots protect you from a bad package update inside the guest. Proxmox snapshots capture the entire VM state (including RAM if you choose) and work even if the guest OS itself is unresponsive.

Conclusion

Once the VM settings match what openSUSE actually expects — enough disk space, VirtIO SCSI, a sane CPU type — the rest of the install is genuinely straightforward. YaST does most of the thinking for you, and the guest agent setup at the end is two commands and a service enable. If you've been running the same two or three distros in your homelab for years, openSUSE Leap is a low-effort way to try something with a different (and in some ways more polished) approach to system administration.

Vormox is an independent virtualization management platform built on Proxmox VE. Proxmox® and Proxmox VE® are trademarks of Proxmox Server Solutions GmbH. Vormox is not affiliated with, endorsed by, or sponsored by Proxmox.