Opt-in Linux 7.3 Kernel for Proxmox VE 9 available

t.lamprecht

Proxmox Staff Member
Staff member
Jul 28, 2015
6,908
5,667
315
South Tyrol/Italy
shop.proxmox.com
We recently uploaded the 7.3 kernel to the test and no-subscription repositories of all our Debian Trixie-based releases. It will stay an opt-in kernel for these release series, while the 7.0-based kernel remains the default for them.

Unlike our previous kernels, which were based on the Ubuntu kernel, the 7.3 kernel is based directly on the upstream stable branch from kernel.org. 7.3 is also likely to become this year's upstream longterm (LTS) kernel.
We have a long-standing and good working relationship with the upstream kernel community when it comes to bug reports and fixes. Basing our kernel directly on the upstream stable branch shortens the path in both directions even further: upstream fixes reach our kernel with less effort on our side, and what we and our community find and fix applies directly to the code that upstream maintains. It also keeps the gap to current upstream development small.
Naturally, this also comes with a somewhat different regression risk, for example, if an Ubuntu downstream patch or a kernel build config option is no longer present.

We have run this kernel on some of our test setups over the last few weeks without encountering any significant issues. The general approach of basing our kernel directly on upstream stable has been in testing for longer, as we already packaged and evaluated the upstream 7.2 kernel this way. However, for production setups, we strongly recommend either using the 7.0-based kernel or thoroughly testing on similar hardware/setups before upgrading any production nodes to 7.3.

How to install:
  1. Ensure that you have either the pve-test repository (or pbs-test for Proxmox Backup Server) or the respective no-subscription repositories set up correctly.
    You can do so via a 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 in the web UI.
  3. apt update
  4. apt install proxmox-kernel-7.3
  5. reboot
Future updates to the 7.3 kernel will now be installed automatically when upgrading a node.

Please note:
  • The current 7.0 kernel is still supported and will stay the default kernel for the current release series.
  • There were many changes to improve hardware support and performance across the board.
    For a good overview of prominent changes, we recommend checking out the kernel-newbies site for 7.1, 7.2, and 7.3.
  • The new 7.3-based opt-in kernel will not be made available for older release series.
  • If you're unsure, we recommend continuing to use the 7.0-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, and whether you use ZFS as your root file system, whether your feedback is positive or you've run into issues that seem likely to have been caused by the opt-in 7.3 kernel.
As this is our first kernel based directly on upstream stable, we are especially interested in anything that worked with the 7.0 kernel but no longer does with 7.3, such as missing drivers, modules, or features.

Known Issues:
None at the time of writing.
 
Tested with 7.3.5-1-pve:
- Dell Poweredge R730 - 2 x Intel(R) Xeon(R) CPU E5-2630 v3 / 128Gb RAM / LVM thick guests on H730 RAID
- Supermicro X9DR3-F - 2 x Intel(R) Xeon(R) CPU E5-2630 v2 / 64Gb RAM / LVM thick guests on SATA RAID1 via mdadm

- AMD Ryzen 7 3700X + MSI X570-A PRO (MS-7C37) mainboard / 128Gb RAM / ZFS for VMs, LV for PVE install, pass through SATA SSD
- AMD Ryzen 7 5700G + Gigabyte B550M DS3H AC R2 mainboard / 128Gb RAM / ZFS for VMs, LV for PVE install

Both Ryzen systems have ConnectX3 10Gbit NICs.

All booted and functional.
 
If you are already using the pve-enterprise repo, and you *only* want to pull in kernel updates from the `pve-no-subscription` repo, you can drop in the following as the file: /etc/apt/preferences.d/pve-no-subscription:

Code:
Package: *
Pin: release c=pve-no-subscription
Pin-Priority: -1

Package: proxmox-kernel-7.3*
Pin: release c=pve-no-subscription
Pin-Priority: 600

Package: pve-firmware*
Pin: release c=pve-no-subscription
Pin-Priority: 600

This should only pull in updates to the kernel from `pve-no-subscription` repo and leave other packages untouched. This is currently at a 'theoretically works' to block out any other updates from the pve-no-subscription repo and was tested against the `pve-test` repo for formatting & syntax, but due care should be taken when testing this filtering too and validating expected results.

This wouldn't be supported under your Support Agreement - but would allow you to run the kernel on test hardware.
 
Got this installed on my little 3-node cluster. 2 × Intel 285H and 1 × 255H. No issues so far.

One thing is, I have been using the out-of-tree Realtek r8152 driver to power my 5Gbit USB-C NICs. Since those are now supported in tree, I removed the DKMS drivers and am now using the builtin:

Code:
# ethtool -i en1
driver: r8152
version: 7.3.5-1-pve
firmware-version:
expansion-rom-version:
bus-info: usb-0000:00:0d.0-3
supports-statistics: yes
supports-test: no
supports-eeprom-access: no
supports-register-dump: no
supports-priv-flags: no

It's working fine...

Code:
# iperf3 -c 192.168.40.21
Connecting to host 192.168.40.21, port 5201
[  5] local 192.168.40.51 port 44838 connected to 192.168.40.21 port 5201
[ ID] Interval           Transfer     Bitrate         Retr  Cwnd
[  5]   0.00-1.00   sec   591 MBytes  4.95 Gbits/sec    0   1.23 MBytes
[  5]   1.00-2.00   sec   588 MBytes  4.93 Gbits/sec    0   1.30 MBytes
[  5]   2.00-3.00   sec   588 MBytes  4.93 Gbits/sec    0   1.30 MBytes
[  5]   3.00-4.00   sec   586 MBytes  4.91 Gbits/sec    0   1.30 MBytes
[  5]   4.00-5.00   sec   588 MBytes  4.93 Gbits/sec    0   1.30 MBytes
[  5]   5.00-6.00   sec   586 MBytes  4.92 Gbits/sec    0   1.30 MBytes
[  5]   6.00-7.00   sec   588 MBytes  4.93 Gbits/sec    0   1.30 MBytes
[  5]   7.00-8.00   sec   588 MBytes  4.93 Gbits/sec    0   1.30 MBytes
[  5]   8.00-9.00   sec   587 MBytes  4.92 Gbits/sec    0   1.30 MBytes
[  5]   9.00-10.00  sec   589 MBytes  4.94 Gbits/sec    0   1.95 MBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-10.00  sec  5.74 GBytes  4.93 Gbits/sec    0            sender
[  5]   0.00-10.00  sec  5.74 GBytes  4.93 Gbits/sec                  receiver

iperf Done.

The only thing is, I'm getting this error on boot about missing firmware:
Code:
# dmesg | grep r8152
[    1.503506] usbcore: registered new device driver r8152-cfgselector
[    1.616533] r8152-cfgselector 2-3: reset SuperSpeed Plus Gen 2x1 USB device number 2 using xhci_hcd
[    1.632967] r8152 2-3:1.0: Direct firmware load for rtl_nic/rtl8157-1.fw failed with error -2
[    1.632971] r8152 2-3:1.0: unable to load firmware patch rtl_nic/rtl8157-1.fw (-2)
[    1.672228] usbcore: registered new interface driver r8152
[    1.679267] r8152 2-3:1.0 enx00242715821b: renamed from eth0
[    2.367190] r8152 2-3:1.0 en1: renamed from enx00242715821b
[    3.820619] r8152 2-3:1.0 en1: entered allmulticast mode
[    3.820653] r8152 2-3:1.0 en1: entered promiscuous mode
[    5.866731] r8152 2-3:1.0 en1: Promiscuous mode enabled
[    5.866838] r8152 2-3:1.0 en1: carrier on

Anyone know if this is "normal" or how to fix it? I found this...
 
The firmware file `rtl_nic/rtl8157-1.fw` isn't included in the linux-firmware repo [0]. As such, its unlikely to be included in a package until it is.

If you power off the hardware and power it on again, does it still work without that firmware file?

Otherwise, if you obtain it from elsewhere, you can copy it to /usr/lib/firmware/rtl_nic on your PVE install and it should pick it up as expected on the next boot.

[0]: https://gitlab.com/kernel-firmware/linux-firmware/-/tree/main/rtl_nic?ref_type=heads
 
Thanks for making the 7.3 kernel available in the test repositories!

Switching directly to the upstream kernel.org stable branch rather than tracking Ubuntu builds is a very welcome move, especially with 7.3 targeting LTS status. We are currently rolling this out on a few staging bare-metal nodes with ZFS on NVMe pools to evaluate IO stability and KVM hypervisor throughput under load.

Initial tests boot smoothly without dmesg anomalies. Appreciate the continued hard work from the Proxmox engineering team!