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

推荐订阅源

T
Troy Hunt's Blog
GbyAI
GbyAI
博客园 - Franky
博客园 - 【当耐特】
U
Unit 42
Microsoft Security Blog
Microsoft Security Blog
Microsoft Azure Blog
Microsoft Azure Blog
阮一峰的网络日志
阮一峰的网络日志
P
Proofpoint News Feed
酷 壳 – CoolShell
酷 壳 – CoolShell
V
Visual Studio Blog
博客园 - 司徒正美
Blog — PlanetScale
Blog — PlanetScale
人人都是产品经理
人人都是产品经理
Threat Intelligence Blog | Flashpoint
Threat Intelligence Blog | Flashpoint
K
Kaspersky official blog
V
Vulnerabilities – Threatpost
P
Privacy & Cybersecurity Law Blog
V
V2EX
Google DeepMind News
Google DeepMind News
S
Securelist
A
About on SuperTechFans
Cisco Talos Blog
Cisco Talos Blog
T
The Exploit Database - CXSecurity.com
博客园 - 聂微东
T
The Blog of Author Tim Ferriss
T
Tor Project blog
C
Cybersecurity and Infrastructure Security Agency CISA
P
Proofpoint News Feed
The Hacker News
The Hacker News
P
Privacy International News Feed
罗磊的独立博客
N
Netflix TechBlog - Medium
cs.CL updates on arXiv.org
cs.CL updates on arXiv.org
I
Intezer
C
Check Point Blog
The Cloudflare Blog
Scott Helme
Scott Helme
P
Palo Alto Networks Blog
Y
Y Combinator Blog
Cyber Security Advisories - MS-ISAC
Cyber Security Advisories - MS-ISAC
L
Lohrmann on Cybersecurity
PCI Perspectives
PCI Perspectives
freeCodeCamp Programming Tutorials: Python, JavaScript, Git & More
Spread Privacy
Spread Privacy
Recent Commits to openclaw:main
Recent Commits to openclaw:main
大猫的无限游戏
大猫的无限游戏
C
CXSECURITY Database RSS Feed - CXSecurity.com
L
LINUX DO - 最新话题
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 ceph-osd crashes with kernel 6.17.2-1-pve on Dell system [META] Links on Proxmox Forum Website Hardwarer oder Software RAID Joining a cluster with already created guests VM PDM missing backup jobs from PVE / Log retention Remove VM.Monitor from all users/roles, PVE 9.2 Proxmox Freezing (new instalation) 9.2.2 - Intel 12700T No Web gui and random connection reset by peer [SOLVED] - i40e module for X710 Intel NIC Dutch Proxmox Day 2026 How pools use the space Corosync initiiert Reboot trotz Verfügbarkeit der Systeme Opt-in Linux 7.0 Kernel for Proxmox VE 9 available After PVE 8to9 upgrade, unable to check guest fs freeze status Problem with MegaRAID SAS3508 controller proxmox-kernel-7.0.2-6-pve failing network service Auto sync guest time after rollback of VM snapshot with RAM/state Broadcom BCM57504 (100G) bnxt_en TX timeout and NIC reset on Proxmox 8.1.5 — while BCM57414 (25G) works fine on same host QEMU 11.0 available on pve-test and pve-no-subscription as of now 350 MPM Solventless Lamination Machine for High-Speed Flexible Packaging Making sense of NVMe zfs and SMART errors [SOLVED] - PVE loses network connection after kernel upgrade to proxmox-kernel-7.0.0-3-pve [SOLVED] - Remove or reset cluster configuration. Proxmox 8.4.1 Fresh Install BCM57416 10G Ethernet Adapter Not Recognized PDM 1.1.1 unable to add AD realm with anonymous search [TUTORIAL] - Developer Workstation (Proxmox-VE 9) with cinnamon (LMDE7) SDN zone shows "pending" on peer nodes after node reboot (9.2.x) Cluster not quorate - extending auth key lifetime! Proxmox not rebooting properly (SOLVED) Proxmox 9 Stuck on loading initial ramdisk With new HA-Disarm Feature is there a Documentation for NUT Setup on Clusters? Proxmox 8.3 Installation Issue on ProLiant DL380 Gen9 Cluster networking setup LXC System images unavailable Install NUT directly on Proxmox VE and control guests from here driver usb for windows 7 System startup error and no network: Failed to start ifupdown2-pre.service - Helper to synchronize boot up for ifupdown. PBS backup space grow up constantly Proxmox Datacenter Manager 1.1 released! IPv4 not available in newly created VM Recommended Setup for Offsite Proxmox Backups? Hetzner Storage Box & Remote PBS Challenges duplicate, please delete this passthrought an USB device "by ID" to CT PDM Installer Freezes at 66% Tried PDM for the first time (version 1.1) - had issues PDM 1.1 automated install Suche Server-Provider für Proxmox connecting sdn to edge firewall SDN, IPAM & DHCP Migrating from read-only file system Ubuntu 26.04 installation fails for unknown reason Status Unbekannt nach Cluster Join Installing Proxmox Backup Server on Mac Mini (Late 2012) kernel 7.0 performance issue with zfs pools PVE becomes unreachable via ethernet but OS is running [SOLVED] - New 9.2 install - can't find 7.0.2-6-pve , not all the time [SOLVED] - Backup and dedupe a VM with LUKS Gibt es mit PVE 2.x ggf. Änderungen bei der RAM-Nutzung, bzw. deren Anzeige bei VMs? I need help for setting up backup solution Way more NAGware, very little functionality, bugs galore Root squashing virtiofsd with --uid-map Intel ixgbe Driver Update Fail Help to fix Proxmox access issues after power cut Passkey Login (not 2FA) Roblox VM detection - can be overcome? [TUTORIAL] - ZFS-Autosnaptshot inkl. Rollback und Daten direkt recovern (Windows/Linux) How to stop PVE Kernel upgrade [SOLVED] - very long waiting to log in to lxc debian 11 ssh [TUTORIAL] - Configuring Fusion-Io (SanDisk) ioDrive, ioDrive2, ioScale and ioScale2 cards with Proxmox Increase maximum USB devices in vm.conf
[SOLVED] - Fix: NVIDIA Drivers Failing after upgrade to Proxmox 9.2.2 (Kernel 7.0.2-6-pve) / NovaCore Conflict
invalid@exam · 2026-05-29 · via Proxmox Support Forum

I recently upgraded to Proxmox 9.2.2 and my NVIDIA drivers completely stopped working.

In the process of fixing this, post-upgrade. I found two issues.

  1. DKMS failed to rebuild driver for new kernel
    • I think this was my fault. I had previously installed headers for a specific kernel version using apt install pve-headers-$(uname -r). I should have probably used apt install pve-headers.
  2. The NovaCore module bound itself to the card before the nvidia driver/module could.

Code:

## journalctl (UI: Host > System > System Log) 
May 23 17:20:30 box kernel: NVRM: GPU 0000:65:00.0 is already bound to NovaCore.
May 23 17:20:30 box kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
May 23 17:20:30 box kernel: NVRM: This can occur when another driver was loaded and
NVRM: obtained ownership of the NVIDIA device(s).
May 23 17:20:30 box kernel: NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
  • For context, Nova is the new open-source, Rust-based kernel driver meant to replace Nouveau for modern (Turing/RTX 2000+) GPUs that use GSP firmware. It seems to essentially be the new nouveau.

Here is the fix that worked for me!

1. Validate your NVIDIA DKMS Module was built for your new kernel version
Check your installed driver and kernel version:

**If your DKMS status output indicates the driver is already built for your active kernel, Skip to Step 3.**

Code:

# example 1: DKMS Module built for current active kernel
root@box:~# dkms status && uname -r
nvidia/595.71.05, 7.0.2-6-pve, x86_64: installed
7.0.2-6-pve

# example 2:  DKMS Module NOT built for current active kernel
root@box:~# dkms status && uname -r
nvidia/595.71.05, 6.17.13-7-pve, x86_64: installed
7.0.2-6-pve

2. Rebuild the NVIDIA Module (DKMS)
Install the headers for the new kernel so DKMS can compile the driver.

Bash:

apt update
apt install pve-headers-$(uname -r)

Force DKMS to rebuild and install the module for the new kernel

Bash:

# example for a card with nvidia driver 595.71.05 ('dkms status' output) on kernel 7.0.2-6-pve ('uname -r' output)
dkms install -m nvidia -v 595.71.05 -k 7.0.2-6-pve

3. Blacklist the NovaCore Driver
To prevent NovaCore from taking control of the GPU during early boot, you need to blacklist it.

If you already have a blacklist entry in one of your /etc/modprobe.d/ files for nouveau, just add the lines specific to nova/nova_core.

Bash:

echo "blacklist nova" >> /etc/modprobe.d/blacklist.conf
echo "blacklist nova_core" >> /etc/modprobe.d/blacklist.conf
echo "options nova modeset=0" >> /etc/modprobe.d/blacklist.conf
echo "blacklist nouveau" >> /etc/modprobe.d/blacklist.conf
echo "options nouveau modeset=0" >> /etc/modprobe.d/blacklist.conf

4. Update Initramfs and Reboot
Finally, rebuild your initial ramdisk so the blacklist applies during the boot sequence, and restart the host.

Bash:

update-initramfs -u -k all
reboot

5. Validate fix
Once the host comes back online, run nvidia-smi, it should be back to normal!

EDIT: intramfs command
EDIT2: Updated blacklist location from nvidia.conf to a generic blacklist.conf file. Aligns with proxmox official blacklist instructions & prevents revert of blacklist during nvidia driver upgrade.
EDIT3: Added a snippet from my host's journalctl that pointed to NovaCore being the issue

Last edited:

I generally recommend these commands

Bash:

apt install -y proxmox-default-headers proxmox-headers-$(uname -r) gcc make dkms

Reason being that proxmox-headers-$(uname -r) takes care of the current kernel (think pinned/not yet rebooted) and proxmox-default-headers is a meta package that targets the newest one so no future headaches.
Same reason why I'd recommend update-initramfs -ukall to update the initramfs for all kernels. dpkg-reconfigure nvidia-kernel-dkms should force a rebuild as well.
I haven't heard of nova_core before but the NVIDIA driver packages usually ship with a noveau blacklist already.

Ahh, that makes sense. edited the post with the updated intramfs command!

In regards to nova, it's a relatively new addition to the linux kernel. There were some articles on its inclusion into the 7.0 kernel as the successor to noveau.

I had the noveau blacklist entry, but I think nova was enabled automatically upon upgrading to the new pve version (which includes the 7.0+ linux kernel).

That rendered the noveau blacklist entry in modprobe useless, which blocked the nvidia driver from loading until the new nova specific blacklist entries were added.

Hi

Thank you for the information.

Could you please let me know where you obtained the NVIDIA driver version 595.71.05 for 7.0.2-6-pve x86_64?

On the NVIDIA website, the latest package I can find is:

Complete vGPU 19.4 package for Linux KVM including supported guest drivers
vGPU 19.4

I cannot find the driver version 595.71.05 there. Could you please point me to the correct download source or let me know if this driver comes from another package or repository?

Thank you very much for your help.

Hi!​

Thank you for your guide!​

Unfortunately this didnt work in our environment :/​

I have setup a fresh install with PVE 9.1.1 (which has the Kernel 6.17) I have have setup everything according to the guide of Proxmox themselves and everything worked great.​

Until I decided to upgrade to PVE 9.2.2, which comes with the new Kernel 7.0 and as soon as I did that, the server would run into a Kernel Panic.​

So I googled and found this article and thought I give it a try, but no chance it just simply doesnt want run under Linux Kernel 7.​

When I boot into Rescue Mode, the NVIDIA driver cant even see the GPU's.​

So then I went back to Kernel 6.17, pinned it and then it worked like a charm.​

Any ideas?​

Please let me know if you have any further questions or if I haven't made myself clear :)

Specs of the Server are down below.​

------------------------------------------------------------------------------------------------------------------------------------------​

CPU:​

2x Intel XEON GOLD 6544Y​

Mainboard:​

Supermicro X13DEI-T-B​

RAM:​

16x Samsung M321R8GA0PB0-CWMCJ 64GB DDR5 5200MT/s​

GPU:​

2x NVIDIA RTX 6000 ADA​

Hi!​

Thank you for your guide!​

Unfortunately this didnt work in our environment :/​

I have setup a fresh install with PVE 9.1.1 (which has the Kernel 6.17) I have have setup everything according to the guide of Proxmox themselves and everything worked great.​

Until I decided to upgrade to PVE 9.2.2, which comes with the new Kernel 7.0 and as soon as I did that, the server would run into a Kernel Panic.​

So I googled and found this article and thought I give it a try, but no chance it just simply doesnt want run under Linux Kernel 7.​

When I boot into Rescue Mode, the NVIDIA driver cant even see the GPU's.​

So then I went back to Kernel 6.17, pinned it and then it worked like a charm.​

Any ideas?​

Please let me know if you have any further questions or if I haven't made myself clear :)

Specs of the Server are down below.​

------------------------------------------------------------------------------------------------------------------------------------------​

CPU:​

2x Intel XEON GOLD 6544Y​

Mainboard:​

Supermicro X13DEI-T-B​

RAM:​

16x Samsung M321R8GA0PB0-CWMCJ 64GB DDR5 5200MT/s​

GPU:​

2x NVIDIA RTX 6000 ADA​

I have upgrade to nvidia 610.43.02 driver and it's work. I use nvidia-open

nvidia doc

Hi

Thank you for the information.

Could you please let me know where you obtained the NVIDIA driver version 595.71.05 for 7.0.2-6-pve x86_64?

On the NVIDIA website, the latest package I can find is:

Complete vGPU 19.4 package for Linux KVM including supported guest drivers
vGPU 19.4

I cannot find the driver version 595.71.05 there. Could you please point me to the correct download source or let me know if this driver comes from another package or repository?

Thank you very much for your help.

The latest nvidia driver you'll see via apt depends on where you have apt configured to look for drivers.

By default debian (13) will not show any proprietary nvidia drivers via apt,

  • If you have added non-free non-free-firmware to /etc/apt/sources/debian.sources, you will see nvidia-drivers post apt update, though these will very likely not be the latest drivers.
    • The default debian distro package repository's can lag months behind the official nvidia repository
  • If you have apt configured to source drivers from the official nvidia repository, you will see the latest drivers.
    • Subject to change, but the basic flow is.
      • From Nvidia's official repo, Download the latest cuda-keyringpackage
        • For PVE 9 that should be under debian13/x86_64/
      • install it with dpkg -i [the file you downloaded].deb
      • apt update

For more involved steps on installing the latest nvidia cuda drivers on your host, my recommendation is to follow this guide's "Proxmox Host" section. Nvidia also has a guide but it can be a bit tough to follow.

Last edited:

Hi!​

Thank you for your guide!​

Unfortunately this didnt work in our environment :/​

I have setup a fresh install with PVE 9.1.1 (which has the Kernel 6.17) I have have setup everything according to the guide of Proxmox themselves and everything worked great.​

Until I decided to upgrade to PVE 9.2.2, which comes with the new Kernel 7.0 and as soon as I did that, the server would run into a Kernel Panic.​

So I googled and found this article and thought I give it a try, but no chance it just simply doesnt want run under Linux Kernel 7.​

When I boot into Rescue Mode, the NVIDIA driver cant even see the GPU's.​

So then I went back to Kernel 6.17, pinned it and then it worked like a charm.​

Any ideas?​

Please let me know if you have any further questions or if I haven't made myself clear :)

Specs of the Server are down below.​

------------------------------------------------------------------------------------------------------------------------------------------​

CPU:​

2x Intel XEON GOLD 6544Y​

Mainboard:​

Supermicro X13DEI-T-B​

RAM:​

16x Samsung M321R8GA0PB0-CWMCJ 64GB DDR5 5200MT/s​

GPU:​

2x NVIDIA RTX 6000 ADA​

Given this seems like a relatively new install on enterprise hw and likely your first kernel upgrade... Are you using SecureBoot by chance? This might be a case of mok/dkms not signing the new kernel modules with your signing key. If so, this article might help you out!

Either way I would recommend checking your journalctl / dmesg output. It may give you some hints as to what's causing your issue.

Is VGPU Working with this setup? (before i try to install :-D) ... Thx

Is VGPU Working with this setup? (before i try to install :-D) ... Thx

I don't have any vGPU capable GPU's in my lab so outside of giving you the link to the official proxmox vGPU support matrix... I couldn't give you any insight on that.

I'm virtualizing using "less than" privleged LXC's.

If you have a spare GPU that supports it, send it my way. Happy to test it on your behalf! ;D

Last edited:

Given this seems like a relatively new install on enterprise hw and likely your first kernel upgrade... Are you using SecureBoot by chance? This might be a case of mok/dkms not signing the new kernel modules with your signing key. If so, this article might help you out!

Either way I would recommend checking your journalctl / dmesg output. It may give you some hints as to what's causing your issue.

Nope, Secure Boot has been deactivated the whole time.

In the meantime I have opened a Support Ticket with Proxmox, in hopes that they know what to da :D

Howdy,

Thank you for your detailed steps.

I am having an issue that I believe is related to what's been discussed here. Full disclosure, I'm a simple homelab hobbyist and this issue is rapidly getting above my experience level. I am presently on kernel 6.17.13-8-pve and my goal is to upgrade to the new 7.0 kernel. I started the upgrade using the webGUI method. After the upgrades complete and the system reboots I run into the kernel panic issue. Finding this post I attempted the instructions for installing the new kernel via the terminal:

Code:

#apt install proxmox-kernel-7.0
Continue? [Y/n] y

Autoinstall of module nvidia/580.105.08 for kernel 7.0.6-2-pve (x86_64)
Building module(s).......(bad exit status: 2)
Failed command:
'make' -j32 NV_EXCLUDE_BUILD_MODULES='' KERNEL_UNAME=7.0.6-2-pve modules

Error! Bad return status for module build on kernel: 7.0.6-2-pve (x86_64)
Consult /var/lib/dkms/nvidia/580.105.08/build/make.log for more information.

Autoinstall on 7.0.6-2-pve failed for module(s) nvidia(10).

Error! One or more modules failed to install during autoinstall.
Refer to previous errors for more information.
run-parts: /etc/kernel/postinst.d/dkms exited with return code 1
Failed to process /etc/kernel/postinst.d at /var/lib/dpkg/info/proxmox-kernel-7.0.6-2-pve-signed.postinst line 20.
dpkg: error processing package proxmox-kernel-7.0.6-2-pve-signed (--configure):
 installed proxmox-kernel-7.0.6-2-pve-signed package post-installation script subprocess returned error exit status 2

dpkg: dependency problems prevent configuration of proxmox-kernel-7.0:
 proxmox-kernel-7.0 depends on proxmox-kernel-7.0.6-2-pve-signed | proxmox-kernel-7.0.6-2-pve; however:
  Package proxmox-kernel-7.0.6-2-pve-signed is not configured yet.
  Package proxmox-kernel-7.0.6-2-pve is not installed.
  Package proxmox-kernel-7.0.6-2-pve-signed which provides proxmox-kernel-7.0.6-2-pve is not configured yet.

dpkg: error processing package proxmox-kernel-7.0 (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of proxmox-default-kernel:
 proxmox-default-kernel depends on proxmox-kernel-7.0; however:
  Package proxmox-kernel-7.0 is not configured yet.

dpkg: error processing package proxmox-default-kernel (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of proxmox-ve:
 proxmox-ve depends on proxmox-default-kernel; however:
  Package proxmox-default-kernel is not configured yet.

dpkg: error processing package proxmox-ve (--configure):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 proxmox-kernel-7.0.6-2-pve-signed
 proxmox-kernel-7.0.2-3-pve-signed
 proxmox-kernel-7.0.0-3-pve-signed
 proxmox-kernel-7.0
 proxmox-default-kernel
 proxmox-ve
Error: Sub-process /usr/bin/dpkg returned an error code (1)

These outputs make me think the nvidia drivers are what is preventing the new kernel from installing, but I am uncertain. I have reviewed the log located at /var/lib/dkms/nvidia/580.105.08/build/make.log, but i am unsure what to make of it, I will attach it if requested. Digging through my journalctl entries, I don't believe my environment is using NovaCore.

Here are the results when I repeat your steps:

Code:

# dkms status
nvidia/580.105.08, 6.17.13-1-pve, x86_64: installed
nvidia/580.105.08, 6.17.13-2-pve, x86_64: installed
nvidia/580.105.08, 6.17.13-6-pve, x86_64: installed
nvidia/580.105.08, 6.17.13-8-pve, x86_64: installed
nvidia/580.105.08, 6.17.2-2-pve, x86_64: installed
nvidia/580.105.08, 6.17.4-1-pve, x86_64: installed
nvidia/580.105.08, 6.17.4-2-pve, x86_64: installed

# uname -r
6.17.13-8-pve

Even though I have matching entries, I opted to follow through with step 2, and when attempting to install the pve-headers, I get the same array of error messages as above. When trying to reinstall the module for the new kernel, I'm not successful either.

Code:

# dkms install -m nvidia -v 580.105.08 -k 7.0.2-6-pve

Error! Your kernel headers for kernel 7.0.2-6-pve cannot be found at /lib/modules/7.0.2-6-pve/build or /lib/modules/7.0.2-6-pve/source.
Please install the linux-headers-7.0.2-6-pve package or use the --kernelsourcedir option to tell DKMS where it's located.

I made the blacklist changes:

Code:

# cat /etc/modprobe.d/blacklist.conf
blacklist nouveau
blacklist nvidia
blacklist i915
blacklist xe
blacklist nova
blacklist nova_core
options nova modeset=0
options nouveau modeset=0

And this is the output from the initramfs command:

Code:

# update-initramfs -u -k all
update-initramfs: Generating /boot/initrd.img-6.17.13-8-pve
Running hook script 'zz-proxmox-boot'..
Re-executing '/etc/kernel/postinst.d/zz-proxmox-boot' in new private mount namespace..
No /etc/kernel/proxmox-boot-uuids found, skipping ESP sync.
update-initramfs: Generating /boot/initrd.img-6.17.13-6-pve
Running hook script 'zz-proxmox-boot'..
Re-executing '/etc/kernel/postinst.d/zz-proxmox-boot' in new private mount namespace..
No /etc/kernel/proxmox-boot-uuids found, skipping ESP sync.
update-initramfs: Generating /boot/initrd.img-6.17.13-2-pve
Running hook script 'zz-proxmox-boot'..
Re-executing '/etc/kernel/postinst.d/zz-proxmox-boot' in new private mount namespace..
No /etc/kernel/proxmox-boot-uuids found, skipping ESP sync.
update-initramfs: Generating /boot/initrd.img-6.17.13-1-pve
Running hook script 'zz-proxmox-boot'..
Re-executing '/etc/kernel/postinst.d/zz-proxmox-boot' in new private mount namespace..
No /etc/kernel/proxmox-boot-uuids found, skipping ESP sync.
update-initramfs: Generating /boot/initrd.img-6.17.4-2-pve
Running hook script 'zz-proxmox-boot'..
Re-executing '/etc/kernel/postinst.d/zz-proxmox-boot' in new private mount namespace..
No /etc/kernel/proxmox-boot-uuids found, skipping ESP sync.
update-initramfs: Generating /boot/initrd.img-6.17.4-1-pve
Running hook script 'zz-proxmox-boot'..
Re-executing '/etc/kernel/postinst.d/zz-proxmox-boot' in new private mount namespace..
No /etc/kernel/proxmox-boot-uuids found, skipping ESP sync.
update-initramfs: Generating /boot/initrd.img-6.17.2-2-pve
Running hook script 'zz-proxmox-boot'..
Re-executing '/etc/kernel/postinst.d/zz-proxmox-boot' in new private mount namespace..
No /etc/kernel/proxmox-boot-uuids found, skipping ESP sync.

Since 7.0.2-6 isn't listed in any of these outputs, I suspect this command has done nothing productive at this point.
I'm sure there's something obviously wrong that I'm doing, but it's not obvious to me. Any insights y'all could provide would be greatly appreciated.

Howdy,

Thank you for your detailed steps.

I am having an issue that I believe is related to what's been discussed here. Full disclosure, I'm a simple homelab hobbyist and this issue is rapidly getting above my experience level. I am presently on kernel 6.17.13-8-pve and my goal is to upgrade to the new 7.0 kernel. I started the upgrade using the webGUI method. After the upgrades complete and the system reboots I run into the kernel panic issue. Finding this post I attempted the instructions for installing the new kernel via the terminal:

Code:

#apt install proxmox-kernel-7.0
Continue? [Y/n] y

Autoinstall of module nvidia/580.105.08 for kernel 7.0.6-2-pve (x86_64)
Building module(s).......(bad exit status: 2)
Failed command:
'make' -j32 NV_EXCLUDE_BUILD_MODULES='' KERNEL_UNAME=7.0.6-2-pve modules

Error! Bad return status for module build on kernel: 7.0.6-2-pve (x86_64)
Consult /var/lib/dkms/nvidia/580.105.08/build/make.log for more information.

Autoinstall on 7.0.6-2-pve failed for module(s) nvidia(10).

Error! One or more modules failed to install during autoinstall.
Refer to previous errors for more information.
run-parts: /etc/kernel/postinst.d/dkms exited with return code 1
Failed to process /etc/kernel/postinst.d at /var/lib/dpkg/info/proxmox-kernel-7.0.6-2-pve-signed.postinst line 20.
dpkg: error processing package proxmox-kernel-7.0.6-2-pve-signed (--configure):
 installed proxmox-kernel-7.0.6-2-pve-signed package post-installation script subprocess returned error exit status 2

dpkg: dependency problems prevent configuration of proxmox-kernel-7.0:
 proxmox-kernel-7.0 depends on proxmox-kernel-7.0.6-2-pve-signed | proxmox-kernel-7.0.6-2-pve; however:
  Package proxmox-kernel-7.0.6-2-pve-signed is not configured yet.
  Package proxmox-kernel-7.0.6-2-pve is not installed.
  Package proxmox-kernel-7.0.6-2-pve-signed which provides proxmox-kernel-7.0.6-2-pve is not configured yet.

dpkg: error processing package proxmox-kernel-7.0 (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of proxmox-default-kernel:
 proxmox-default-kernel depends on proxmox-kernel-7.0; however:
  Package proxmox-kernel-7.0 is not configured yet.

dpkg: error processing package proxmox-default-kernel (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of proxmox-ve:
 proxmox-ve depends on proxmox-default-kernel; however:
  Package proxmox-default-kernel is not configured yet.

dpkg: error processing package proxmox-ve (--configure):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 proxmox-kernel-7.0.6-2-pve-signed
 proxmox-kernel-7.0.2-3-pve-signed
 proxmox-kernel-7.0.0-3-pve-signed
 proxmox-kernel-7.0
 proxmox-default-kernel
 proxmox-ve
Error: Sub-process /usr/bin/dpkg returned an error code (1)

These outputs make me think the nvidia drivers are what is preventing the new kernel from installing, but I am uncertain. I have reviewed the log located at /var/lib/dkms/nvidia/580.105.08/build/make.log, but i am unsure what to make of it, I will attach it if requested. Digging through my journalctl entries, I don't believe my environment is using NovaCore.

Here are the results when I repeat your steps:

Code:

# dkms status
nvidia/580.105.08, 6.17.13-1-pve, x86_64: installed
nvidia/580.105.08, 6.17.13-2-pve, x86_64: installed
nvidia/580.105.08, 6.17.13-6-pve, x86_64: installed
nvidia/580.105.08, 6.17.13-8-pve, x86_64: installed
nvidia/580.105.08, 6.17.2-2-pve, x86_64: installed
nvidia/580.105.08, 6.17.4-1-pve, x86_64: installed
nvidia/580.105.08, 6.17.4-2-pve, x86_64: installed

# uname -r
6.17.13-8-pve

Even though I have matching entries, I opted to follow through with step 2, and when attempting to install the pve-headers, I get the same array of error messages as above. When trying to reinstall the module for the new kernel, I'm not successful either.

Code:

# dkms install -m nvidia -v 580.105.08 -k 7.0.2-6-pve

Error! Your kernel headers for kernel 7.0.2-6-pve cannot be found at /lib/modules/7.0.2-6-pve/build or /lib/modules/7.0.2-6-pve/source.
Please install the linux-headers-7.0.2-6-pve package or use the --kernelsourcedir option to tell DKMS where it's located.

I made the blacklist changes:

Code:

# cat /etc/modprobe.d/blacklist.conf
blacklist nouveau
blacklist nvidia
blacklist i915
blacklist xe
blacklist nova
blacklist nova_core
options nova modeset=0
options nouveau modeset=0

And this is the output from the initramfs command:

Code:

# update-initramfs -u -k all
update-initramfs: Generating /boot/initrd.img-6.17.13-8-pve
Running hook script 'zz-proxmox-boot'..
Re-executing '/etc/kernel/postinst.d/zz-proxmox-boot' in new private mount namespace..
No /etc/kernel/proxmox-boot-uuids found, skipping ESP sync.
update-initramfs: Generating /boot/initrd.img-6.17.13-6-pve
Running hook script 'zz-proxmox-boot'..
Re-executing '/etc/kernel/postinst.d/zz-proxmox-boot' in new private mount namespace..
No /etc/kernel/proxmox-boot-uuids found, skipping ESP sync.
update-initramfs: Generating /boot/initrd.img-6.17.13-2-pve
Running hook script 'zz-proxmox-boot'..
Re-executing '/etc/kernel/postinst.d/zz-proxmox-boot' in new private mount namespace..
No /etc/kernel/proxmox-boot-uuids found, skipping ESP sync.
update-initramfs: Generating /boot/initrd.img-6.17.13-1-pve
Running hook script 'zz-proxmox-boot'..
Re-executing '/etc/kernel/postinst.d/zz-proxmox-boot' in new private mount namespace..
No /etc/kernel/proxmox-boot-uuids found, skipping ESP sync.
update-initramfs: Generating /boot/initrd.img-6.17.4-2-pve
Running hook script 'zz-proxmox-boot'..
Re-executing '/etc/kernel/postinst.d/zz-proxmox-boot' in new private mount namespace..
No /etc/kernel/proxmox-boot-uuids found, skipping ESP sync.
update-initramfs: Generating /boot/initrd.img-6.17.4-1-pve
Running hook script 'zz-proxmox-boot'..
Re-executing '/etc/kernel/postinst.d/zz-proxmox-boot' in new private mount namespace..
No /etc/kernel/proxmox-boot-uuids found, skipping ESP sync.
update-initramfs: Generating /boot/initrd.img-6.17.2-2-pve
Running hook script 'zz-proxmox-boot'..
Re-executing '/etc/kernel/postinst.d/zz-proxmox-boot' in new private mount namespace..
No /etc/kernel/proxmox-boot-uuids found, skipping ESP sync.

Since 7.0.2-6 isn't listed in any of these outputs, I suspect this command has done nothing productive at this point.
I'm sure there's something obviously wrong that I'm doing, but it's not obvious to me. Any insights y'all could provide would be greatly appreciated.

I was a little hasty and jumped to conclusions. In a nutshell I was correct about the nvidia drivers preventing the kernel upgrade. I simply had to uninstall the Nvidia driver, then the kernel upgrade proceeded without issue. I simply reinstalled the nvidia drivers following the upgrade.