Opt-in Linux 6.17 Kernel for Proxmox VE 9 available on test & no-subscription

  • Like
Reactions: jsterr
Had one issue today, but I'm not sure if its strictly related to the kernel. Had a windows 11 VM crash with a "Internal VM error". System logs showed the following. I restarted the windows 11 VM and so far so good. Screenshot 2025-10-14 at 8.01.57 PM.png
 
No issues with nvidia dkms drivers on 6.17:
No Issues with 6.17 and 580.82.07
No issues with 6.17 and 580.95.05

(Genoa 9374f + RTX 6000 96gb)

Code:
root@pve-bdr:~# apt install proxmox-headers-6.17
The following packages were automatically installed and are no longer required:
  proxmox-headers-6.14.11-2-pve  proxmox-headers-6.14.11-3-pve  proxmox-kernel-6.14.11-1-pve-signed
Use 'apt autoremove' to remove them.

Installing:
  proxmox-headers-6.17

Installing dependencies:
  proxmox-headers-6.17.1-1-pve

Summary:
  Upgrading: 0, Installing: 2, Removing: 0, Not Upgrading: 0
  Download size: 15.3 MB
  Space needed: 105 MB / 891 GB available

Continue? [Y/n] Y
Get:1 http://download.proxmox.com/debian/pve trixie/pve-no-subscription amd64 proxmox-headers-6.17.1-1-pve amd64 6.17.1-1 [15.3 MB]
Get:2 http://download.proxmox.com/debian/pve trixie/pve-no-subscription amd64 proxmox-headers-6.17 all 6.17.1-1 [11.1 kB]
Fetched 15.3 MB in 2s (9,621 kB/s)             
Selecting previously unselected package proxmox-headers-6.17.1-1-pve.
(Reading database ... 167573 files and directories currently installed.)
Preparing to unpack .../proxmox-headers-6.17.1-1-pve_6.17.1-1_amd64.deb ...
Unpacking proxmox-headers-6.17.1-1-pve (6.17.1-1) ...
Selecting previously unselected package proxmox-headers-6.17.
Preparing to unpack .../proxmox-headers-6.17_6.17.1-1_all.deb ...
Unpacking proxmox-headers-6.17 (6.17.1-1) ...
Setting up proxmox-headers-6.17.1-1-pve (6.17.1-1) ...
Setting up proxmox-headers-6.17 (6.17.1-1) ...
root@pve-bdr:~# apt install proxmox-kernel-6.17 proxmox-headers-6.17
proxmox-headers-6.17 is already the newest version (6.17.1-1).
The following packages were automatically installed and are no longer required:
  proxmox-headers-6.14.11-2-pve  proxmox-headers-6.14.11-3-pve  proxmox-kernel-6.14.11-1-pve-signed
Use 'apt autoremove' to remove them.

Installing:
  proxmox-kernel-6.17

Installing dependencies:
  proxmox-kernel-6.17.1-1-pve-signed

Summary:
  Upgrading: 0, Installing: 2, Removing: 0, Not Upgrading: 0
  Download size: 124 MB
  Space needed: 989 MB / 891 GB available

Get:1 http://download.proxmox.com/debian/pve trixie/pve-no-subscription amd64 proxmox-kernel-6.17.1-1-pve-signed amd64 6.17.1-1 [124 MB]
Get:2 http://download.proxmox.com/debian/pve trixie/pve-no-subscription amd64 proxmox-kernel-6.17 all 6.17.1-1 [11.4 kB]                 
Fetched 124 MB in 11s (10.8 MB/s)                                                                                                         
Selecting previously unselected package proxmox-kernel-6.17.1-1-pve-signed.
(Reading database ... 195241 files and directories currently installed.)
Preparing to unpack .../proxmox-kernel-6.17.1-1-pve-signed_6.17.1-1_amd64.deb ...
Unpacking proxmox-kernel-6.17.1-1-pve-signed (6.17.1-1) ...
Selecting previously unselected package proxmox-kernel-6.17.
Preparing to unpack .../proxmox-kernel-6.17_6.17.1-1_all.deb ...
Unpacking proxmox-kernel-6.17 (6.17.1-1) ...
Setting up proxmox-kernel-6.17.1-1-pve-signed (6.17.1-1) ...
Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/dkms 6.17.1-1-pve /boot/vmlinuz-6.17.1-1-pve
Sign command: /lib/modules/6.17.1-1-pve/build/scripts/sign-file
Signing key: /var/lib/dkms/mok.key
Public certificate (MOK): /var/lib/dkms/mok.pub

Autoinstall of module nvidia/580.82.07 for kernel 6.17.1-1-pve (x86_64)
Building module(s)........ done.
Signing module /var/lib/dkms/nvidia/580.82.07/build/nvidia.ko
Signing module /var/lib/dkms/nvidia/580.82.07/build/nvidia-modeset.ko
Signing module /var/lib/dkms/nvidia/580.82.07/build/nvidia-drm.ko
Signing module /var/lib/dkms/nvidia/580.82.07/build/nvidia-uvm.ko
Signing module /var/lib/dkms/nvidia/580.82.07/build/nvidia-peermem.ko
Installing /lib/modules/6.17.1-1-pve/updates/dkms/nvidia.ko
Installing /lib/modules/6.17.1-1-pve/updates/dkms/nvidia-modeset.ko
Installing /lib/modules/6.17.1-1-pve/updates/dkms/nvidia-drm.ko
Installing /lib/modules/6.17.1-1-pve/updates/dkms/nvidia-uvm.ko
Installing /lib/modules/6.17.1-1-pve/updates/dkms/nvidia-peermem.ko
Running depmod... done.

Autoinstall on 6.17.1-1-pve succeeded for module(s) nvidia.
run-parts: executing /etc/kernel/postinst.d/initramfs-tools 6.17.1-1-pve /boot/vmlinuz-6.17.1-1-pve
update-initramfs: Generating /boot/initrd.img-6.17.1-1-pve
Running hook script 'zz-proxmox-boot'..
Re-executing '/etc/kernel/postinst.d/zz-proxmox-boot' in new private mount namespace..
Copying and configuring kernels on /dev/disk/by-uuid/8674-D819
        Copying kernel and creating boot-entry for 6.14.11-2-pve
        Copying kernel and creating boot-entry for 6.14.11-4-pve
        Copying kernel and creating boot-entry for 6.17.1-1-pve
        Removing old version 6.14.11-3-pve
Copying and configuring kernels on /dev/disk/by-uuid/8695-C91A
        Copying kernel and creating boot-entry for 6.14.11-2-pve
        Copying kernel and creating boot-entry for 6.14.11-4-pve
        Copying kernel and creating boot-entry for 6.17.1-1-pve
        Removing old version 6.14.11-3-pve
run-parts: executing /etc/kernel/postinst.d/proxmox-auto-removal 6.17.1-1-pve /boot/vmlinuz-6.17.1-1-pve
run-parts: executing /etc/kernel/postinst.d/zz-proxmox-boot 6.17.1-1-pve /boot/vmlinuz-6.17.1-1-pve
Re-executing '/etc/kernel/postinst.d/zz-proxmox-boot' in new private mount namespace..
Copying and configuring kernels on /dev/disk/by-uuid/8674-D819
        Copying kernel and creating boot-entry for 6.14.11-2-pve
        Copying kernel and creating boot-entry for 6.14.11-4-pve
        Copying kernel and creating boot-entry for 6.17.1-1-pve
Copying and configuring kernels on /dev/disk/by-uuid/8695-C91A
        Copying kernel and creating boot-entry for 6.14.11-2-pve
        Copying kernel and creating boot-entry for 6.14.11-4-pve
        Copying kernel and creating boot-entry for 6.17.1-1-pve
run-parts: executing /etc/kernel/postinst.d/zz-update-grub 6.17.1-1-pve /boot/vmlinuz-6.17.1-1-pve
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-6.17.1-1-pve
Found initrd image: /boot/initrd.img-6.17.1-1-pve
/usr/sbin/grub-probe: error: unknown filesystem.
Found linux image: /boot/vmlinuz-6.14.11-4-pve
Found initrd image: /boot/initrd.img-6.14.11-4-pve
Found linux image: /boot/vmlinuz-6.14.11-3-pve
Found initrd image: /boot/initrd.img-6.14.11-3-pve
Found linux image: /boot/vmlinuz-6.14.11-2-pve
Found initrd image: /boot/initrd.img-6.14.11-2-pve
Found linux image: /boot/vmlinuz-6.14.11-1-pve
Found initrd image: /boot/initrd.img-6.14.11-1-pve
/usr/sbin/grub-probe: error: unknown filesystem.
Found memtest86+ 64bit EFI image: /boot/memtest86+x64.efi
Found memtest86+ 32bit EFI image: /boot/memtest86+ia32.efi
Found memtest86+ 64bit image: /boot/memtest86+x64.bin
Found memtest86+ 32bit image: /boot/memtest86+ia32.bin
Adding boot menu entry for UEFI Firmware Settings ...
done
Setting up proxmox-kernel-6.17 (6.17.1-1) ...

Code:
root@pve-bdr:~# nvidia-smi
Wed Oct 15 07:12:54 2025       
+-----------------------------------------------------------------------------------------+
| NVIDIA-SMI 580.95.05              Driver Version: 580.95.05      CUDA Version: 13.0     |
+-----------------------------------------+------------------------+----------------------+
| GPU  Name                 Persistence-M | Bus-Id          Disp.A | Volatile Uncorr. ECC |
| Fan  Temp   Perf          Pwr:Usage/Cap |           Memory-Usage | GPU-Util  Compute M. |
|                                         |                        |               MIG M. |
|=========================================+========================+======================|
|   0  NVIDIA RTX PRO 6000 Blac...    On  |   00000000:41:00.0 Off |                  Off |
| 30%   27C    P8              6W /  300W |       2MiB /  97887MiB |      0%      Default |
|                                         |                        |                  N/A |
+-----------------------------------------+------------------------+----------------------+

+-----------------------------------------------------------------------------------------+
| Processes:                                                                              |
|  GPU   GI   CI              PID   Type   Process name                        GPU Memory |
|        ID   ID                                                               Usage      |
|=========================================================================================|
|  No running processes found                                                             |
+-----------------------------------------------------------------------------------------+
root@pve-bdr:~# uname -a
Linux pve-bdr 6.17.1-1-pve #1 SMP PREEMPT_DYNAMIC PMX 6.17.1-1 (2025-10-06T16:20Z) x86_64 GNU/Linux
 
Hi,
Had one issue today, but I'm not sure if its strictly related to the kernel. Had a windows 11 VM crash with a "Internal VM error". System logs showed the following. I restarted the windows 11 VM and so far so good. View attachment 91673
please share the VM configuration qm config ID, the output of pveversion -v and the output of lscpu. Are the latest BIOS updates/CPU microcode installed? Anything additional in the surrounding system logs?
 
root@neptune:~# qm config 101
agent: 1,fstrim_cloned_disks=1
audio0: device=ich9-intel-hda,driver=spice
balloon: 0
bios: ovmf
boot: order=ide2;scsi0
cores: 6
cpu: x86-64-v3
cpuunits: 150
description: Running windows 11 with Only Office
efidisk0: sata-zfs:vm-101-disk-3,efitype=4m,pre-enrolled-keys=1,size=1M
hostpci0: mapping=B50-SRIOV,pcie=1,x-vga=1
ide2: none,media=cdrom
machine: pc-q35-9.0
memory: 12288
meta: creation-qemu=7.1.0,ctime=1671541357
name: Win-ThinServer
net0: virtio=2E:4B:05:74:1C:AF,bridge=vmbr1,firewall=1,queues=6,tag=5
numa: 0
onboot: 1
ostype: win11
scsi0: local-zfs:vm-101-disk-0,discard=on,iothread=1,size=85G,ssd=1
scsihw: virtio-scsi-single
smbios1: uuid=48d76fbb-0a05-4efc-a48e-e66402df1d80
sockets: 1
spice_enhancements: videostreaming=filter
startup: order=2,up=30,down=60
tablet: 0
tags: ThinClientVM;IOT
tpmstate0: sata-zfs:vm-101-disk-5,size=4M,version=v2.0
vga: qxl2
vmgenid: dd53ac36-3bb1-4017-ac1a-197c4166f202

root@neptune:~# pveversion -v
proxmox-ve: 9.0.0 (running kernel: 6.17.1-1-pve)
pve-manager: 9.0.11 (running version: 9.0.11/3bf5476b8a4699e2)
proxmox-kernel-helper: 9.0.4
proxmox-kernel-6.17.1-1-pve-signed: 6.17.1-1
proxmox-kernel-6.17: 6.17.1-1
proxmox-kernel-6.14.11-4-pve-signed: 6.14.11-4
proxmox-kernel-6.14: 6.14.11-4
proxmox-kernel-6.14.11-2-pve-signed: 6.14.11-2
proxmox-kernel-6.14.8-2-pve-signed: 6.14.8-2
amd64-microcode: 3.20250311.1
ceph-fuse: 19.2.3-pve2
corosync: 3.1.9-pve2
criu: 4.1.1-1
frr-pythontools: 10.3.1-1+pve4
ifupdown2: 3.3.0-1+pmx10
ksm-control-daemon: 1.5-1
libjs-extjs: 7.0.0-5
libproxmox-acme-perl: 1.7.0
libproxmox-backup-qemu0: 2.0.1
libproxmox-rs-perl: 0.4.1
libpve-access-control: 9.0.3
libpve-apiclient-perl: 3.4.0
libpve-cluster-api-perl: 9.0.6
libpve-cluster-perl: 9.0.6
libpve-common-perl: 9.0.11
libpve-guest-common-perl: 6.0.2
libpve-http-server-perl: 6.0.4
libpve-network-perl: 1.1.8
libpve-rs-perl: 0.10.10
libpve-storage-perl: 9.0.13
libspice-server1: 0.15.2-1+b1
lvm2: 2.03.31-2+pmx1
lxc-pve: 6.0.5-1
lxcfs: 6.0.4-pve1
novnc-pve: 1.6.0-3
proxmox-backup-client: 4.0.16-1
proxmox-backup-file-restore: 4.0.16-1
proxmox-backup-restore-image: 1.0.0
proxmox-firewall: 1.2.0
proxmox-kernel-helper: 9.0.4
proxmox-mail-forward: 1.0.2
proxmox-mini-journalreader: 1.6
proxmox-widget-toolkit: 5.0.6
pve-cluster: 9.0.6
pve-container: 6.0.13
pve-docs: 9.0.8
pve-edk2-firmware: 4.2025.02-4
pve-esxi-import-tools: 1.0.1
pve-firewall: 6.0.3
pve-firmware: 3.17-2
pve-ha-manager: 5.0.5
pve-i18n: 3.6.1
pve-qemu-kvm: 10.0.2-4
pve-xtermjs: 5.5.0-2
qemu-server: 9.0.23
smartmontools: 7.4-pve1
spiceterm: 3.4.1
swtpm: 0.8.0+pve2
vncterm: 1.9.1
zfsutils-linux: 2.3.4-pve1

Screenshot 2025-10-15 at 8.47.23 AM.png
Bios/system firmware is current. I looked in the logs for anything else that seemed relevant and around the time frame of the actual vm lockup most of the locks besides the snippet above were actually fairly quiet.
 
Last edited:
  • Like
Reactions: fiona
It does not work with NVIDIA vgpu drivers GRID 6.12 drivers, it fails to build. (grid 6.12 builds just fine with kernel 6.14). I know it isn't proxmox specific, just saving some people some time if they are running GRID drivers