strudel
/
ServerIssueApril2026
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

June 8th last update

This commit is contained in:
Seb Trudel 2026-06-08 18:26:43 -04:00
parent c4290f2948
commit 4762326e5f
1 changed files with 32 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

34
ServerIssueManual.html
View File

@ -143,7 +143,7 @@ Using <a href="https://ostechnix.com/proxmox-ve-8-linux-6-14-kernel-opt-in/">thi
</code>
The server boots fine after installing the 6.14 kernel. The comments said you could force a default kernel for Proxmox to boot to with the Proxmox-boot-tool kernel pin command.<br><br>
The server boots fine after installing the 6.14 kernel and selecting it manually at boot. The comments said you could force a default kernel for Proxmox to boot to with the Proxmox-boot-tool kernel pin command.<br><br>
Running <b>proxmox-boot-tool kernel list</b> command gives the following results:
@ -164,6 +164,36 @@ Running <b>proxmox-boot-tool kernel list</b> command gives the following results
</code>
Running <b>proxmox-boot-tool kernel pin 6.14.11-8-bpo12-pve</b> outputs:
<hr>
E: no kernel image found in /boot for '6.14.11-8-bpo12-pve', not setting default.
Possible Proxmox kernel versions are:
6.14.11-8-bpo12-pve
6.8.12-23-pve
<hr>
Assuming the Automatically selected kernels from kernel list means the new kernels are already pinned.
uname -r gives 6.8.12-23-pve which is good enough for me for now. I would like to make sure the kernel updates arent done without approval though, so I still need to figure out how to do that.
</p>
@ -175,7 +205,7 @@ Running <b>proxmox-boot-tool kernel list</b> command gives the following results
<h1 id="References"><Font color="Blue">References</Font></h1>
<h3>Test h3</h3>
</body>
</html>