How to Install Proxmox VE 9 on Debian 13 (Trixie)
Turn a Debian 13 server into a Proxmox VE 9 host: fix hostname resolution, add the repository, boot the Proxmox kernel, install the packages and set up a bridge.
Proxmox VE is an open-source virtualization platform that manages KVM virtual machines and LXC containers from one web interface. The supported way to install it is the bare-metal ISO, but Proxmox also documents installing it on top of an existing Debian system, which is useful when you need a custom partition layout or your provider only offers stock Debian images. This guide follows that documented route for Proxmox VE 9 on Debian 13 (Trixie), 64-bit. Debian 8 (Jessie) and the Proxmox releases built on it are long out of support.
Requirements
- A fresh Debian 13 amd64 installation with only the standard system utilities and SSH server. No desktop environment.
- A static IP address and
rootaccess. All commands below are run asroot. - Hardware virtualization (Intel VT-x or AMD-V) if you want to run KVM virtual machines.
- Secure Boot disabled if the system boots with systemd-boot; Proxmox states that installing on top of Debian is not supported with that combination.
Check whether the CPU exposes virtualization extensions:
grep -E -c '(vmx|svm)' /proc/cpuinfoA result of 0 means KVM guests cannot be hardware-accelerated. That is the normal situation on a VPS, which is already a virtual machine, unless the provider enables nested virtualization. LXC containers still work there. For production use, install Proxmox VE on a dedicated server.
Proxmox VE 9 is tied to Debian 13. On Debian 12 the matching release is Proxmox VE 8, which has its own repository and installation page; do not mix the two.
Step 1: Make the hostname resolve to the server's IP
The hostname must resolve to an address other hosts can reach, not to a loopback address. This is the most common cause of a failed installation. Edit /etc/hosts, remove the hostname from any 127.0.1.1 line, and add a line with the real address:
127.0.0.1 localhost
203.0.113.10 pve1.example.com pve1
# The following lines are desirable for IPv6 capable hosts
::1 localhost ip6-localhost ip6-loopback
ff02::1 ip6-allnodes
ff02::2 ip6-allroutersTest it. The command must return at least one non-loopback address:
hostname --ip-addressOn cloud images, cloud-init may regenerate /etc/hosts at boot. If your change disappears after a reboot, disable its hosts management before you continue.
Step 2: Add the Proxmox VE repository
Create the repository definition in deb822 format:
cat > /etc/apt/sources.list.d/pve-install-repo.sources << EOL
Types: deb
URIs: http://download.proxmox.com/debian/pve
Suites: trixie
Components: pve-no-subscription
Signed-By: /usr/share/keyrings/proxmox-archive-keyring.gpg
EOLDownload the repository keyring:
wget https://enterprise.proxmox.com/debian/proxmox-archive-keyring-trixie.gpg -O /usr/share/keyrings/proxmox-archive-keyring.gpgVerify the file before trusting it. Compare the output with the checksum published on the Proxmox wiki page linked at the end of this section; at the time of writing it lists 136673be77aba35dcce385b28737689ad64fd785a797e57897589aed08db6e45.
sha256sum /usr/share/keyrings/proxmox-archive-keyring.gpgUpdate the package lists and bring the system fully up to date:
apt update && apt full-upgradeThe pve-no-subscription repository is intended for testing and non-production use. See the official Install Proxmox VE on Debian 13 Trixie page for the current checksum and any changes to these steps.
Step 3: Install and boot the Proxmox kernel
Some Proxmox packages depend on features of its own kernel, so install and boot it first:
apt install proxmox-default-kernelsystemctl rebootAfter the reboot, uname -r should show a version ending in -pve.
Step 4: Install the Proxmox VE packages
apt install proxmox-ve postfix open-iscsi chronyWhen Postfix asks for a configuration type, choose Local only and keep the suggested system name unless you have a mail server to relay through, in which case choose Satellite system. chrony can be replaced by another NTP daemon, but Proxmox advises against systemd-timesyncd on servers.
Step 5: Remove the Debian kernel and os-prober
Keeping the stock Debian kernel alongside the Proxmox one can break upgrades, so Proxmox requires removing it:
apt remove linux-image-amd64 'linux-image-6.12*'Regenerate the GRUB configuration (not needed if the system uses systemd-boot):
update-grubUnless the server dual-boots another operating system, also remove os-prober. It scans every partition, including disks assigned to virtual machines, and could add them as boot entries:
apt remove os-proberStep 6: Log in to the web interface
Open https://203.0.113.10:8006 in a browser, replacing the address with your own, and accept the self-signed certificate. Select the Linux PAM standard authentication realm and log in as root with the system password. If a firewall sits in front of the server, allow TCP port 8006 only from the addresses you administer from.
Step 7: Create a network bridge
Guests attach to a Linux bridge, conventionally named vmbr0. You can create it under System → Network in the web interface or by editing /etc/network/interfaces. With a physical interface called eno1, the default bridged layout moves the host address onto the bridge:
auto lo
iface lo inet loopback
iface eno1 inet manual
auto vmbr0
iface vmbr0 inet static
address 203.0.113.10/24
gateway 203.0.113.1
bridge-ports eno1
bridge-stp off
bridge-fd 0Bridging gives each guest its own MAC address on the provider's network. Many hosting networks drop traffic from MAC addresses they did not assign; in that case use the routed or masquerading (NAT) setups described in the Proxmox VE network configuration documentation instead. Apply network changes from the console rather than over SSH, so a mistake does not cut you off.
Step 8: Subscription and repositories
The installation also configures the enterprise repository, which needs a subscription key. With a subscription, upload the key in the web interface and remove the installation repository:
rm /etc/apt/sources.list.d/pve-install-repo.sourcesWithout one, keep the no-subscription repository and disable the enterprise entries under Updates → Repositories on the node, otherwise apt update reports authentication errors for them.
Troubleshooting
ipcc_send_rec[1] failed: Connection refusedor a failingpve-clusterservice: the hostname does not resolve to a non-loopback address. Go back to step 1.error: bad shim signatureat boot: disable Secure Boot.- DNS stops working: Proxmox manages
/etc/resolv.confitself. Remove packages that regenerate it, such asresolvconforrdnssd.
Frequently asked questions
Can I run Proxmox VE on a VPS?
It installs, and LXC containers work, but KVM guests need hardware virtualization, which a VPS only has when the provider exposes nested virtualization. Even then performance is lower than on bare metal, and Proxmox recommends dedicated hardware for production.
Should I use the ISO installer instead?
If you can boot an ISO, yes. It is the installation method Proxmox supports and it sets up storage, networking and the kernel in one pass. Installing over Debian is for cases where you need a partition layout or boot setup the installer does not offer.
Is the no-subscription repository safe to use?
It carries the same software, but packages land there before they have been through the testing applied to the enterprise repository. Proxmox recommends the enterprise repository for production servers.
How do I upgrade later?
Within a major release, use apt update && apt full-upgrade or the Updates panel. Never use plain apt upgrade on a Proxmox host, because it can hold back packages that must be upgraded together.