Proxmox (as a company) - what the HELL are you doing? Kernel update to 7 broke networking IN A VM

K

Kingneutron

Renowned Member
Feb 21, 2024
1,243
478
93
github.com
I use PDM and noticed a kernel upgrade available to 7.0 for my 3x PBS VMs. Upgraded (1) and rebooted it. Should be simple, right?

NO NETWORK after reboot. WTF?

This is my time off work for homelab maint, I'm not gonna try and troubleshoot that dumpster fire. Restored the VM from backup and all is fine now. If I have to pin the kernel to 6.17 I will.

But come on - if you guys want to be taken seriously as an Enterprise-level solution, DO NOT RELEASE BREAKING UPDATES!! I am not your beta tester, I rely on this stuff to be reliable to upgrade, even for homelab! Debian is supposed to be SIMPLE!

My $DAYJOB boss is having me evaluate Proxmox and PBS as a possible side-by-side solution for our Vmware ESXI stuff. There is NO WAY I can recommend going forward with proxmox at work if this kind of stuff keeps happening with what should be a run-of-the-mill upgrade process.

Please tell your devs to get their s--t together. Thank God I did this at home first instead of at work, your obviously untested rev would have made me look bad. I have been paying out of my own pocket for a support license for 2 years now, but this kind of breakage happening again would make me seriously rethink supporting proxmox going forward.

As an aside, this event made me rethink my backup strategy. I had been backing up my 3x PBS VMs about twice a week to other PBS VMs. If all 3 PBS instances had gone down at once after a simple upgrade... I have now scheduled .tar backups daily to local storage so I always have something to restore.
 
7.0 is a test kernel,not an enterprise kernel atm, so if you are okay with breakages you use this kernel. If not, you usually pay for enterprise subscription.
Why would you be angry on a company giving you a test repo?
 
Kingneutron said:
I use PDM and noticed a kernel upgrade available to 7.0 for my 3x PBS VMs. Upgraded (1) and rebooted it. Should be simple, right?

NO NETWORK after reboot. WTF?

This is my time off work for homelab maint, I'm not gonna try and troubleshoot that dumpster fire. Restored the VM from backup and all is fine now. If I have to pin the kernel to 6.17 I will.

But come on - if you guys want to be taken seriously as an Enterprise-level solution, DO NOT RELEASE BREAKING UPDATES!! I am not your beta tester, I rely on this stuff to be reliable to upgrade, even for homelab! Debian is supposed to be SIMPLE!

My $DAYJOB boss is having me evaluate Proxmox and PBS as a possible side-by-side solution for our Vmware ESXI stuff. There is NO WAY I can recommend going forward with proxmox at work if this kind of stuff keeps happening with what should be a run-of-the-mill upgrade process.

Please tell your devs to get their s--t together. Thank God I did this at home first instead of at work, your obviously untested rev would have made me look bad. I have been paying out of my own pocket for a support license for 2 years now, but this kind of breakage happening again would make me seriously rethink supporting proxmox going forward.

As an aside, this event made me rethink my backup strategy. I had been backing up my 3x PBS VMs about twice a week to other PBS VMs. If all 3 PBS instances had gone down at once after a simple upgrade... I have now scheduled .tar backups daily to local storage so I always have something to restore.
Click to expand...
Seriously? Did you even try to understand what you were doing with this? 7.0 is not production release code. This was self inflicted unfortunately. I would suggest starting over after reading some basic installation materials and stick with 6.x code until 7 is ready for production.

So yes, if you are using kernel 7, you are a beta tester lol.
 
No. I think it’s fair to voice my concerns here.

Anyone other than subscribers could be affected.

This is an opt-in feature, but it is located in the no-subscription repository rather than the test repository.

if it really was a kernel issue, he was the victim.

*Since I haven’t encountered the issue myself, I can’t say for sure without knowing the cause.

t.lamprecht

Thread 'Opt-in Linux 7.0 Kernel for Proxmox VE 9 available on test and no-subscription'

We recently uploaded the 7.0 (rc6) kernel to our repositories. The current default kernel for the Proxmox VE 9 series is still 6.17, but 7.0 is now an option.

We plan to use the 7.0 kernel as the new default for the upcoming Proxmox VE 9.2 and Proxmox Backup Server 4.2 releases planned later in Q2.
This follows our tradition of upgrading the Proxmox VE kernel to match the current Ubuntu version until we reach an Ubuntu LTS release, at which point we will only provide newer kernels as an opt-in option. The 7.0 kernel is based on the upcoming Ubuntu 26.04 Resolute release.

We have run this...
  • Like

Known Issues:

None at the time of writing.

Edit 2026-04-20: the kernel is now also available on the no-subscription repository.
 
Last edited:
uzumo said:
Anyone other than subscribers could be affected.
Click to expand...
It is not (yet) installed automatically during updates, at least not if you’re using the non-subscription repositories. You have to explicitly install it via apt install proxmox-kernel-7.0.

How do I know? I’m using the non-subscription repositories and just ran an apt full-upgrade on PBS and all my PVE hosts. And guess what I’m still on 6.17.13-3-pve. ;)
 
Last edited:
I'm sorry. It's fine if it's a test repository, but a “no-subscription” repository isn't intended for testing purposes.

Also, I don't think the “option” part implies it's for testing, does it?

If there really is an issue and testing hasn't been done yet, I think it's better not to put it in a repository like that.

If that was the intention, I think it's okay to voice your concerns.
 
You must log in or register to reply here.
Top Bottom
Back