Proxmox VE: Are we getting too many kernel updates for an enterprise virtualization platform?

I understand that this topic is important to you. However, it is only very indirectly related to the subject of this thread. The discussion here is about whether there are too many kernel updates and how these could be reduced (presumably mainly because people don't want to reboot, and partly because they're worried about regressions).

Also, and this is more of a side note, independently of whether the improvements you're asking for are actually needed (I only skimmed your two lengthy AI-generated essays), if you're concerned about operational safety, I'd advise caution when letting non-deterministic LLMs loose on your systems.

I also don't think it's a good idea to completely automate updates on critical infrastructure systems like hypervisors. Simply restricting access to this feature to selected admins, allowing them to perform updates manually instead of potentially letting AI agents mess up your hypervisors, would also somewhat mitigate the risks associated with having a root shell in the UI. ;)
If you had read the "lengthy AI essay", you would have noticed that this was the exact thing I criticized in another AI MCP approach. And IMHO it has a lot to do with the topic, namely that we all think that there are many updates that cause a lot of manual work.
My take on this is:
  • Having security updates is better than having none, so do not complain about "too may updates".
  • The reason for the flood is AI-detected exploits and this is not gonna end soon.
  • If you have a big exposure, the mitigate downtimes by HA and automatic VM migration.
  • If you want up lessen the burden of upgrading lots of PVE and PBS machines, you might want to use an automated approach.
  • That approach might ironically be using AI yourself OR any API-based approach. That being said, I would not trust the AI by exposing the raw API, but rather encapsulated isolated work flows via an MCP server or even a script using the API to upgrade and potentially reboot the server.
  • I found that to be infeasible REGARDLESS of if you want to use AI. It is the API itself that is lacking the feature.
  • If you want to circumvent that, you are actually increasing the attack surface, because you have to use a full shell to do the updates.
So, no, point not taken.
 
Last edited:
You are all right. I've witnessed 35 years of Big Tech madness — not by reading about it in the newspapers, but by being part of it myself.

We need to change things, or we will face enormous problems. We need to prepare for developments that are happening whether we like it or not, such as AI and quantum computing.

We need to work together. We need to stand together.
Just to made myself clear. My post isn't meant to be a pro- or anti-AI rant. But when it comes to system updates with APT, I wouldn't want to automate that on an important infrastructure server like Proxmox, and certainly wouldn't want an AI agent handling it, only for it to decide, in the worst-case scenario, "Sure, let's remove those 200 packages if that's what APT suggests." ;)

Don't get me wrong. I've been using Proxmox for more than 10 years, and this has never happened to me. Nevertheless, I think it's a good idea to keep certain processes from being fully automated and have a human review the proposed changes before pressing Y. Running apt full-upgrade on a hypervisor would be one of those things where I'd want that extra confirmation. And that also seems to be the reasoning behind the way the Proxmox devs have implemented updates, the way they did.

But hey, to each their own... ;)
 
Last edited:
Of course. But that is not what I do. You are insinuating something I did not write. It is just that after I upgraded one of my PVE hosts manually, I do not want to waste time and effort to do the same thing on 10 other machines manually. Also, if those are not backed by HA and actually do have downtimes, I want to update them during nighttime. That is something I can do by instructing my AI to do it at 2am. I might as well use a script that calls the API at the same time.

Besides, that is precisely what I proposed in Bug 6799: the API should first generate an upgrade plan for each individual host, including any package removals, and require explicit approval before executing it. If the plan changes, that approval becomes invalid. So automation would handle the execution, not replace the administrator's decision.
 
Last edited:
AI research is having major effects on software, even more specifically open source software that is widely used... so the linux kernel is definitely under the eye of sauron right now. I saw some report that MS fixed 5,000+ CVEs so far this year, when an average year would be 1,000. Having the kernel patched quickly is nice, having another hypervisor platform that release patches once a quarter is not confidence inspiring (eg. vmware)
 
Of course. But that is not what I do. You are insinuating something I did not write. It is just that after I upgraded one of my PVE hosts manually, I do not want to waste time and effort to do the same thing on 10 other machines manually. Also, if those are not backed by HA and actually do have downtimes, I want to update them during nighttime. That is something I can do by instructing my AI to do it at 2am. I might as well use a script that calls the API at the same time.

Besides, that is precisely what I proposed in Bug 6799: the API should first generate an upgrade plan for each individual host, including any package removals, and require explicit approval before executing it. If the plan changes, that approval becomes invalid. So automation would handle the execution, not replace the administrator's decision.
Well, Proxmox is based on Debian, after all, and theoretically, even just running apt dist-upgrade -y can be risky. You don't need AI for that. I'd say it's better to review what APT is going to do first.

As I said, the risk is very small in Proxmox VE, especially if you haven't installed any additional packages (apart from major version upgrades, which need to be done manually anyway), and I've personally never had any major issues. But the theoretical risk is still there.

But yeah, I can certainly see why you'd want to automate updates as much as possible. However, I think that would require quite a bit of work, in order for Proxmox to be able to officially support that, and possibly even switching to a completely different distro model (perhaps something image-based like the atomic or immutable distros do) to make it truly risk-free. Alternatively, they could go with something truly minimal or custom-built, but then you'd might also lose the flexibility to install additional packages. I don't know.

But as I said, this discussion really belongs in the other thread anyway. ;)
 
Last edited: