Proxmox VE: What Is It and How Do You Install It? VM and LXC Guide

What Is Proxmox VE?

Proxmox VE (Virtual Environment) is an open source virtualization platform that lets you run several virtual machines (KVM) and Linux containers (LXC) on one physical server. You manage everything from a web interface, and storage, networking, and backups live in the same panel.

It installs as a Debian-based Linux distribution. So you first install an operating system, and that system then hosts the others. This guide covers the concept, the install steps, and the first settings you should check.

Also, we wrote it for website owners, e-commerce teams, and developers. We are a digital marketing and web team, not a hosting company. So we base every technical point on the official Proxmox documentation and we say plainly where the limits are.

We also keep the terms simple. A "guest" is a virtual machine or container running inside the main system. The "host" is the physical server where Proxmox is installed.

What Problem Does Proxmox VE Solve, and Who Uses It?

Proxmox VE splits one machine into many independent virtual servers. So you keep test, staging, and production environments apart. Then if one breaks, the others keep running.

Here is an example. An e-commerce team wants to try a new payment plugin. First, before touching the live shop, they clone the setup into a virtual machine and test it there. Then, if something fails, they delete the copy and start again.

Typical users include:

• Developers who want a home or office test lab on their own hardware.
• Small companies that run a few internal services, such as file sharing or accounting software.
• Web teams that want to test changes before they go live.
• People who rent a dedicated server and want to run several projects on it.

On the other hand, a single WordPress site does not need Proxmox. Instead, a good hosting plan or a managed VPS is usually cheaper and simpler. We explain how to pick one in our guide on how to choose web hosting.

How Is Proxmox VE Different From Docker and a Regular VPS?

All three give you isolated environments, but at different layers. First, Proxmox VE divides a server into virtual machines. Second, Docker packages applications inside one operating system. Finally, a regular VPS is a ready-made virtual machine that a provider rents to you.

To learn Docker in depth, read what is Docker. We also compare the server types in VPS vs cloud server vs VDS.

In practice, these tools work together. Many teams create a Linux VM on Proxmox and install Docker inside it. So you get the strong isolation of a VM and the easy packaging of containers.

What Hardware Does Proxmox VE Need?

The official system requirements page lists two levels. The minimum is for evaluation only, while the recommended level is for real use.

• CPU: a 64-bit x86 processor with Intel VT or AMD-V. KVM full virtualization needs this support.
• Memory: at least 1 GB plus whatever the guests need as a minimum. The recommendation is at least 2 GB for the OS and Proxmox services, plus memory for the guests.
• Storage: fast and redundant storage. The documentation says SSDs give the best results.
• Network: one network card is enough to start, but multiple Gbit cards are recommended for production.

However, ZFS and Ceph need extra memory. The documentation suggests roughly 1 GB of RAM for every TB of used storage.

Let us turn that into a rough plan. Example calculation: four VMs with 4 GB each need 16 GB, and Proxmox itself needs at least 2 GB more. That makes 18 GB at minimum, and a little headroom is wise.

How Do You Check Whether Your CPU Supports Virtualization?

First, on Linux, you look at the CPU flags. Intel processors show the vmx flag, and AMD processors show svm. Even when the flag shows up, virtualization must also be switched on in the BIOS or UEFI settings.

grep -E -c '(vmx|svm)' /proc/cpuinfo

If the output is 0, the flag is missing or disabled. Any number above zero means the hardware is suitable.

Be careful if you plan to install Proxmox inside a VPS. That needs nested virtualization, and your provider must allow it. So ask them before you buy.

How Should You Plan Disks and RAID Before Installing Proxmox VE?

Changing the disk layout later is painful, so decide before you install. The Proxmox documentation suggests two paths: a hardware RAID card with a battery-backed write cache (BBU), or no RAID card with ZFS.

Do not mix hardware RAID and ZFS on the same disks, because ZFS wants to see the disks directly. We explain RAID levels in what is RAID.

Disk speed matters too, because many VMs share the same disks. For measuring it, see our guide on IOPS and NVMe SSDs.

Also, do not trust a single disk. If it fails, every VM on it is gone. A redundant layout plus a separate backup target cuts that risk a lot.

What Should You Prepare Before the Installation?

A few preparations make the install go smoothly. Specifically, The first one is critical, because the installer uses the whole target server by default and removes existing data.

1. Back up any data on the target disks.
2. Download the ISO only from the official Proxmox download page, and verify it against the published checksum.
3. Write the ISO to a USB stick using the method in the official documentation.
4. Enable virtualization support in the BIOS or UEFI.
5. Note the static IP address, gateway, and DNS server you plan to give the machine.

To verify the checksum, run sha256sum on the downloaded file and compare the output with the official page.

Also think about how you will reach the server. For example, in a remote data center, you need screen and keyboard access during setup. Also, many providers offer a remote console for this. If yours does not, installing from an ISO is hard, so ask first.

What Are the Proxmox VE Installation Steps?

The installer is a graphical wizard, and the official installation guide walks through these steps:

1. Boot the server from the USB stick and choose the Proxmox VE installer.
2. Accept the license agreement.
3. Pick the target disk. The Options button lets you change the filesystem.
4. Enter your country, time zone, and keyboard layout.
5. Set the administrator password and a notification email address.
6. Configure the management network interface, IP address, gateway, and DNS.
7. Review the summary, start the install, and reboot when it finishes.

The password must have at least 8 characters. The documentation recommends 12 or more, mixing upper case, lower case, numbers, and symbols.

However, take care in the network step. According to the guide, the installer asks for either an IPv4 or an IPv6 address, not both. So dual stack needs extra setup after installation. For background, see what is IPv6.

Because of a wrong IP, you cannot reach the web interface. You would then have to fix the network from the server console. So double-check the values before you confirm.

Which Filesystem Should You Choose During Installation?

The installer offers four options. Then the default is ext4 with LVM. Changing it later often means reinstalling, so think about it up front.

So ext4 is enough for most beginners. If you have several disks and plenty of RAM, look at ZFS.

The appeal of ZFS is disk redundancy without buying a RAID card. However, the price is memory use. On a small machine, ZFS leaves less RAM for your VMs, so choose by your hardware, not by trend.

How Do You Log In to the Proxmox VE Web Interface?

When the install finishes, open a browser and go to the IP address you set, on port 8006. For example, the address looks like https://192.0.2.10:8006. The username is root and the realm is PAM. Also, you chose the password during setup.

On first login the browser shows a certificate warning, because Proxmox uses a self-signed certificate by default. If you have a domain name, you can set up a valid certificate. To understand how certificates work, read what is an SSL certificate.

Do not click through the warning forever. Fix the certificate once, because otherwise you cannot tell a real attack from the usual warning. You can check addresses and DNS records with our DNS lookup tool.

Why Does Proxmox VE Show a Subscription Notice and Repository Errors?

After you log in, you see a notice saying there is no valid subscription. This is not a fault, because Proxmox enables the enterprise repository by default, and that repository needs a paid subscription. Without one, it gives errors during updates.

The package repositories documentation describes three repositories:

• Enterprise: the most stable packages, recommended for production, and it needs a subscription.
• No-subscription: free, suitable for testing and non-production use. The documentation warns that these packages are not always as heavily tested, and it does not recommend them for production.
• Test: only for trying new features and bug fixes.

In the interface, open the node, then Updates, then Repositories to switch them. For example, for a lab, no-subscription is fine. However, for an environment with customer data, seriously consider a subscription.

Check prices only on the official Proxmox site, since they can change. The question to ask is simple: can this server tolerate downtime?

How Do You Run the First Update After Installing?

First, once the repository is set, update the packages. In the interface, the Refresh and Upgrade buttons under Updates do this. You can also use the shell.

apt update
apt dist-upgrade

If a kernel update arrives, reboot the server afterwards. Also, if you already have running VMs, plan a maintenance window.

Clock accuracy matters too, because logs and certificates break when the time is wrong. Verify it as described in time sync with NTP.

Update right after the first install, since packages on the ISO age quickly. Then set a regular schedule. A monthly maintenance window, for example, reduces unplanned outages.

How Do You Create a Virtual Machine in Proxmox VE?

First, upload the ISO file. Select the local storage in the interface, open ISO Images, and upload the file. Then click Create VM at the top right to open the wizard. The QEMU/KVM documentation describes each step.

1. General: the VM ID and name.
2. OS: the ISO file and the guest OS type. The right type lets Proxmox tune some low-level settings.
3. System: the display type, SCSI controller, QEMU Agent checkbox, firmware (SeaBIOS or OVMF), and machine type (440FX or Q35).
4. Disks: the disk size and storage.
5. CPU and Memory: the number of cores and the amount of RAM.
6. Network: the network card model and bridge.

When the wizard ends, start the VM and install the OS from the console. On the command line, qm list shows your VMs, and qm start 100 starts VM number 100.

Start small with your first VM. One core, 2 GB of RAM, and a 20 GB disk are enough for a Linux test. You can add resources later, so you do not block host memory for nothing.

Why Do VirtIO and the QEMU Guest Agent Matter?

The documentation strongly recommends the VirtIO SCSI or VirtIO Block controller, for performance and because they are better maintained. The same goes for networking. According to the docs, a VirtIO network interface can deliver up to three times the throughput of an emulated Intel E1000.

Linux guests usually include VirtIO drivers already. Windows guests, however, need the drivers installed separately. If the installer cannot see the disk, this is often the reason.

The QEMU Guest Agent is a small service inside the guest. Through it, the host can talk to the guest, for example to shut it down cleanly or to freeze the filesystem during a backup.

So if you install Windows, remember to attach the VirtIO driver ISO too. Then install the agent in the guest and enable it in the VM options. Doing both makes backups and shutdowns more reliable.

How Do You Create an LXC Container?

An LXC container uses the kernel of the host and does not emulate a full operating system. According to the container documentation, the runtime cost is usually negligible. On the other hand, you can only run Linux distributions. Windows and FreeBSD do not work.

First, update and download the templates. Then create the container from a template:

pveam update
pveam available
pveam download local TEMPLATE_NAME
pct create 200 local:vztmpl/TEMPLATE_NAME --hostname example --memory 512 --net0 name=eth0,bridge=vmbr0,ip=dhcp --storage local-lvm --unprivileged 1
pct start 200
pct enter 200

Replace TEMPLATE_NAME with the real file name from the pveam available output. Confirm the option names against the official documentation for your version.

Mapping the container to an ordinary user matters for security. The documentation says unprivileged containers are the default and safe by design. It tells you to use privileged containers only in trusted environments, so stay unprivileged unless you have a reason.

Should You Choose a VM or an LXC Container?

The short rule: pick a VM if you want full isolation or a non-Linux system, and pick LXC if you want a light setup. The documentation also advises running application containers such as Docker inside a Proxmox VM, not inside LXC.

We do not cover the inner workings of KVM here. We handle that in a sibling article.

Ask one question: does this workload need its own kernel? If yes, choose a VM. For a light Linux service, such as a small web server or a database, LXC is far more economical.

What Do the local and local-lvm Storages Do in Proxmox VE?

A standard installation creates two storages automatically. Knowing them helps you see where files go. According to the Proxmox storage documentation, this is how they work:

• local: a directory storage that points to /var/lib/vz. It holds ISO files, container templates, and backups.
• local-lvm: an lvmthin pool on LVM installs. It holds VM disks and container root filesystems.

So you upload the ISO to local, and you create the VM disk on local-lvm. The content types are images (VM disks), rootdir (containers), vztmpl (templates), backup, iso, and snippets.

If you picked ZFS, the storage names may differ. Check the real state under Datacenter, then Storage, in the interface.

To expand storage, add a new one from the same screen, for example a second disk or an NFS share. A separate storage for backups also lowers the risk of a full disk.

What Do You Usually Get Wrong After a New Proxmox VE Install?

Beginners tend to hit the same few problems. Most can be avoided with preparation. This list shows the common ones and the first thing to check.

• Cannot reach the web interface? Check the IP, the gateway, and port 8006.
• A VM that will not start usually means virtualization is off in the BIOS.
• When updates fail, check the enterprise repository and the subscription.
• No disk in Windows setup? Load the VirtIO driver.
• If the disk is full, clear old backups and unused ISO files.

Also make it a habit to back up before every change. A mistake with a way back is just a lesson.

How Does Backup (vzdump) Work in Proxmox VE?

vzdump is the built-in backup tool of Proxmox. According to the backup documentation, backups are always full backups. That means they contain the VM or container configuration and all the data.

There are three modes:

• Stop: shuts the VM down cleanly. It gives the best consistency but causes a short downtime.
• Suspend: pauses the VM briefly, so the downtime is small.
• Snapshot: backs up while the system runs. The documentation describes it as the lowest-downtime mode, with a small risk of inconsistency.

vzdump 100 --compress zstd --mode snapshot --storage local

For regular backups, define a scheduled job in the interface under Datacenter, then Backup. To restore, use qmrestore for VMs and pct restore for containers.

Also set a retention rule. Otherwise backups pile up and fill the storage. Keeping the last seven daily and four weekly copies is a reasonable start for many small setups. That value is only an example, so adjust it to your needs.

Is Your Backup Safe if It Sits on the Same Server?

No, it is not. If the backup and the original data live on the same disk or machine, a disk failure takes both. The documentation also shows that backups are local archives by default, and an off-host copy needs separate storage.

Proxmox recommends its own product, Proxmox Backup Server, for backups. It stores backups as deduplicated chunks. You can also use file-level storage such as NFS.

The rule is simple: keep copies in different places, and test restores regularly. For the whole strategy, read our website backup strategy guide.

For systems with databases, make sure the backup is consistent. If needed, take a separate application-level dump. Our guide to mysqldump and pg_dump shows how.

How Do You Secure a Proxmox VE Server?

The management interface gives full control of the server. For that reason, we recommend you do not open port 8006 directly to the internet. Limit access with a VPN or an IP restriction.

• Use a strong, unique root password.
• Apply updates on a regular schedule.
• Use SSH keys instead of passwords.
• Limit brute-force attempts with Fail2ban.
• Give each guest system its own firewall and update routine.

Also look at the built-in firewall and two-factor authentication in the interface. See the official documentation for the details.

For the wider picture of web vulnerabilities, our OWASP Top 10 guide helps. Finally, watch the access logs. An unexpected login attempt can be a sign of an attack.

When Does Proxmox VE Make Sense, and When Not?

It makes sense when you have a strong server that is idle or rented, you want several independent environments, and you have time to learn the management. Test and staging setups also suit it very well.

It does not make sense in these cases:

• You have a single business site and no technical skills.
• Nobody can step in when the server has a problem.
• You plan a production system with no backup and no recovery plan.
• You cannot get spare parts or a spare server when hardware fails.

So treat Proxmox as a tool, not a goal. Write down the need first, then pick the tool.

Here is a scenario. A small agency wants separate staging environments for three clients. Three LXC containers on one Proxmox server fit that job. The live sites stay on reliable hosting, so the risk stays separated.

When Should You Not Do This Yourself and Leave It to Your Hosting Provider?

Let us be honest: this is system administration, and we are a digital marketing and web team, not a hosting company. This guide gives people who want to run their own server a roadmap based on the official docs.

Leave the job to your provider or an experienced system administrator in these cases:

• The site brings in sales, and even one hour of downtime is costly.
• Customer data or payment information is stored on it.
• Your schedule leaves no time to follow security updates.
• You do not want to own hardware, data center, and network duties.

Server slowness also shows up in search. We explain the link in how site speed affects SEO, and the measurement in Google Lighthouse performance test.

In short, do not make server decisions on technical taste alone. Speed, security, and uptime directly shape visitor experience and sales. When you are unsure, expert help is cheaper in the long run.

What Checklist Should You Follow Before Starting With Proxmox VE?

Finally, here are the steps in a single list. Tick each item in order.

1. Check the CPU for the vmx or svm flag and enable virtualization in the BIOS.
2. Choose the disk layout: hardware RAID or ZFS.
3. Download the ISO from the official page and verify it.
4. Back up the data on the target disks.
5. Install, then open the web interface on port 8006.
6. Set the repository and update the system.
7. Create your first VM and LXC container as a test.
8. Set up a backup job and test one restore.
9. Restrict access to the interface.

To verify your IP and domain details, use our IP lookup and SSL checker tools. If you want support on the server side, get in touch with us.