Docker build from 2022-07-09 working :) #15
Replies: 1 comment 5 replies
-
|
Ta, I'll look at adding this build to the releases soonish. (Need to schedule some downtime and give it a quick confirm on my own node.) |
Beta Was this translation helpful? Give feedback.
-
|
No worries, just thought I'd mention that it works, flawlessly I might add. Thanks! You're a star. If you need me to test anything or whatnot, give me a shout and I'll do my best. Don't know much kernel code, but have compiled it a couple of times (not recently though haha) I did have to do something a bit different to pass through some NVMe storage, but I think that was because of a firmware bug on them rather than anything to do with the kernel. (had to modify my VM's config with With the docker build image, how does that run? Would you just download the docker image and run it and you get a kernel at the end then, or...? No rush on a reply if it's something complex. Hope you had a good one. Jessica |
Beta Was this translation helpful? Give feedback.
-
Yes this certainly looks related to some firmware / VFIO passthrough shenanigans. You may be able to avoid the need for this by flashing new firmware to your NVMe drive/s.
Assuming you have docker installed on a machine you'd just run the command:
Where the volume binding (-v bit) is set to the host machine folder of your choice, in the above case Note that the Docker container path That command will download the most recent Docker image for the builder and start building it. Give it 10 - 300 minutes depending on how fast your host machine and storage drives are and the debs will get generated in the host path you chose. Just make sure you give it a folder on a disk with ~40GB of spare space (the full kernel source is rather large and the intermediate build files will be too). (Don't expect the lower end of that timescale though, that's more what I see when running kernel compiles on a supercomputer node with some fairly high specs.) More details on the docker process above can be found here: https://github.com/Aterfax/relax-intel-rmrr/blob/master/README.md#docker---build-packages-from-sources-intermediate The Docker image itself is built from: https://github.com/Aterfax/relax-intel-rmrr/blob/master/Dockerfile after Git cloning the repo locally. You can also see that the ENTRYPOINT is the last line and is set to run the exact same command in the Github Action since the Action will override the standard ENTRYPOINT. This Docker build process is exactly the same as the Github Action used to make the debs here on Github, as the Github action is using the same docker image with a bit more Github Action tooling to save the important files (as artifacts). My action is also set to use tagged Github Action runners (tagged: pve-kernel) on virtual machines I have specifically configured to build these kernel debs This is mainly to do with using faster (SSD) storage, limiting the blast radius of any compromise with VLAN network separation, retaining the build files between kernel builds to speed things up and because the default Github Actions runners would take a very long time to finish compiling. (Plus I think they also lack the required storage space?) This repo will also automatically rebuild the docker image and upload it to dockerhub when I make changes. The If you are interested in the actions driving this, they are all stored in https://github.com/Aterfax/relax-intel-rmrr/blob/master/.github/workflows/
I think if anything making the readme / documentation around the process as concise and clear as possible would be great so more eyes on that and any suggestions / comments are welcome. I don't expect the build process / kernel compile parts to change a great deal or often so we're likely good on the more esoteric codey front for a while. My plan is to update the kernel on my node over the weekend assuming I don't melt into a puddle (the UK being mid-heatwave by that time by the look of the forecast.) |
Beta Was this translation helpful? Give feedback.
-
|
I have also validated this build as functional. Thanks! |
Beta Was this translation helpful? Give feedback.
-
|
Release is now available. |
Beta Was this translation helpful? Give feedback.
-
|
Huzzah! Thank you for the detailed information for using docker for builds, very appreciated. Been a bit busy past couple of weeks, but the build I installed from this has been working flawlessly. I haven't updated to any later build yet, but I have a plan for testing newer builds without having to test them "trial by fire". I've got a somewhat spare G6 here that I have a testing install of proxmox on, so I think that would make a perfect testing ground for testing passthrough and this kernel, so I can give more regular feedback. I'll definitely have a look at the documentation to see if there's anything I can help clarify for readability and people less familiar with working round HPE's somewhat esoteric hardware :) Hope you've had a good couple of weeks. Kind regards, |
Beta Was this translation helpful? Give feedback.
-
Hey @Aterfax
I've done my upgrade to Proxmox 7.2 (on my G8 HPE DL380e) and I've tried the kernel from https://github.com/Aterfax/relax-intel-rmrr/actions/runs/2639751612 and it works just fine passing through a PCIe Disk Controller, and I thought I'd just write a quick discussion thread and let you know :)
When I get some more time, I'll also try it on my G6s and see if it works on that too. 👍
Thank you :)
Jessica
Beta Was this translation helpful? Give feedback.
All reactions