Opt-in Linux 6.11 Kernel for Proxmox VE 8 available on test & no-subscription

[t.lamprecht]

We recently uploaded a 6.11 kernel into our repositories. The current 6.8 kernel will stay the default on the Proxmox VE 8 series, the newly introduced 6.11 kernel is an option.
The 6.11 based kernel may be useful for some (especially newer) setups, for example if there is improved hardware support that has not yet been backported to 6.8.
This follows our tradition of upgrading the Proxmox VE kernel to match the current Ubuntu version until we reach an (Ubuntu) LTS release, like the 6.8 kernel is, and then provide newer kernels as opt-in. The 6.11 kernel is based on the Ubuntu 24.10 Oracular release.

We have run this kernel on some parts of our test setups over the last few days without any notable issues, for production setups we still recommend keeping the 6.8 based kernel, or test on similar hardware/setups before moving all your production nodes up to 6.11.

How to install:

1. Ensure that either the pve-no-subscription or pvetest repository is set up correctly.
   You can do so via CLI text-editor or using the web UI under Node -> Repositories.
2. Open a shell as root, e.g. through SSH or using the integrated shell on the web UI.
3. apt update
4. apt install proxmox-kernel-6.11
5. reboot

Future updates to the 6.11 kernel will now be installed automatically when upgrading a node.

Please note:

• The current 6.8 kernel is still supported and will stay the default kernel.
• There were many changes, for improved hardware support and performance improvements all over the place.
  For a good overview of prominent changes, we recommend checking out the kernel-newbies site for 6.9, 6.10, and 6.11 (in progress).
• For those depending on Realtek's r8125 out-of-tree driver, we also uploaded a newer r8125-dkms package in version 9.013.02-1~bpo12+1 to fix support for that driver when used with 6.8+ kernels.
• The kernel is also available on the test and no-subscription repositories of Proxmox Backup Server and Proxmox Mail Gateway.
• If you're unsure, we recommend continuing to use the 6.8-based kernel for now.

Feedback about how the new kernel performs in any of your setups is welcome!
Please provide basic details like CPU model, storage types used, ZFS as root file system, and the like, for both positive feedback or if you ran into some issues, where using the opt-in 6.11 kernel seems to be the likely cause.

 

[toe]

Three machines upgraded

Zen 2 and 3 (One Epyc) - ZFS as root and datapools.

No problems so far. All went smoothly.

 

[ram75]

hola, después de instalar el kernel 6.11 no inician los LXC, probé generar uno nuevo pero tuve el mismo error

cgfsng_setup_limits_legacy: 3442 No such file or directory - Failed to set "memory.limit_in_bytes" to "536870912"
lxc_spawn: 1802 Failed to setup cgroup limits for container "122"
TASK ERROR: startup for container '122' failed

 

[t.lamprecht]

hola, después de instalar el kernel 6.11 no inician los LXC, probé generar uno nuevo pero tuve el mismo error

cgfsng_setup_limits_legacy: 3442 No such file or directory - Failed to set "memory.limit_in_bytes" to "536870912"
lxc_spawn: 1802 Failed to setup cgroup limits for container "122"
TASK ERROR: startup for container '122' failed

Can you please open a new thread and post the container config there (pct config VMID)?

 

[vesalius]

Small 3 node cluster. ZFS on root. Ceph 18.2. Have x553 SFP+ based networking and no issues so far.

 

[bbgeek17]

We will get it into our QA pipeline asap!

---

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

 

[Firebat]

For those depending on Realtek's r8125 out-of-tree driver, we also uploaded a newer r8125-dkms package in version 9.013.02-1~bpo12+1 to fix support for that driver when used with 6.8+ kernels.

Does it support r8126, too?

 

[Seed]

I updated to the 6.11 kernel and my Intel® Killer™ E5000B 5G LAN r8126 isn't detected. I also installed the dkms package and no go as well. pve 8.2.7. I'm on a very new z890 chipset mother board with Intel Ultra 265k

        *-network UNCLAIMED
             description: Ethernet controller
             product: Realtek Semiconductor Co., Ltd.
             vendor: Realtek Semiconductor Co., Ltd.
             physical id: 0
             bus info: pci@0000:84:00.0
             version: 04
             width: 64 bits
             clock: 33MHz
             capabilities: pm msi pciexpress msix vpd cap_list
             configuration: latency=0
             resources: ioport:5000(size=256) memory:b8800000-b880ffff memory:b8810000-b8813fff

I was able to get the NIC working, it's techinicall the: (Intel® Killer™ E5000B 5G LAN r8126) << for search doing the following:

grab the driver here:

https://www.realtek.com/Download/List?cate_id=584 (5G Ethernet LINUX driver r8126 for kernel up to 6.4)

or

https://www.realtek.com/Download/ToDownload?type=direct&downloadid=4445

move the source to your proxmox host, chmod executable the autorun.sh and let er rip. I did this on the newer 6.11 kernel and it works great.

       *-network DISABLED
             description: Ethernet interface
             product: Realtek Semiconductor Co., Ltd.
             vendor: Realtek Semiconductor Co., Ltd.
             physical id: 0
             bus info: pci@0000:84:00.0
             logical name: enp132s0
             version: 04
             serial: 34:5a:60:07:1d:ae
             capacity: 1Gbit/s
             width: 64 bits
             clock: 33MHz
             capabilities: pm msi pciexpress msix vpd cap_list ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation
             configuration: autonegotiation=on broadcast=yes driver=r8126 driverversion=10.014.01-NAPI latency=0 link=no multicast=yes port=twisted pair
             resources: irq:18 ioport:5000(size=256) memory:b8800000-b880ffff memory:b8810000-b8813fff

I have a feeling maybe, the module didn't load after installing the package noted here. Not sure though, as lsmod | grep r8126 was empty after installing the dkms driver, but is now showing when built from source.

lsmod | grep r8126
r8126                 204800  0

 

[mac.linux.free]

4 hosts upgraded mostly AMD Epyc. No problems so far.

 

[fiona]

hola, después de instalar el kernel 6.11 no inician los LXC, probé generar uno nuevo pero tuve el mismo error

cgfsng_setup_limits_legacy: 3442 No such file or directory - Failed to set "memory.limit_in_bytes" to "536870912"
lxc_spawn: 1802 Failed to setup cgroup limits for container "122"
TASK ERROR: startup for container '122' failed

Can you please open a new thread and post the container config there (pct config VMID)?

For reference: https://forum.proxmox.com/threads/linux-6-11-kernel-failure-to-start-lxc.156830/

 

[ram75]

kernel 6.11 OK on 6 IBM blade

proxmox-ve: 8.2.0 (running kernel: 6.11.0-1-pve)
pve-manager: 8.2.7 (running version: 8.2.7/3e0176e6bb2ade3b)

blade1: Intel(R) Xeon(R) CPU E5620 @ 2.40GHz (2 Sockets)
blade2: Intel(R) Xeon(R) CPU E5540 @ 2.53GHz (2 Sockets)
blade3: Intel(R) Xeon(R) CPU E5540 @ 2.53GHz (2 Sockets)
blade4: Intel(R) Xeon(R) CPU X5670 @ 2.93GHz (2 Sockets)
blade5: Intel(R) Xeon(R) CPU X5670 @ 2.93GHz (2 Sockets)

PBS 3.2-7 : Intel(R) Xeon(R) CPU E5540 @ 2.53GHz (2 Sockets)

SCSI storage controller Broadcom/LSI SAS1064ET PCI-Express Fusion-MPT SAS (rev 10) -- fails in kernel-6.8
all hosts with LVM storage