[pve-devel] Please help: beginner trying to compile Proxmox kernel 4.15
The Anh Tran
trtheanh at gmail.com
Sat Sep 22 07:19:02 CEST 2018
I have Dell EMC ScaleIO (renamed to VxFlexOS) license.
ScaleIO has 3 components:
SDS: server storage provider. This component could be installed on
MDM: distributed storage metadata management. This is installed on a VM
for HA & live-migration requirement.
SDC: storage client consumer. This component could be installed on
I have posted a SR ticket on EMC site. They replied: "unable to support
Proxmox distribution due to ... reasons".
=> have to solve this myself.
Sdc has a kernel module: scini.ko, which is a pre-compiled binary by
EMC, for each support OS version (Redhat, Ubuntu, ...).
scini.ko, which compiled on ubuntu xenial 16.04, has this module version
magic string: "4.15.0-33-generic SMP mod_unload".
Promox kernel 4.15.18-xy, while based on Ubuntu hwe kernel 4.15.18, has
module magic string: "4.15.18-xy-pve SMP mod_unload modversions"
SDC boot script /etc/init.d/scini run this: "insmod /bin/emc/scini.ko"
Magic string mismatch => kernel refuse to load
I could change to force load: "insmod -f /bin/emc/scini.ko"
But Proxmox compile flag inside debian/rules doesn't have
So, i could make scini.ko run on Proxmox by re-compile kernel, with some
_ add "-e CONFIG_MODULE_FORCE_LOAD \" in pve-kernel/debian/rules
_ or modify pve-kernel/debian/rules: "-d CONFIG_MODVERSIONS \", and edit
Makefile version string vars, from "4.15.18-xy-pve" to "4.15.0-xy-generic".
May I know the reason why you add "CONFIG_MODVERSIONS" or not enable
On 9/13/2018 6:13 PM, Fabian Grünbichler wrote:
> On Thu, Sep 13, 2018 at 04:08:03PM +0700, The Anh Tran wrote:
>> Dear Teams,
>> I've followed Fabian's instruction, and build process is success.
> that's a good start ;)
>> It turns out that: submodules/ubuntu-bionic downloading by build script, is
>> different than git clone
> no it's not, modulo some different tracking in .git under the hood.
>> Minor suggestion: please update this tutorial
>> I'm testing my modification on this source.
> that tutorial is not written by us ;) but it also does not at any point
> say to copy separately cloned git repositories into sub directories of
> the local clone of pve-kernel.git . the purpose of cloning the ubuntu
> bionic mirror into a separate checkout is to have a clear separation for
> working on your changes - you just need to put the final patch into your
> copy of pve-kernel.git, not manually copy the whole modified kernel
> I suggest we follow up in the forum thread instead of here on pve-devel.
> pve-devel mailing list
> pve-devel at pve.proxmox.com
This email has been checked for viruses by Avast antivirus software.
More information about the pve-devel