Built for 7.1-10

[OrpheeGT]

Hello,

When I tried your compiled *.deb file, it did not work, my kernel was still "5.13.19-4-pve"
So I took your docker build files, and encountered some issues while compiling from sources, so I fixed the patch (5_13)

I did not want to break build7.sh so I made a new build7.1-10.sh

Maybe I should have overwrited it...

Once built with :
RMRR_AUTOINSTALL=1 bash ./build7.1-10.sh

I had :

linux-tools-5.13_5.13.19-10_amd64.deb
linux-tools-5.13-dbgsym_5.13.19-10_amd64.deb
pve-headers-5.13.19-5-pve-relaxablermrr_5.13.19-10_amd64.deb
pve-kernel-5.13.19-5-pve-relaxablermrr_5.13.19-10_amd64.deb
pve-kernel-libc-dev_5.13.19-10_amd64.deb

after reboot :

uname -r

5.13.19-5-pve-relaxablermrr

And PCI passthrough works with my LSI HBA IT card.

Feel free to adapt to better standards if needed.

thanks

[MichaelTrip]

Sorry for missing this one. I will take a look at it this week. Thank you for your PR!

[OrpheeGT]

Hi again,
I didn't pay attention to it earlier, but, in DMESG I have the following messages :

[ 0.098731] DMAR: [Firmware Bug]: No firmware reserved region can cover this RMRR [0x00000000000e8000-0x00000000000e8fff], contact BIOS vendor for fixes
[ 0.098794] DMAR: [Firmware Bug]: Your BIOS is broken; bad RMRR [0x00000000000e8000-0x00000000000e8fff]
[ 0.123113] [Firmware Bug]: the BIOS has corrupted hw-PMU resources (MSR 38d is 330)

Is it expected or do I really have an issue ?
Thanks

Edit : Ok it does not seems to be related to the kernel/patch ... same happens with default kernel.

[Aterfax]

I have also modified OrpheeGT's fork to support the latest kernel (5_15) here: https://github.com/Aterfax/relax-intel-rmrr

I have 5.15.35-1-pve-relaxablermrr currently.

[Aterfax]

FYI - I have now updated my repo to use sed instead of patch to avoid the code moving lines breaking the patching (aka needing a specific patch for each kernel version.)

https://github.com/Aterfax/relax-intel-rmrr

I'll need to make a PR a little later if this is desired in the main repo.

[MichaelTrip]

Hi all,

First of all: sorry for my absence, but i had some other work stuff to take care of. Also, because of the rising power prices here in Holland, i no longer use my HP ML380 g8, so i don´t have a test system for testing my patches. If someone wants to take over this kernel, please do it, because i am no longer capable of compiling and testing new kernels.

[Aterfax]

Hi all,

First of all: sorry for my absence, but i had some other work stuff to take care of. Also, because of the rising power prices here in Holland, i no longer use my HP ML380 g8, so i don´t have a test system for testing my patches. If someone wants to take over this kernel, please do it, because i am no longer capable of compiling and testing new kernels.

No worries dude, thanks for all the effort you have put in already!

I think this patch also applies to the HP Gen 8 microserver? So there's probably a few people kicking about who can do testing. I expect that this can also be "Dockerized" entirely and potentially ran on Github Actions if if doesn't exceed the compute/time requirements.

[accessiblepixel]

Hi all,
First of all: sorry for my absence, but i had some other work stuff to take care of. Also, because of the rising power prices here in Holland, i no longer use my HP ML380 g8, so i don´t have a test system for testing my patches. If someone wants to take over this kernel, please do it, because i am no longer capable of compiling and testing new kernels.

No worries dude, thanks for all the effort you have put in already!

I think this patch also applies to the HP Gen 8 microserver? So there's probably a few people kicking about who can do testing. I expect that this can also be "Dockerized" entirely and potentially ran on Github Actions if if doesn't exceed the compute/time requirements.

Yep. I'm running HPE G8 hardware, (A DL380e to be exact) and so far both the original killer127 patch has done me right. I'll be testing out your 7.2 kernel tonight myself @Aterfax available in your repo. There's a few people who've made forks, but it appears that yours has the latest version? :)

Thanks for all your work @MichaelTrip I know you've helped a lot of people keep their systems running since the original killer127 patches haven't been updated for Proxmox 7, and given that support for Proxmox 6 ends in about 20 days, I figure it's as good a time as any to try out a new kernel. :)

Kind regards,
Jessica

[Aterfax]

At present I am only adding the kernels I have actually updated to on my DL380p and tested in https://github.com/Aterfax/relax-intel-rmrr/releases That said, in principle if the build process didn't error out then you should get away with grabbing the lastest build (happens every Saturday) here: https://github.com/Aterfax/relax-intel-rmrr/actions/workflows/build-kernel-debs.yml

Just be aware the older build artifacts will stop being available after a while when Github purges them so you might want to get copies of older ones JIC.

[accessiblepixel]

At present I am only adding the kernels I have actually updated to on my DL380p and tested in https://github.com/Aterfax/relax-intel-rmrr/releases That said, in principle if the build process didn't error out then you should get away with grabbing the lastest build (happens every Saturday) here: https://github.com/Aterfax/relax-intel-rmrr/actions/workflows/build-kernel-debs.yml

Just be aware the older build artifacts will stop being available after a while when Github purges them so you might want to get copies of older ones JIC.

@Aterfax You're a star, friend :) I'll keep you posted if I have any problems running them on my two G6s and G8s. I'm part of a homelab community too, if you don't mind I'll share links there, and on my site, to your repo and build process if you're alright with that?

I'll open issues in future on there too, just so Michael doesn't get a bunch of messages too.

If there's anything else I can do to help, do let me know. Maybe could set up some kind of mirror for the automatic builds so that they're always available after they expire on github, or something? Just an idea :)

I'll be starting the upgrade to Proxmox 7 sometime this week hopefully, so everythings up and running before official support ends.

Kind regards,
Jessica.

[Aterfax]

@Aterfax You're a star, friend :) I'll keep you posted if I have any problems running them on my two G6s and G8s. I'm part of a homelab community too, if you don't mind I'll share links there, and on my site, to your repo and build process if you're alright with that?

Yep that's fine though I think I still have a bit of work to do on the CI/CD process. I'll probably take a look at sorting out a form of longer term artifact storage in a bit.