Install Proxmox VE on Debian 11 Bullseye
The installation of a supported Proxmox VE server should be done via bare-metal ISO installer. In some cases it makes sense to install Proxmox VE on top of a running Debian Bullseye 64-bit, especially if you want a custom partition layout. For this How-To any official Bullseye installation medium should work.
Install a standard Debian Bullseye (amd64)
Install a standard Debian Bullseye, for details consider the Debian installation guide, and configure a static IP. It is recommended to only install the "standard system utilities" and "SSH server" package selection, as Proxmox VE brings its own packages for QEMU and LXC. A desktop environment is not necessary.
Add an /etc/hosts entry for your IP address
The hostname of your machine must be resolvable via /etc/hosts. This means that in /etc/hosts you need one of the following entries for your hostname:
- 1 IPv4 or
- 1 IPv6 or
- 1 IPv4 and 1 IPv6
Note: This also means removing the address 127.0.1.1 that is present as default.
For instance, if your IP address is 192.168.15.77, and your hostname prox4m1, then your /etc/hosts file could look like:
127.0.0.1 localhost 192.168.15.77 prox4m1.proxmox.com prox4m1 # The following lines are desirable for IPv6 capable hosts ::1 localhost ip6-localhost ip6-loopback ff02::1 ip6-allnodes ff02::2 ip6-allrouters
You can test if your setup is ok using the hostname command:
hostname --ip-address 192.168.15.77 # should return your IP address here
Install Proxmox VE
Adapt your sources.list
Add the Proxmox VE repository:
echo "deb [arch=amd64] http://download.proxmox.com/debian/pve bullseye pve-no-subscription" > /etc/apt/sources.list.d/pve-install-repo.list
Add the Proxmox VE repository key:
wget https://enterprise.proxmox.com/debian/proxmox-release-bullseye.gpg -O /etc/apt/trusted.gpg.d/proxmox-bullseye.gpg chmod +r /etc/apt/trusted.gpg.d/proxmox-ve-release-7.x.gpg # optional, if you have a non-default umask
Update your repository and system by running:
apt update && apt full-upgrade
Install Proxmox VE packages
Install the Proxmox VE packages
apt install proxmox-ve postfix open-iscsi
Configure packages which require user input on installation according to your needs.
If you have a mail server in your network, you should configure postfix as a satellite system. Your existing mail server will then be the relay host which will route the emails sent by Proxmox VE to their final recipient. If you don't know what to enter here, choose local only and leave the system name as is.
Finally, reboot your system.
Recommended: remove the os-prober package
The os-prober package scans all the partitions of your host, including those assigned to guests VMs, to create dual-boot GRUB entries. If you didn't install Proxmox VE as dual boot beside another Operating System, you can safely remove the os-prober package.
apt remove os-prober
Connect to the Proxmox VE web interface
Connect to the admin web interface (https://youripaddress:8006). If you have a fresh install and haven not added any users yet, you should use the root account with your linux root password, and select "PAM Authentication" to log in.
Create a Linux Bridge
Once logged in, create a Linux Bridge called vmbr0, and add your first network interface to it.
Upload subscription key
The Proxmox VE enterprise repository is set up automatically during the installation. You should now upload your subscription key in the web interface. Afterwards, you can remove the installation repository.
resolv.conf gets overwritten
The PVE GUI expects to control DNS management and will no longer take its DNS settings from /etc/network/interfaces. Any package that auto-generates (overwrites) /etc/resolv.conf will cause DNS to fail, e.g. packages 'resolvconf' for IPv4 and 'rdnssd' for IPv6.
If you see
ipcc_send_rec failed: Connection refused
then you should review your /etc/hosts file according to the instructions above.
Optional: Remove the Debian kernel
Proxmox VE ships its own kernel. Therefore, it is safe to remove the default Debian kernel.
apt remove linux-image-amd64 'linux-image-5.10*'
Update and check grub2 config by running: