惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

Last Week in AI
Last Week in AI
阮一峰的网络日志
阮一峰的网络日志
P
Proofpoint News Feed
让小产品的独立变现更简单 - ezindie.com
让小产品的独立变现更简单 - ezindie.com
MongoDB | Blog
MongoDB | Blog
云风的 BLOG
云风的 BLOG
OSCHINA 社区最新新闻
OSCHINA 社区最新新闻
J
Java Code Geeks
WordPress大学
WordPress大学
T
The Blog of Author Tim Ferriss
V
Visual Studio Blog
小众软件
小众软件
Microsoft Azure Blog
Microsoft Azure Blog
博客园_首页
IT之家
IT之家
Vercel News
Vercel News
C
Check Point Blog
Google DeepMind News
Google DeepMind News
月光博客
月光博客
D
DataBreaches.Net
酷 壳 – CoolShell
酷 壳 – CoolShell
美团技术团队
Y
Y Combinator Blog
Hugging Face - Blog
Hugging Face - Blog

Proxmox Support Forum

[SOLVED] - Github Auth for Mirrors-Kernel Repo? [Automation] Mass migration tool for MS Win11/Server Proxmox GUI hang - not response is it possible to reject or quarantine spam based on conditions I set ? The PVENode task list in PVE9 is partially obscured due to the terminal font being too large. About 100% error reporting due to pveproxy.service hooks Kubernetes overlay networking breaks when upgrading from PVE 9.1 to PVE 9.2.3 Zentraler Speicher No space left on device Combine datastore and direct file archival to tape Kernel panic VFS: Unable to mount root fs on unknown-block (0,0) sobald ein 7.x Kernel verwendet wird. How to migrate disk of a VM from one ZFS to another Windows Server 2025 fails to boot after PVE 9.2 / Linux 7.0 Kernel upgrade Cannot Install Proxmox on T610 Poweredge with H700 PERC card sdn Config. gateway not reachable How to safely change domain/FQDN? Welche Filterquote erreicht ihr? NFS Share status unknown on 2 of 5 nodes Can't connect to PVE9 consoles [solved] Can't connect to PVE9 consoles [solved] [SOLVED] - Use secondary network for PVE commands Created cluster, one node storage gone BUG: proxmox mail gateway FROM = null bypass spam filtering Moving existing PBS from VMWare workstation to PVE cluster Does eBGP SDN fabric support external peering? Bug: PDM 1.1 not recognizing valid license status Proxmox GUI hang - not response PVE crashes unexpectedly Proxmox Backup Server 4.2 released! Advice
[BETA] Community Linux 7.1 kernel packages for Proxmox VE...
invalid@exam · 2026-06-20 · via Proxmox Support Forum

For all of y'all that like bleeding-edge kernels, or need better support for the latest hardware, I'm sharing a first beta of a community-built Proxmox-style kernel based on Linux 7.1.0.

If you're the type who wants to try newer drivers, newer kernel features, and hardware enablement ahead of the official Proxmox kernel line, this may be worth a look — but only on test systems. -- Unless you are real daring :)

This is not an official Proxmox release. It is an unofficial/community build intended for testing and feedback only. And maybe a preview of what's to come.

Version: 7.1.0-1~beta1+1
Kernel image: 7.1.0-1-pve
Base: Ubuntu stonking / 26.10 beta (Ubuntu-7.1.0-5.5)
ZFS userland: 2.4.3-pve1 (separate download)
Architecture: amd64

Who is this for?

  • People who want a newer kernel than the current stable Proxmox 7.0 line
  • Users with newer hardware that may benefit from more recent kernel drivers?
  • Anyone interested in testing Linux 7.1 on Proxmox before Proxmox makes one officially
  • A good learning expeirence in how to make a kernel -- If you compile it yourself.

Downloads

There is no apt repository for these packages. You download the .deb files and install them locally.

Important warnings

  • Testing only — not for production
  • Based on Ubuntu's beta 7.1 kernel sources, which is based on the final Kernel 7.1 release.
  • Proxmox-specific patches have been rebased for 7.1, but are not QA'd like official Proxmox kernels
  • No Secure Boot support — this is a custom/community kernel and is not signed for Secure Boot. Disable Secure Boot in firmware/BIOS before trying to boot it.
  • Installs alongside your existing kernel (for example 7.0.x-pve) and is default at boot, unless you pin your current kernel.
  • If you use ZFS, you must install the matching ZFS userland packages from the ZFS repo above. The old ones may still work, but it is better for them to all match.
  • apt does not auto-discover .deb files in a folder — you must list every required package on the command line

What this includes

  • Linux 7.1.0
  • Refreshed Proxmox patch series (bridge MAC behavior, PCI ACS/passthrough helpers, KVM tweaks, wireless regdb certs, etc.)
  • Rebased KVM MBEC/GMET support for nested virtualization
  • Updated firmware package: pve-firmware 3.19-0b1
  • ZFS kernel modules built into the kernel package; ZFS userland installed separately

Some 7.0-era backports were dropped because they are already in the 7.1 kernel. Patch coverage is not the same as the current stable proxmox-kernel-7.0 line. Hence why it is not recommended on a production machine.

Installation

See releases on Github.

Feedback welcome

If you try this, I'd appreciate reports on:

  • Boot success/failure on your hardware
  • KVM / nested virtualization
  • ZFS pool health and basic operations
  • PCI passthrough
  • Networking / bridges / VLANs
  • Any regressions compared with your current 7.0.x-pve kernel

I have tested all of these on my Ryzen 7 9700X + RX 6900 XT with PCI passthrough to macOS Tahoe, Windows 11, Fedora. Running with zfs on NVME boot drive. I also have many LXC's, and have Podman running in containers with no issuses with this kernel. I also have vendor_reset DKMS for the AMD passthrough from when I had a VEGA64 in there. I will have to test to see if the 6900 XT works well without it.

Please report issues on GitHub:

Thanks to anyone willing to test this early. Again: please use this only on non-production systems.