PVE Kernel Pin
PVE Kernel Pin is a simple tool for Proxmox users that locks a specific version of the system’s "engine" (the kernel) in place.
Platform availability
Available on 1 of 10 platforms
- Unraid (not listed)
- TrueNAS (not listed)
- Umbrel (not listed)
- ZimaOS (not listed)
- Proxmox
- Helm (not listed)
- Mac (not listed)
- Windows (not listed)
- Linux (not listed)
- Any server (not listed)
Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.
64/100 Good
- Maintained
- 100last commit 19 days ago
- Popular
- 46209 GitHub stars
- Easy to install
- 150 install platforms, install notes
- Light to run
- 502 GB minimum RAM
- Security check
- 75no serious findings
- GitHub stars
- 209
- Open issues
- 1
- Last commit
- 2026-11-02
- Activity
- steady
Checked 15 days ago - source: GitHub (proxmox/pve-kernel)
Resources & Compatibility
Minimum requirements: 2 GB RAM.
Checked 41 days ago - source: Docker Hub image tags and published docs
First-install notes
- Install the Proxmox driver in Rancher In Rancher, add the pve-node-driver Helm chart (a packaged install file for Kubernetes) and install the driver version you want. If this step is skipped, Rancher won’t have the Proxmox node driver or UI extension, so you can’t manage Proxmox VMs from Rancher. source
- Configure Rancher for no internet If your Rancher setup can’t reach the internet, set nodeDriver.url and uiPlugin.endpoint to your own internal file URLs. Without those, Rancher can’t pull the driver or UI extension, so the Proxmox driver install will fail. source
Fetched 41 days ago - each note links to its source
Variants
Alternatives
No alternatives collected yet.
Common questions
How do I pin an older Proxmox kernel?
Run proxmox-boot-tool kernel list to find the kernel version, then run proxmox-boot-tool kernel pin with that version. Reboot after pinning so VMs use the pinned kernel.
How can I test a newer kernel once after pinning an older one?
Use proxmox-boot-tool kernel pin <kernel> --next-boot to pin the kernel only for the next boot. This is useful for checking whether an updated kernel fixed the issue that caused the pin.
Which older kernel should I pin if a PVE 8.2 kernel breaks DKMS SR-IOV on an Intel iGPU?
Pin 6.5.13-3-pve-signed, because a user held back a newer PVE 8.2 kernel after it broke a DKMS SR-IOV Intel iGPU setup that worked on that signed kernel.
What should I do if kernel pinning appears to have no effect?
Rerun the proxmox-boot-tool pin commands and check the kernel list to verify the selected kernel.
Answers sourced from forum.proxmox.com, forum.proxmox.com, www.reddit.com, www.reddit.com
Community
- Proxmox Kernel 5.15.60-1-pve Breaks PCI Passthrough - Reddit (reddit)
- Question about downgrading to 6.5.13-3-pve-signed kernel on ... - Reddit (reddit)
- [SOLVED] - how to pin unpin a specific kernel? - Proxmox Support Forum (forum)
- [SOLVED] - Kernel pinning no effect | Proxmox Support Forum (forum)
- How to Pin a Machine to Proxmox 8.1 (or Any Previous Version)? (forum)
- Need help rolling back to previous kernel auto select during boot (reddit)
Collected 48 days ago - public community threads