Search results

confirmed

same issue with Dell R630

we have several PVE cluster. the dell R630 cluster failed to boot with CPU error, and dell R640 cluster works with proxmox-kernel-6.17.2-1-pve-signed

$ dpkg -l|grep proxmox-kernel-6.17 ii proxmox-kernel-6.17 6.17.2-1 all Latest Proxmox Kernel Image ii proxmox-kernel-6.17.2-1-pve-signed 6.17.2-1 amd64 Proxmox Kernel Image (signed)

i upgrade three nodes pve to 6.17.2-1-pve, reboot and failed. all nodes are Dell R630，all are failed to boot new kernel. i should boot 6.14.11-4-pve to recover. $ lscpu Architecture: x86_64 CPU op-mode(s): 32-bit, 64-bit Address sizes: 46 bits...

why not put 18.2.4 in no-subscription repo? is any issue?

thanks, disalbe iothread, then it's OK now. when will the patch be merged?

same issue for my centos 7 guest vm. it's OK for almalinux8, debian 12. centos has 64G RAM and 16VCPU( 2 socket)

i downgrade the pve-qemu-kvm from 8.1.2-4 to 8.0.2-3, same problem.

https://gitlab.com/qemu-project/qemu/-/issues/2006 Host environment Operating system: Proxmox 8.1(Debian 12.2) OS/kernel version: Linux pve0.wx.xxxx.com 6.5.11-4-pve #1 SMP PREEMPT_DYNAMIC PMX 6.5.11-4 (2023-11-20T10:19Z) x86_64 GNU/Linux Architecture...

request for support Erasure Coded pools

it's hardware limit of ConnectX-3 card. https://forum.proxmox.com/threads/vlan-with-tag-above-126-problem.46072/

it does not work even though i remove mtu 9000. it dose work if vlan number less than 127 with bridge-vlan-aware enabled. auto vmbr0 iface vmbr0 inet static bridge-ports bond0 bridge-stp off bridge-fd 0 bridge-vlan-aware yes bridge-vids 2-4094 mtu 9000 address 172.18.100.10/24 gateway...

vlan 1002 and 1003 only worked when i comment "bridge-vlan-aware yes", otherwise it will not ping nodes each other. iface enp94s0 inet manual iface enp94s0d1 inet manual auto bond0 iface bond0 inet manual bond-slaves enp94s0 enp94s0d1 bond-miimon 100 bond-mode 802.3ad...