Opt-in Linux 7.0 Kernel for Proxmox VE 9 available

We recently uploaded the 7.0 (rc6) kernel to our repositories. The current default kernel for the Proxmox VE 9 series is still 6.17, but 7.0 is now an option.

We plan to use the 7.0 kernel as the new default for the upcoming Proxmox VE 9.2 and Proxmox Backup Server 4.2 releases planned later in Q2.
This follows our tradition of upgrading the Proxmox VE kernel to match the current Ubuntu version until we reach an Ubuntu LTS release, at which point we will only provide newer kernels as an opt-in option. The 7.0 kernel is based on the upcoming Ubuntu 26.04 Resolute release.

We have run this kernel on some of our test setups over the last few days without encountering any significant issues. However, for production setups, we strongly recommend either using the 6.17-based kernel or testing on similar hardware/setups before upgrading any production nodes to 7.0.

How to install:

Ensure that you either have 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 CLI text editor or using the web UI under Node -> Repositories.
Open a shell as root, e.g., through SSH or using the integrated shell on the web UI.
apt update
apt install proxmox-kernel-7.0
reboot

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

Please note:

The current 6.17 kernel is still supported and will stay the default kernel until further notice.
There were many changes for improved hardware support and performance improvements across the board.
For a good overview of prominent changes, we recommend checking out the kernel-newbies site for 6.18, 6.19, and 7.0.
The kernel is also available on the test and no-subscription repositories of Proxmox Backup Server and Proxmox Mail Gateway, and in the test repo of Proxmox Datacenter Manager.
The new 7.0-based opt-in kernel will not be made available for the previous Proxmox VE 8 release series.
If you're unsure, we recommend continuing to use the 6.17-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 issues where using the opt-in 7.0 kernel seems to be the likely cause.

Known Issues:
None at the time of writing.

Edit 2026-04-20: the kernel is now also available on the no-subscription repository.
Edit 2026-04-29: the kernel is now the default on no-subscription, and will be the default for Proxmox Backup Server. The remaining rollout for Proxmox VE will be happen over the next weeks.

Last edited: Apr 29, 2026

First!
Just kidding, tested with one physical atm, works okay.
Linux SPS2 7.0.0-1-rc6-pve #1 SMP PREEMPT_DYNAMIC PMX 7.0.0-1~rc6+1 (2026-03-30T09:17Z) x86_64 GNU/Linux

Kernel seems to be working well so far! (Uptime is less than 15 minutes so... will report back later...)

System details:
System: Dell PowerEdge R740XD
CPU: Intel Xeon Gold 6154
ZFS as root-filesystem on SATA PM883's
ZFS as VM-storage filesystem running NVMe Kioxia CD8-R's.

The server does seem to be running a little bit less power-efficient, around ~15W higher idle power-consumption after all machines have been booted.

Three machines upgraded

CPUs: Ryzen 3600, Epyc Rome, Ryzen 5825U
Storage: ZFS across all three for root and data.

All smooth, no issues, everything operating as expected.

runs fine on
AMD EPYC 9015
ASRockRack
TURIND8UD-2T/X550
zfs mirror
intel E810 nic
-------------------------
AMD EPYC 3151 4-Core Processor
GIGABYTE
MJ11-EC1-OT
zfs mirror
-------------------------
Intel(R) Pentium(R) CPU D1508 @ 2.20GHz
Supermicro
X10SDV-2C-TLN2F
zfs mirror
Intel Corporation Ethernet Connection X552/X557-AT 10GBASE-T

Last edited: Apr 3, 2026

All fine, zfs as boot - mirror.

CPU(s):24 x Intel(R) Core(TM) Ultra 9 285K (1 Socket)

Kernel Version Linux 7.0.0-1-rc6-pve (2026-03-30T09:17Z)

Boot Mode EFI (Secure Boot)

Manager Version pve-manager/9.1.7/16b139a017452f16

Well done, thanks !

Running great on test lab, small cluster of Dell 7070.

CPU(s) - 8 x Intel(R) Core(TM) i7-9700T CPU @ 2.00GHz (1 Socket)
Kernel Version - Linux 7.0.0-1-rc6-pve (2026-03-30T09:17Z)
Boot Mode- EFI (Secure Boot)
Manager Version - pve-manager/9.1.7/16b139a017452f16

No ZFS here, all LVM (thin volume for containers and vms)

Everybodys hardware is different, we will expect to see different results. In My environment I see a CPU reduction, not an increase.

Thank you for Proxmox!

I ran a full set of tests today, and everything seems to be working fine.

No changes are apparent compared to before the update.

Performance improvement: None
Performance degradation: None
Increase in power consumption: None
Errors in the log: None

Very good

Code:

[CPU] Intel Core Ultra 7 265K
[MEM] Crucial CP2K48G56C46U5 x4
[MB] Asrock Z890 Pro RS WiFi White (Latest BIOS 3.24 2026/2/5)
[PCIE 1 x16] PowerColor Hellhound Spectral White AMD Radeon RX 9070 XT 16GB GDDR6 (Pass-through to a virtual machine)
[PCIE 2 x1] USB (Pass-through to a virtual machine)
[PCIE 3 x4] Broadcom HBA9500-16i (The following storage devices are connected)
[PCIE 4 x4] Intel X710-DA2
[M.2 Gen5 x4] WDS200T4X0E-EC (Pass-through to a virtual machine)

Code:

Storage
[Boot Volume] ZFS RAID0 KPM5XMUG400G x1
[Local VM Volume] ZFS RAID1 HUSMM3280ASS201 x2
[Disk] HUSMR3232ASS200 x2 (Pass-through to a virtual machine)
[Disk] WUSTM3216ASS200 x2 (Pass-through to a virtual machine)
[Disk] ST8000VN0022 x2 (Pass-through to a virtual machine)
[Truenas ZFS over iSCSI Volume] (proxmox-truenas-native plugin v1.0.113)

Code:

Package
proxmox-ve: 9.1.0 (running kernel: 7.0.0-1-rc6-pve)
pve-manager: 9.1.7 (running version: 9.1.7/16b139a017452f16)
proxmox-kernel-helper: 9.0.4
proxmox-kernel-7.0.0-1-rc6-pve-signed: 7.0.0-1~rc6+1
pve-edk2-firmware: 4.2025.05-2
qemu-server: 9.1.6
pve-qemu-kvm: 10.1.2-7
zfsutils-linux: 2.4.1-pve1
pve-firmware: 3.18-2

Code:

pveperf

// kernel 6.17
pveperf
CPU BOGOMIPS:      155136.00
REGEX/SECOND:      11154807
HD SIZE:           358.47 GB (rpool/ROOT/pve-1)
FSYNCS/SECOND:     9668.38
DNS EXT:           14.48 ms
DNS INT:           16.04 ms

// kernel 7
pveperf
CPU BOGOMIPS:      155136.00
REGEX/SECOND:      11224671
HD SIZE:           358.49 GB (rpool/ROOT/pve-1)
FSYNCS/SECOND:     9437.17
DNS EXT:           19.15 ms
DNS INT:           15.93 ms

edit : 20260409

There are no issues with the update from 7.0.0-1~rc6+1 to 7.0.0-1~rc7+1 either.

Code:

proxmox-kernel-7.0.0-1-rc7-pve-signed amd64 7.0.0-1~rc7+1
proxmox-kernel-7.0 amd64 7.0.0-1~rc7+1

Last edited: Apr 9, 2026

After ~27h everything looks fine and within normal ranges (journalctl, dmesg, Zabbix monitoring stats)

Systems PVE:
- AMD EPYC 9474F 48C (Zen4), DDR5
- AMD EPYC 7402p 24C (Zen2), DDR4
- Intel XL710 10G NICs

VMs:
mostly OpenBSD
Linux
Windows 10

Configuration:
HA
ZFS Pool
Backup via Proxmox Backup

Systems PBS:
- AMD EPYC 7401p 24C (Zen1), DDR4
- AMD Ryzen 3 3200, 4C (Zen+), DDR4
- Intel XL710 10G NICs

Configuration:
ZFS Pool

Last edited: Apr 4, 2026

The kernel is also available on the test and no-subscription repositories of Proxmox Backup Server and Proxmox Mail Gateway [...]

Copy + paste oversight, I guess?

Looking forward to the stable release and the (hopefully quick) push into the no-subscription repositories of it. :cool:

Copy + paste oversight, I guess?
Looking forward to the stable release and the (hopefully quick) push into the no-subscription repositories of it.

Yeah, fixed now, thx for noticing. As this is just opt-in for now we probably make it available on no-subscription relative soon though.

I can observe a high IO pressure stall percentage after switching to this kernel—consistently above 90%—but without any noticeable side effects.... all my servers seem to be affected

Last edited: Apr 4, 2026

I can observe a high IO pressure stall percentage after switching to this kernel—consistently above 90%—but without any noticeable side effects.... all my servers seem to be affected

This is most likely stemming from the newer Qemu 10.2, which is also available on the test repo and is likely an accounting issue, but we're looking into that in any case.

Last edited: Apr 4, 2026

Has anyone tested SR-IOV functionality for iGPUs like the one in Alder Lake CPUs ? I'd be curious to know. Haven't switched my system to 7.0 yet as I need it for work, but if anyone's tested it, I'd be curious about your results. Thanks !

Last edited: Apr 6, 2026

I can observe a high IO pressure stall percentage after switching to this kernel—consistently above 90%—but without any noticeable side effects.... all my servers seem to be affected

This is most likely stemming from the newer Qemu 10.2, which is also available on the test repo and is likely an accounting issue, but we're looking into that in any case.

To fix this, all you need to do is downgrade the pve-qemu-kvm like this:

Code:

apt install pve-qemu-kvm=10.1.2-7

The Proxmox team should have pulled 10.2.1-1 off the test server once the high IO pressure was discovered.

To fix this, all you need to do is downgrade the pve-qemu-kvm like this:
Code:
apt install pve-qemu-kvm=10.1.2-7
The Proxmox team should have pulled 10.2.1-1 off the test server once the high IO pressure was discovered.

With respect, disagree - yes there is an issue but seemingly cosmetic. There is a suggestion that if you dont enable iothreads then you're not even affected. Discussed elsewhere - its "test" repo for a reason.

Yes there's that issue but early adopters also have a chance to test what else they might have configured for their specific environment. They also have the chance to report back any issues.

The questions like @AlexanderG poses are useful to know the answer to before it goes upwards into pve-non-subscription and pve-enterprise.

My £0.02

Happy Proxmox

The Proxmox team should have pulled 10.2.1-1 off the test server once the high IO pressure was discovered.

I don’t see any problem with packages that have already been flagged as problematic remaining in the “test repository.”

If that issue hadn’t been present in the test repository, we wouldn’t have noticed it or reported it in the first place.

I am keenly aware of just how valuable the test repository is.
*We were able to catch this during testing. That’s truly a relief. It’s a good thing this didn’t make it to production, isn’t it?

Since we cannot rule out the possibility of unknown issues existing alongside those already discovered, the more people who perform testing, the better.

The Proxmox team should have pulled 10.2.1-1 off the test server once the high IO pressure was discovered.

Why? it's purely accounting cosmetic issue and it's a test repo.

Since we cannot rule out the possibility of unknown issues existing alongside those already discovered, the more people who perform testing, the better.

Exactly this is why it's still valuable to keep it out there.

Last edited: Apr 7, 2026

I read that Kernel 7 has now SR-IOV already enabled.
Any hint how to use / enable it ?
I would need it for the intel iGPU (265H)

推荐订阅源

Proxmox Support Forum