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

推荐订阅源

钛媒体:引领未来商业与生活新知
钛媒体:引领未来商业与生活新知
U
Unit 42
GbyAI
GbyAI
M
MIT News - Artificial intelligence
美团技术团队
罗磊的独立博客
雷峰网
雷峰网
量子位
博客园 - 【当耐特】
Last Week in AI
Last Week in AI
D
Docker
小众软件
小众软件
S
SegmentFault 最新的问题
Blog — PlanetScale
Blog — PlanetScale
阮一峰的网络日志
阮一峰的网络日志
宝玉的分享
宝玉的分享
T
Tailwind CSS Blog
WordPress大学
WordPress大学
V
V2EX
博客园_首页
腾讯CDC
The Cloudflare Blog
A
About on SuperTechFans
Cyber Security Advisories - MS-ISAC
Cyber Security Advisories - MS-ISAC

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
PVE 8 - Kernel 6.8.12-29 Issue
invalid@exam · 2026-06-17 · via Proxmox Support Forum

I've been running PVE 8 for quite a while and have kept my system up to date without issue until now. Tonight when I ran apt upgrade, it installed a new kernel version 6.8.12-29-pve and after reboot my management NIC would not connect, and my pfSense VM with 5 passed through NICs would not start.

I pulled the logs and found the below:

I could see the console, but attempting to login it would just freeze, and never ask for my password. The last item in the log was

Jun 10 21:11:20 pve systemd-journald[400]: Time spent on flushing to /var/log/journal/a2efdef8ee09453d933200b5aa21cbaa is 24.247ms for 998 entries.
I used proxmox-boot-tool to list the other kernels and I had 6.8.12-24 still installed so I chose that and it started up again without issue. I then tried 6.8.12-29 again and the system failed to let me login, failed to connect my management NIC and failed to start my pfSense VM.

I've pinned the old kernel version for now. Is there an issue with this -29 kernel version?

I pasted the start of my log and end of my log below. Full log at https://pastebin.com/AaTRX2aE

Code:

Jun 10 21:11:20 pve kernel: Linux version 6.8.12-29-pve (build@proxmox) (gcc (Debian 12.2.0-14+deb12u1) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40) #1 SMP PREEMPT_DYNAMIC PMX 6.8.12-29 (2026-05-29T17:48Z) ()
Jun 10 21:11:20 pve kernel: Command line: initrd=\EFI\proxmox\6.8.12-29-pve\initrd.img-6.8.12-29-pve root=ZFS=rpool/ROOT/pve-1 boot=zfs quiet intel_iommu=on iommu=pt
Jun 10 21:11:20 pve kernel: KERNEL supported cpus:
Jun 10 21:11:20 pve kernel:   Intel GenuineIntel
Jun 10 21:11:20 pve kernel:   AMD AuthenticAMD
Jun 10 21:11:20 pve kernel:   Hygon HygonGenuine
Jun 10 21:11:20 pve kernel:   Centaur CentaurHauls
Jun 10 21:11:20 pve kernel:   zhaoxin   Shanghai 
Jun 10 21:11:20 pve kernel: x86/split lock detection: #AC: crashing the kernel on kernel split_locks and warning on user-space split_locks

Jun 10 21:11:20 pve kernel: Kernel command line: initrd=\EFI\proxmox\6.8.12-29-pve\initrd.img-6.8.12-29-pve root=ZFS=rpool/ROOT/pve-1 boot=zfs quiet intel_iommu=on iommu=pt
Jun 10 21:11:20 pve kernel: DMAR: IOMMU enabled
Jun 10 21:11:20 pve kernel: Unknown kernel command line parameters "boot=zfs", will be passed to user space.

Jun 10 21:11:20 pve systemd-journald[400]: Journal started
Jun 10 21:11:20 pve systemd-journald[400]: Runtime Journal (/run/log/journal/a2efdef8ee09453d933200b5aa21cbaa) is 8.0M, max 318.7M, 310.7M free.
Jun 10 21:11:20 pve systemd-modules-load[401]: Inserted module 'vfio'
Jun 10 21:11:20 pve systemd-modules-load[401]: Inserted module 'vfio_pci'
Jun 10 21:11:20 pve systemd-modules-load[401]: Failed to find module 'vfio_virqfd'
Jun 10 21:11:20 pve systemd-modules-load[401]: Inserted module 'vhost_net'
Jun 10 21:11:20 pve systemd[1]: Finished systemd-sysctl.service - Apply Kernel Variables.
Jun 10 21:11:20 pve systemd: Started systemd-journald.service - Journal Service.
Jun 10 21:11:20 pve systemd[1]: Starting systemd-journal-flush.service - Flush Journal to Persistent Storage...
Jun 10 21:11:20 pve systemd[1]: Finished systemd-tmpfiles-setup-dev.service - Create Static Device Nodes in /dev.
Jun 10 21:11:20 pve systemd[1]: Reached target local-fs-pre.target - Preparation for Local File Systems.
Jun 10 21:11:20 pve systemd[1]: Set up automount mnt-backups.automount.
Jun 10 21:11:20 pve systemd[1]: Starting systemd-udevd.service - Rule-based Manager for Device Events and Files...
Jun 10 21:11:20 pve systemd-journald[400]: Time spent on flushing to /var/log/journal/a2efdef8ee09453d933200b5aa21cbaa is 24.247ms for 998 entries.
-- Reboot --

fabian

Proxmox Staff Member

Staff member

Jan 7, 2016
13,087
3,884
303

I was on 24, I jumped to 29 during the update. I just tried 28.1 and it worked so definitely the 29 version. I'm pinning 28.1 now and I guess I just wait till 30 is released?

hmm I read in the bug reports above that 24 was the previous kernel but looking at the repo I saw 28.1. Now that I've installed and pinned that I still have 24 installed but it is not shown in proxmox-boot-tool. Have I broken something now?

Code:

root@pve:~# proxmox-boot-tool kernel list
Manually selected kernels:
None.

Automatically selected kernels:
6.5.13-6-pve
6.8.12-28.1-pve
6.8.12-29-pve

Pinned kernel:
6.8.12-28.1-pve
root@pve:~#

How do I get version 24 back in the list as I already have the package installed?

fabian

Proxmox Staff Member

Staff member

Jan 7, 2016
13,087
3,884
303

if 28.1 works, use that, it contains more security fixes. proxmox-boot-tool will only pick the last N versions per series, you can add more with `proxmox-boot-tool kernel add ..`

Kernel 6.8.12-30 solved the problem for me. Came out yesterday.

Last edited: