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

Yeah,there isn't at the moment.
@ProxmoxTeam : maybe you could post how-to where we can add our own packages/kernels , so that we can somehow respin and add whatever needed. I'm not sure that CUBIC would work atm.
 
Partok said:
Is there an ISO available that includes the 6.2 kernel?
Click to expand...
No currently not. But as we saw some more requests we'll discuss with devs & QA building a variant of the 7.4 ISO with that kernel.

ness1602 said:
Yeah,there isn't at the moment.
@ProxmoxTeam : maybe you could post how-to where we can add our own packages/kernels , so that we can somehow respin and add whatever needed. I'm not sure that CUBIC would work atm.
Click to expand...
You can already install on-top of Debian and respin a Debian ISO for whatever you require as base.
 
  • Like
Reactions: s0rn0, adresner, Falk R. and 1 other person
I'd prefer an ISO installer with kernel 6.2 as well. We are running our servers with 6.x kernel. The first step after installing a new node has been to switch to opt-in kernel 6.
Besides that, we are hit by a bug in pve-kernel-5.15.102-1-pve, which leads to a deadlock when using bonds (https://bugzilla.proxmox.com/show_bug.cgi?id=4604). This kernel is used by the proxmox-ve_7.4-1.iso installer. Because our network connection depends on the bond, we can't use version 7.4 to rollout new nodes. The only way to get a new node up and running is to use the previous 7.3 ISO installer and switch to kernel 6.2 right away.
 
  • Like
Reactions: s0rn0
6.2 has been very nice.. Looking forward to 6.3 asap to support the X670 boards for my Ryzen 9 sensors !!!
 
After installation 6.2 kernel, BT device stopped work:
Code: 
Apr 08 10:50:47 proxmox systemd[1195]: Stopped target Bluetooth.
Apr 08 10:50:47 proxmox systemd[1]: Stopped target Bluetooth.
Apr 08 10:50:52 proxmox systemd[1]: systemd-rfkill.service: Succeeded.
Apr 08 10:50:55 proxmox kernel: usb 1-8: reset full-speed USB device number 6 using xhci_hcd
Apr 08 10:50:56 proxmox kernel: usb 1-8: USB disconnect, device number 6
Apr 08 10:50:56 proxmox QEMU[5983]: kvm: libusb_release_interface: -4 [NO_DEVICE]
Apr 08 10:50:56 proxmox QEMU[5983]: kvm: libusb_release_interface: -4 [NO_DEVICE]
Apr 08 10:50:56 proxmox kernel: usb 1-8: new full-speed USB device number 7 using xhci_hcd
Apr 08 10:50:56 proxmox kernel: usb 1-8: New USB device found, idVendor=8087, idProduct=0032, bcdDevice= 0.00
Apr 08 10:50:56 proxmox kernel: usb 1-8: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Apr 08 10:50:56 proxmox kernel: Bluetooth: hci0: Device revision is 0
Apr 08 10:50:56 proxmox kernel: Bluetooth: hci0: Secure boot is enabled
Apr 08 10:50:56 proxmox kernel: Bluetooth: hci0: OTP lock is enabled
Apr 08 10:50:56 proxmox kernel: Bluetooth: hci0: API lock is enabled
Apr 08 10:50:56 proxmox kernel: Bluetooth: hci0: Debug lock is disabled
Apr 08 10:50:56 proxmox kernel: Bluetooth: hci0: Minimum firmware build 1 week 10 2014
Apr 08 10:50:56 proxmox kernel: Bluetooth: hci0: Bootloader timestamp 2019.40 buildtype 1 build 38
Apr 08 10:50:56 proxmox kernel: Bluetooth: hci0: Found device firmware: intel/ibt-0041-0041.sfi
Apr 08 10:50:56 proxmox kernel: Bluetooth: hci0: Boot Address: 0x100800
Apr 08 10:50:56 proxmox kernel: Bluetooth: hci0: Firmware Version: 172-6.23
Apr 08 10:50:56 proxmox systemd[1195]: Reached target Bluetooth.
Apr 08 10:50:56 proxmox systemd[1]: Starting Load/Save RF Kill Switch Status...
Apr 08 10:50:56 proxmox systemd[1]: Reached target Bluetooth.
Apr 08 10:50:56 proxmox systemd[1]: Started Load/Save RF Kill Switch Status.
Apr 08 10:50:58 proxmox kernel: Bluetooth: hci0: Waiting for firmware download to complete
Apr 08 10:50:58 proxmox kernel: Bluetooth: hci0: Firmware loaded in 1518206 usecs
Apr 08 10:50:58 proxmox kernel: Bluetooth: hci0: Waiting for device to boot
Apr 08 10:50:58 proxmox kernel: Bluetooth: hci0: Device booted in 25408 usecs
Apr 08 10:50:58 proxmox kernel: Bluetooth: hci0: Malformed MSFT vendor event: 0x02
Apr 08 10:50:58 proxmox kernel: Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-0041-0041.ddc
Apr 08 10:50:58 proxmox kernel: Bluetooth: hci0: Applying Intel DDC parameters completed
Apr 08 10:50:58 proxmox kernel: Bluetooth: hci0: Firmware timestamp 2023.6 buildtype 1 build 59564
Apr 08 10:51:01 proxmox systemd[1]: systemd-rfkill.service: Succeeded.
Apr 08 10:51:25 proxmox pvedaemon[1185]: <root@pam> successful auth for user 'root@pam'
Apr 08 10:53:25 proxmox pvedaemon[1183]: <root@pam> successful auth for user 'root@pam'
Apr 08 10:55:25 proxmox pve-guests[1228]: <root@pam> end task UPID:proxmox:000004CD:00000564:64311B87:startall::root@pam: OK
Apr 08 10:55:25 proxmox systemd[1]: Finished PVE guests.
Apr 08 10:55:25 proxmox systemd[1]: Starting Proxmox VE scheduler...
Apr 08 10:55:26 proxmox pvescheduler[7540]: starting server
Apr 08 10:55:26 proxmox systemd[1]: Started Proxmox VE scheduler.
Apr 08 10:55:26 proxmox systemd[1]: Reached target Multi-User System.
Apr 08 10:55:26 proxmox systemd[1]: Reached target Graphical Interface.
Apr 08 10:55:26 proxmox systemd[1]: Starting Update UTMP about System Runlevel Changes...
Apr 08 10:55:26 proxmox systemd[1]: systemd-update-utmp-runlevel.service: Succeeded.
Apr 08 10:55:26 proxmox systemd[1]: Finished Update UTMP about System Runlevel Changes.

Please advice how to fix or safely rollback to 5.15.
 
@vgomenyuk
# proxmox-boot-tool kernel list
to see what is available on your system and pick the 5.15.*-pve you want to boot into, latest is 5.15.104-1-pve
# proxmox-boot-tool kernel pin 5.15.104-1-pve

link on the above and how to test future 6.2 kernels without permanently selecting them, --next-boot.
Override the Kernel-Version for next Boot
 
vesalius said:
@vgomenyuk
# proxmox-boot-tool kernel list
to see what is available on your system and pick the 5.15.*-pve you want to boot into, latest is 5.15.104-1-pve
# proxmox-boot-tool kernel pin 5.15.104-1-pve

link on the above and how to test future 6.2 kernels without permanently selecting them, --next-boot.
Override the Kernel-Version for next Boot
Click to expand...
Thanks. BT integration stops work even on 5.15 version. Strange. Interesting how to fix it.
 
t.lamprecht said:
No currently not. But as we saw some more requests we'll discuss with devs & QA building a variant of the 7.4 ISO with that kernel.


You can already install on-top of Debian and respin a Debian ISO for whatever you require as base.
Click to expand...
I would also be interested in a 7.4 ISO with 6.2 kernel. Thank you.
 
  • Like
Reactions: moooootz
Just FYI, after having tried the opt-in 5.19 kernel some time ago (see https://forum.proxmox.com/threads/o...-proxmox-ve-7-x-available.115090/#post-498817) I now gave the opt-in 6.2 a try.
Behavior seemed to be indentical to my experience with 5.19.
In general it seems OK (like with 5.19), but on my gaming Win 10 VM with GPU pass-through performance is still far worse, than with the compared 5.15.x kernel.
The "preempt=" boot parameters still have the same effect as described before. Regardless of the setting, games show lags every few seconds.
I still could not pin it down to some specific change. However, as before I'll have to stay with 5.15 for now.
 
I have switched from kernel 5.15 to 6.2.9-1 and for some reason a LXC (Alpine 3.17) is maxing out on memory....
On 5.15 kernel the LXC had 512MB working memory and only used about 200-250MB.
But with kernel 6.2.9-1 the same LXC uses (or peaks) at it's maximum 512MB.
Even my Proxmox host crashed as a result, so I set the LXC memory to 1024MB. So far no crashes.

- Is this normal behavior with the new kernel, more memory consumption?
 
Spoonman2002 said:
I have a second Proxmox host with exactly the same LXC running, also new kernel 6.2.1-9 and this has no (memory) issues at all.
Click to expand...
Different CPUs? Some CPU mitigations might have a small overhead, but normally that's on computation, not memory.
 
@t.lamprecht
just had another "freeze" of my Proxmox host.....
So the Alpine lxc had nothing to do with this.

I'm left with two options:
- or the new 6.2.9-1 kernel is the cause (I will now downgrade back to 5.15)
- or the HP BIOS/firmware I did last monday is the cause of the hanging (official HP firmware used).
 
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