Opt-in Linux 6.1 Kernel for Proxmox VE 7.x available

Hi, brand new here, maybe I'm missing something.
I'm trying to install the latest 6.1 kernel but:

root@proxmox:~# dpkg-query --list | grep pve-kernel
ii pve-firmware 3.4-1 all Binary firmware code for the pve-kernel
ii pve-kernel-5.15 7.2-1 all Latest Proxmox VE Kernel Image
ii pve-kernel-5.15.30-2-pve 5.15.30-3 amd64 The Proxmox PVE Kernel Image
ii pve-kernel-helper 7.2-2 all Function for various kernel maintenance tasks.

root@proxmox:~# apt install pve-kernel-6.1
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
E: Unable to locate package pve-kernel-6.1
E: Couldn't find any package by glob 'pve-kernel-6.1'

Any ideas please? Thank you.
 
tchuyev said:
Hi, brand new here, maybe I'm missing something.
I'm trying to install the latest 6.1 kernel but:

root@proxmox:~# dpkg-query --list | grep pve-kernel
ii pve-firmware 3.4-1 all Binary firmware code for the pve-kernel
ii pve-kernel-5.15 7.2-1 all Latest Proxmox VE Kernel Image
ii pve-kernel-5.15.30-2-pve 5.15.30-3 amd64 The Proxmox PVE Kernel Image
ii pve-kernel-helper 7.2-2 all Function for various kernel maintenance tasks.

root@proxmox:~# apt install pve-kernel-6.1
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
E: Unable to locate package pve-kernel-6.1
E: Couldn't find any package by glob 'pve-kernel-6.1'

Any ideas please? Thank you.
Click to expand...
You seem to be on Proxmox 7.2 not the latest 7.3, maybe update your base install first then try for the new kernel.


try a apt update && apt full-upgrade first before
apt install pve-kernel-6.1
.
 
Last edited:
vesalius said:
You seem to be on Proxmox 7.2 not the latest 7.3, maybe update your base install first then try for the new kernel.


try a apt update && apt full-upgrade first before
apt install pve-kernel-6.1
.
Click to expand...
Still no chance I'm afraid:

root@proxmox:~# apt update
Hit:1 http://ftp.fr.debian.org/debian bullseye InRelease
Hit:2 http://security.debian.org bullseye-security InRelease
Hit:3 http://ftp.fr.debian.org/debian bullseye-updates InRelease
Err:4 https://enterprise.proxmox.com/debian/pve bullseye InRelease
401 Unauthorized [IP: 51.91.38.34 443]
Reading package lists... Done
E: Failed to fetch https://enterprise.proxmox.com/debian/pve/dists/bullseye/InRelease 401 Unauthorized [IP: 51.91.38.34 443]
E: The repository 'https://enterprise.proxmox.com/debian/pve bullseye InRelease' is not signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.

root@proxmox:~# apt update && apt full-upgrade
Hit:1 http://security.debian.org bullseye-security InRelease
Hit:2 http://ftp.fr.debian.org/debian bullseye InRelease
Hit:3 http://ftp.fr.debian.org/debian bullseye-updates InRelease
Err:4 https://enterprise.proxmox.com/debian/pve bullseye InRelease
401 Unauthorized [IP: 51.91.38.34 443]
Reading package lists... Done
E: Failed to fetch https://enterprise.proxmox.com/debian/pve/dists/bullseye/InRelease 401 Unauthorized [IP: 51.91.38.34 443]
E: The repository 'https://enterprise.proxmox.com/debian/pve bullseye InRelease' is not signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
 
tchuyev said:
Still no chance I'm afraid:

root@proxmox:~# apt update
Hit:1 http://ftp.fr.debian.org/debian bullseye InRelease
Hit:2 http://security.debian.org bullseye-security InRelease
Hit:3 http://ftp.fr.debian.org/debian bullseye-updates InRelease
Err:4 https://enterprise.proxmox.com/debian/pve bullseye InRelease
401 Unauthorized [IP: 51.91.38.34 443]
Reading package lists... Done
E: Failed to fetch https://enterprise.proxmox.com/debian/pve/dists/bullseye/InRelease 401 Unauthorized [IP: 51.91.38.34 443]
E: The repository 'https://enterprise.proxmox.com/debian/pve bullseye InRelease' is not signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.

root@proxmox:~# apt update && apt full-upgrade
Hit:1 http://security.debian.org bullseye-security InRelease
Hit:2 http://ftp.fr.debian.org/debian bullseye InRelease
Hit:3 http://ftp.fr.debian.org/debian bullseye-updates InRelease
Err:4 https://enterprise.proxmox.com/debian/pve bullseye InRelease
401 Unauthorized [IP: 51.91.38.34 443]
Reading package lists... Done
E: Failed to fetch https://enterprise.proxmox.com/debian/pve/dists/bullseye/InRelease 401 Unauthorized [IP: 51.91.38.34 443]
E: The repository 'https://enterprise.proxmox.com/debian/pve bullseye InRelease' is not signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
Click to expand...

See here: [1] how to update, if you do not have an active subscription.
Then you are also be able to install an opt-in kernel.

[1] https://forum.proxmox.com/threads/reboot-occurs-randomly.119840/#post-520320
 
  • Like
Reactions: vesalius
tchuyev said:
Still no chance I'm afraid:

root@proxmox:~# apt update
Hit:1 http://ftp.fr.debian.org/debian bullseye InRelease
Hit:2 http://security.debian.org bullseye-security InRelease
Hit:3 http://ftp.fr.debian.org/debian bullseye-updates InRelease
Err:4 https://enterprise.proxmox.com/debian/pve bullseye InRelease
401 Unauthorized [IP: 51.91.38.34 443]
Reading package lists... Done
E: Failed to fetch https://enterprise.proxmox.com/debian/pve/dists/bullseye/InRelease 401 Unauthorized [IP: 51.91.38.34 443]
E: The repository 'https://enterprise.proxmox.com/debian/pve bullseye InRelease' is not signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.

root@proxmox:~# apt update && apt full-upgrade
Hit:1 http://security.debian.org bullseye-security InRelease
Hit:2 http://ftp.fr.debian.org/debian bullseye InRelease
Hit:3 http://ftp.fr.debian.org/debian bullseye-updates InRelease
Err:4 https://enterprise.proxmox.com/debian/pve bullseye InRelease
401 Unauthorized [IP: 51.91.38.34 443]
Reading package lists... Done
E: Failed to fetch https://enterprise.proxmox.com/debian/pve/dists/bullseye/InRelease 401 Unauthorized [IP: 51.91.38.34 443]
E: The repository 'https://enterprise.proxmox.com/debian/pve bullseye InRelease' is not signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
Click to expand...
As stated above you need change your /etc/apt/sources.list file. yoi can do that from the CLI as linked above or since pve 7 you can also disable the enterprise repository and add the non-enterprise repository from the web-gui. https://pve.proxmox.com/wiki/Package_Repositories#_repositories_in_proxmox_ve

gui-node-repositories.png
 
In your screenshot:
  1. the last line stands for the enterprise repository. Get a license, or simply remove that line. This line triggers the "401 Unauthorized" message.
  2. then click the "Add" button and select the "no-subscription" entry in the drop-down list

Problem solved ;-)
 
  • Like
Reactions: vesalius
I run a Threadripper with 2GPU in passthrough and a root ZFS install.
I mounted /tmp on ram as indicated and I have no issues.
Both passthrough are working fine.
Thanks for releasing 6.1 this early!
 
Last edited:
First, best wishes to all.

When using pve kernel 6.1 with multi monitor setup (so probably for gpu passthrough) using amdgpu driver you could run into issues.
I'm using it with daisy chained dp monitors (MST) and got a stack trace.
First noticed that in a VM running opensuse tumbleweed running kernel 6.1.x using gpu pass through. This vm become unresponsive.
Now tested with pve kernel 6.1. and got a stack trace on the pve host as soon as I used MST. Single monitor use is stable.

https://gitlab.freedesktop.org/drm/amd/-/issues/2171
Above bug report seems to track this issue, with also several other linked bug reports.
 
Thanks for bringing that issue to attention again and the separate thread. Seems that 6.1 kernel needs some polishing on amdgpu side :(
For this moment I will probably stay on 5.19 (as long as it will be available), or current default pve kernel on the host. And will see how a vm with gpu passthrough and guest kernel 6.1 and coming updates will behave.
Otherwise I didn't have other issues with 6.1 (apart from tmp on tmpfs for / on zfs for now).
 
Hmmm... any plans to make a backported OpenVSwitch 3.x available for this kernel?
I'm tracking/seeing strange troubles with 6.1 (like the packets not send up to the IntPort for the VLAN tagged to the IntPort, but the packets do arrive in the bridge) and wonders about kernel interactions
 
  • Like
Reactions: batonac
How can I remove this 6.1 kernel?

Code: 
apt remove pve-kernel-6.1
apt purge pve-kernel-6.1

after my removal it stills boot with 6.1?

Code: 
root@pve:~# uname -a
Linux pve 6.1.0-1-pve #1 SMP PREEMPT_DYNAMIC PVE 6.1.0-1 (Tue, 13 Dec 2022 15:08:53 +0 x86_64 GNU/Linux

Thanks for helping my out.
 
magingale said:
How can I remove this 6.1 kernel?

Code: 
apt remove pve-kernel-6.1
apt purge pve-kernel-6.1

after my removal it stills boot with 6.1?

Code: 
root@pve:~# uname -a
Linux pve 6.1.0-1-pve #1 SMP PREEMPT_DYNAMIC PVE 6.1.0-1 (Tue, 13 Dec 2022 15:08:53 +0 x86_64 GNU/Linux

Thanks for helping my out.
Click to expand...
apt purge pve-kernel-6.1.*
 
mac.linux.free said:
apt purge pve-kernel-6.1.*
Click to expand...

Your the best, a lot more output and file changes I'm getting from your cli commands ;-)


Code: 
The following packages will be REMOVED:
  pve-kernel-6.1* pve-kernel-6.1.0-1-pve*
0 upgraded, 0 newly installed, 2 to remove and 0 not upgraded.
After this operation, 422 MB disk space will be freed.
Do you want to continue? [Y/n] y
(Reading database ... 66584 files and directories currently installed.)
Removing pve-kernel-6.1 (7.3-1) ...
Removing pve-kernel-6.1.0-1-pve (6.1.0-1) ...
 
magingale said:
How can I remove this 6.1 kernel?

Code: 
apt remove pve-kernel-6.1
apt purge pve-kernel-6.1

after my removal it stills boot with 6.1?

Code: 
root@pve:~# uname -a
Linux pve 6.1.0-1-pve #1 SMP PREEMPT_DYNAMIC PVE 6.1.0-1 (Tue, 13 Dec 2022 15:08:53 +0 x86_64 GNU/Linux

Thanks for helping my out.
Click to expand...
You need to update your grub.

List your avaiulable kernel with
proxmox-boot-tool kernel list

then update
proxmox-boot-tool kernel pin <kernel-version>

Also for futher info
proxmox-boot-tool help

Reboot then remove the the kernel again
 
Last edited:
Seamless upgrade here from 5.19.17-1
System: AMD Ryzen 7 5800x, 6900xt + 3070 PCIE passthrough to VM(s). ZFS Raid, LXC containers, everything "just worked".

Swear i'm seeing the CPU idling at lower speeds than before but maybe mis-remembering.
Still set to ondemand governor but seeing noticeable lower idle temps. Maybe a cool change rolled in.
Regardless!

Clean upgrade. Nice one team!
Will tool around see if i can break anything and report back
 
hvisage said:
Hmmm... any plans to make a backported OpenVSwitch 3.x available for this kernel?
I'm tracking/seeing strange troubles with 6.1 (like the packets not send up to the IntPort for the VLAN tagged to the IntPort, but the packets do arrive in the bridge) and wonders about kernel interactions
Click to expand...
Debian pushed an update to OVS yesterday. openvswitch-switch: 2.15.0+ds1-2+deb11u2 Seems to have fixed the network problems I had with the 6.1 kernel. Obviously not much testing but it was unusable before. Didn't see a change log for it.
Your mileage may very.
 
Last edited:
Sadly on my Topton SFF PC with Intel N6005 VMs wont boot on 6.1 kernel (same problems on unofficial 6.0-edge kernels). On 5.19 no problem. VMs are not able to boot from local-lvm storage (nvme-ssd). Its possible to create new VM run installation until vhdd partitioning, but then it fails.

i get error like this: Could not read L1 table: Invalid argument TASK ERROR: start failed: QEMU exited with code 1
 
You must log in or register to reply here.

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Quick Navigation

Home Get Subscription Wiki Downloads Proxmox Customer Portal About

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!
Community platform by XenForo® © 2010-2024 XenForo Ltd.
Top Bottom
Back