wikiKnown Issues Proxmox VE
In Proxmox VE various issues may occur in combination with newer kernels. The following known issues are structured by areas and versions.
General
- Network: Network interface names may change after a kernel update, which can result in loss of network connectivity
- Network: Firmware update of Broadcom add-on cards (network cards)
- Kernel: To improve system stability (AMD), certain kernel parameters can be applied
Network Name Pinning
This snippet pins the network interface naming to the "PCI" location. This means that as long as network cards are not moved to different PCI slots, their names should remain consistent (even after updates). Warning: This snippet initially determines the interface names based on the PCI location. You will need to reconfigure (rename) the interfaces once after applying it:
cp /usr/lib/systemd/network/99-default.link /etc/systemd/network/99-default.link sed -i 's/NamePolicy=keep kernel database onboard slot path/NamePolicy=path/' /etc/systemd/network/99-default.link update-initramfs -u
Firmware Update (Addon Card)
Important note: This snippet should only be used for Broadcom add-on cards. This script does not work with onboard NICs from Broadcom.
apt install unzip
cat << 'EOF' > bcm-nic-update.sh
wget https://www.thomas-krenn.com/redx/tools/mb_download.php/ct.YuuHGw/mid.y9b3b4ba2bf7ab3b8/bnxtnvm.zip
unzip bnxtnvm.zip
chmod +x bnxtnvm
for i in $(./bnxtnvm listdev | grep 'Device Interface Name' | awk '{print $5}')
do
./bnxtnvm -dev=$i install -online -y
done
EOF
chmod +x bcm-nic-update.sh
./bcm-nic-update.sh
Kernel Recommendation
We currently recommend the following parameters as best practice. These improve the overall system stability:
# install all updates to get the latest kernel apt update && apt dist-upgrade # apply the following kernel parameters via snippet sed -i '$ s/$/ pcie_port_pm=off/' /etc/kernel/cmdline sed -i '$ s/$/ pcie_aspm.policy=performance/' /etc/kernel/cmdline sed -i '$ s/$/ libata.force=noncq/' /etc/kernel/cmdline update-initramfs -u -k all && proxmox-boot-tool refresh
Version 9.0
Broadcom HBA Issue
In the current Proxmox kernel (6.17), issues occur with certain Broadcom HBAs.
The problem manifests as NVMe and SSD devices randomly disappearing from the Proxmox overview and no longer being initialized. After a reboot, all drives reappear for a certain period of time.
We therefore recommend pinning to a stable kernel:
# install the kernel apt install proxmox-kernel-6.14.11-6-pve apt install proxmox-headers-6.14.11-6-pve # pin the kernel proxmox-boot-tool kernel list proxmox-boot-tool kernel pin 6.14.11-6-pve proxmox-boot-tool refresh # update initramfs update-initramfs -u -k all # reboot node reboot
Version 8.2
- Network: Broadcom network cards may experience issues where networking does not work after a reboot
- Q-Device: When setting up a Q-Device in Proxmox VE 8.2, errors may occur during creation: see bug report https://bugzilla.proxmox.com/show_bug.cgi?id=5461
Q-Device
When setting up a Q-Device in Proxmox VE 8.2, errors may occur during creation. Bug report: https://bugzilla.proxmox.com/show_bug.cgi?id=5461
Network Broadcom Down
In combination with Proxmox 8.2 and kernel 6.8, an issue occurs with Broadcom network cards. This can be resolved by blacklisting the RDMA driver and performing a firmware upgrade:
echo "blacklist bnxt_re" >> /etc/modprobe.d/blacklist-bnxt_re.conf update-initramfs -u
Afterwards, the server must be rebooted once for the changes to take effect.
 |
Author: Jonas Sterr Jonas Sterr has been working for Thomas-Krenn for several years. Originally employed as a trainee in technical support and then in hosting (formerly Filoo), Mr. Sterr now mainly deals with the topics of storage (SDS / Huawei / Netapp), virtualization (VMware, Proxmox, HyperV) and network (switches, firewalls) in product management at Thomas-Krenn.AG in Freyung.
|
