Opt-in Linux 7.0 Kernel for Proxmox VE 9 available on test

Well, with the 6.18 kernel being absolutely unusable due to SATA controller dropouts crashing containers using NFS and occasionally the entire Proxmox host I expected a repeat with the 7.0 one. Happy to say that it passed every test that would guarantee a crash on 6.18 and after 24 hours uptime I don't notice any real issues, awesome.
 
  • Like
Reactions: nmateo
Cant install proxmox-kernel-7.0. But it was due to having no space left on /boot/efi (1GB). Using a apt autoremove helped. Just wanted to post it here, if anyone has the same situation.

Code: 
Continue? [Y/n] Y
Setting up proxmox-kernel-7.0.0-1-rc7-pve-signed (7.0.0-1~rc7+1) ...
Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/initramfs-tools 7.0.0-1-rc7-pve /boot/vmlinuz-7.0.0-1-rc7-pve
update-initramfs: Generating /boot/initrd.img-7.0.0-1-rc7-pve
Running hook script 'zz-proxmox-boot'..
Re-executing '/etc/kernel/postinst.d/zz-proxmox-boot' in new private mount namespace..
No /etc/kernel/proxmox-boot-uuids found, skipping ESP sync.
Updating kernel version 7.0.0-1-rc7-pve in systemd-boot...
install: error writing '/boot/efi/1446e4c3f5ea48c4a3bbc9c2ba342a6d/7.0.0-1-rc7-pve/linux': No space left on device
Error: could not copy '/boot/vmlinuz-7.0.0-1-rc7-pve' to '/boot/efi/1446e4c3f5ea48c4a3bbc9c2ba342a6d/7.0.0-1-rc7-pve/linux'.
/usr/lib/kernel/install.d/90-loaderentry.install failed with exit status 1.
run-parts: /etc/initramfs/post-update.d//systemd-boot exited with return code 1
run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
Failed to process /etc/kernel/postinst.d at /var/lib/dpkg/info/proxmox-kernel-7.0.0-1-rc7-pve-signed.postinst line 20.
dpkg: error processing package proxmox-kernel-7.0.0-1-rc7-pve-signed (--configure):
 installed proxmox-kernel-7.0.0-1-rc7-pve-signed package post-installation script subprocess returned error exit status 2
dpkg: dependency problems prevent configuration of proxmox-kernel-7.0:
 proxmox-kernel-7.0 depends on proxmox-kernel-7.0.0-1-rc7-pve-signed | proxmox-kernel-7.0.0-1-rc7-pve; however:
  Package proxmox-kernel-7.0.0-1-rc7-pve-signed is not configured yet.
  Package proxmox-kernel-7.0.0-1-rc7-pve is not installed.
  Package proxmox-kernel-7.0.0-1-rc7-pve-signed which provides proxmox-kernel-7.0.0-1-rc7-pve is not configured yet.

dpkg: error processing package proxmox-kernel-7.0 (--configure):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 proxmox-kernel-7.0.0-1-rc7-pve-signed
 proxmox-kernel-7.0
Error: Sub-process /usr/bin/dpkg returned an error code (1)

Code: 
root@pveneo:~# apt autoremove
REMOVING:                       
  libtlsrpt0      proxmox-kernel-6.14.11-1-pve-signed  proxmox-kernel-6.17.13-1-pve-signed  proxmox-kernel-6.17.4-1-pve-signed  proxmox-rrd-migration-tool
  libzpool6linux  proxmox-kernel-6.14.11-4-pve-signed  proxmox-kernel-6.17.2-1-pve-signed   proxmox-kernel-6.17.4-2-pve-signed
  menu            proxmox-kernel-6.14.11-5-pve-signed  proxmox-kernel-6.17.2-2-pve-signed   proxmox-kernel-6.17.9-1-pve-signed

on removal it also set up the proxmox-kernel-7.0 that the server tried to install before. After reboot, node is online with kernel 7.0 :-)
 
jsterr said:
Cant install proxmox-kernel-7.0. But it was due to having no space left on /boot/efi (1GB). Using a apt autoremove helped. Just wanted to post it here, if anyone has the same situation.
*snip*
on removal it also set up the proxmox-kernel-7.0 that the server tried to install before. After reboot, node is online with kernel 7.0 :-)
Click to expand...
I really wish I hadn't gone with the default partitioning sometimes because of stuff like that, and the root lvm "only" being 100gb by default.

I have found one minor bug - when backups are running my webui gets really slow and tasks (container console/login/etc ) keep timing out (ssh to the node is fine and all my containers are still running normal though), but the second the backup is done it's like nothing happened, even without reloading the page.
 
Running a tailscale subnet router on a VM and after upgrading the download speed tanked to ~0.2 Mbps from normal ~100Mbps.
Weirdly the upload speed was fine.
Tested using openspeedtest on another VM and both of them are up to date Debian trixie installs.
VM:s have no iptables and tailscale gets a direct connection according to tailscale status.
 
rage said:
I read that Kernel 7 has now SR-IOV already enabled.
Any hint how to use / enable it ?
I would need it for the intel iGPU (265H)
Click to expand...
Doesnt work on my 245K

Code: 
[    4.241268] i915 0000:00:02.0: driver does not support SR-IOV configuration via sysfs<br>

Even when lspci is showing it is supported

Code: 
    Capabilities: [320 v1] Single Root I/O Virtualization (SR-IOV)
        IOVCap:    Migration- 10BitTagReq+ IntMsgNum 0
        IOVCtl:    Enable- Migration- Interrupt- MSE- ARIHierarchy- 10BitTagReq-
        IOVSta:    Migration-
        Initial VFs: 7, Total VFs: 7, Number of VFs: 0, Function Dependency Link: 00
        VF offset: 1, stride: 1, Device ID: 7d67
        Supported Page Size: 00000553, System Page Size: 00000001
        Region 0: Memory at 000000b010000000 (64-bit, prefetchable)
        VF Migration: offset: 00000000, BIR: 0

But intel website states its unsupported on Meteor Lake

https://www.intel.com/content/www/us/en/support/articles/000093216/graphics/processor-graphics.html
 
Last edited:
But according the Intel site it should work, because 245K and my 265H are Arrow Lake CPUs, which should support .
Intel® Core™ Ultra Processor (Series 2) processor family (Formerly Known as Arrow Lake)Single Root IO Virtualization (SR-IOV)

MeteorLake are Ultra 1xx CPUs.
 
Im really confused about intel new naming scheme, but Im assuming 245K is Core Ultra 100 series (Meteor Lake) and Core Ultra 200 is new release of Arrow Lake Refresh? Anyway, it works just fine with patched strongtz/sriov-dkms on 6.19 and does not work on upstream 7.0.

If you have any suggestion how can I test sriov on 7.0 please let me know, I will try that. sysfs / `options i915 max_vfs=7` doesnt work.

Code: 
$
lspci | grep -iE "(meteor|arrow)"
00:01.0 PCI bridge: Intel Corporation Meteor Lake-H PCIe Root Port (rev 10)
00:02.0 VGA compatible controller: Intel Corporation Arrow Lake-S [Intel Graphics] (rev 06)
00:07.0 PCI bridge: Intel Corporation Meteor Lake-P Thunderbolt 4 PCI Express Root Port #0 (rev 10)
00:07.1 PCI bridge: Intel Corporation Meteor Lake-P Thunderbolt 4 PCI Express Root Port #1 (rev 10)
00:0b.0 Processing accelerators: Intel Corporation Arrow Lake NPU (rev 01)
00:0d.0 USB controller: Intel Corporation Meteor Lake-P Thunderbolt 4 USB Controller (rev 10)
00:0d.2 USB controller: Intel Corporation Meteor Lake-P Thunderbolt 4 NHI #0 (rev 10)
 
You must log in or register to reply here.
Top Bottom
Back