Search results

source node: root@proxmox56:~# pvecm status Cluster information ------------------- Name: Proxmox7 Config Version: 11 Transport: knet Secure auth: on Quorum information ------------------ Date: Wed Apr 16 16:58:23 2025 Quorum provider: corosync_votequorum...

Hi, sometime, randomly, in proxmox 8.4.1 receive that error message during vm migration (all node upgraded). my cluster migrate from proxmox 7 to 8. task started by HA resource agent 2025-04-16 12:33:47 use dedicated network address for sending migration traffic (10.10.11.57)...

Thank you for your reply, but i wrote about i40e driver for XL710 40Gbe Nic NOT about igb Nic (1Gbit ethenet product). These products use different drivers. Actually i can't upgrade server until october, i'd like to solve problem with actual configuration. Please check version about my driver...

Hi, i40e driver included in proxmox 4.15.xx.xx kernel is obsolete. Please read thread https://forum.proxmox.com/threads/kernel-4-15-18-56-nfs-freeze-with-intel-nic-xl710.70112/ and https://yawnbox.wordpress.com/2018/10/27/updating-intels-i40e-driver-in-ubuntu-18-10/ Latest Intel XL710 driver...

The last proxmox 5.4 kernel - Linux proxmox50 4.15.18-28-pve #1 SMP PVE 4.15.18-56 (Wed, 08 Apr 2020 20:06:11 +0200) x86_64 GNU/Linux - containti40 driver version : root@proxmox50:~# modinfo i40e filename: /lib/modules/4.15.18-28-pve/kernel/drivers/net/ethernet/intel/i40e/i40e.ko version...

Node configuration (for all nodes): pveversion -v proxmox-ve: 5.4-2 (running kernel: 4.15.18-28-pve) pve-manager: 5.4-15 (running version: 5.4-15/d0ec33c6) pve-kernel-4.15: 5.4-17 pve-kernel-4.15.18-28-pve: 4.15.18-56 pve-kernel-4.15.18-27-pve: 4.15.18-55 pve-kernel-4.15.18-25-pve: 4.15.18-53...

Hi, i've installed a new Intel Nic XL710 into all my cluster nodes to connect the new NFS storage based on Centos 7. After migrate about 20 virtual servers from old storage, the migration node freeze with kernel error below (freeze only nfs client that point to a new NFS storage, other storage...

No, is not needed to upgrade to 4.x proxmox version. But i've installed my server from 4.3 proxmox cdrom, the controller run ok, the new kernel recognize it. i've prefered to re-create a new cluster then migrate VM. Paolo

Hi, i've the some problem on two Supermicro server.... see my post: https://forum.proxmox.com/threads/urgent-cannot-boot-after-proxmox-3-4-upgrade-to-latest-kernel.29699/#post-149924

UP .... Please Help Me !

Please, can you help me about that problem ? see https://forum.proxmox.com/threads/urgent-cannot-boot-after-proxmox-3-4-upgrade-to-latest-kernel.29699/ thank you in advance Paolo

Hi, today i've upgraded one of my cluster node (supermicro) from 2.6.32-41 to 2.6.32-47 kernel version. This upgrade is needed to later upgrade to 4.x proxmox version, is'nt it ? During reboot i get the following screen error. modinfo of aacraid with old working kernel 2.6.32-41-pve...

Proxmox updated to the latest version. Problem solved. Thank you a lots. Paolo

Installed and update yesterday. Current version: 4.0-48/0d8559d0

Hi, i've found a bug in bond configuration function. If i check Autostart checkbox the /etc/interfaces file do not contain "auto bond0" command then do not start correctly. I need to add it manual. Paolo

Ho un cluster di 4 nodi basato su proxmox 3.1.x volevo fare l'upgrade alla 3.3-5 hai consigli da darmi ? non vorrei distruggere un cluster in produzione perfettamente funzionante... Grazie Paolo

Hello, I have a 4 nodes cluster with promox 3.1 Yesterday, one of the nodes’ motherboard failed, so I manually moved the config files of the virtual servers on the other nodes, entering the following command line: mv /etc/pve/nodes/proxmox11/qemu-server/124.conf...