I checked to same kernel in an instance with memory=2048 and it just works.
Using todays kernel also works woth memory=2048.
Using memory=65536 for the xen instance gives a surprising familiar
TEST-A# modload bpfjit
[ 97.4727034] kobj_load, 444: [%M/bpfjit/bpfjit.kmod]: linker error:
out of memory
modload: bpfjit: Cannot allocate memory
TEST-A#
So it seems to be linked to available memory.
The more you have the less you get for modload.
Frank
On 05/07/20 22:52, Manuel Bouyer wrote:
On Thu, May 07, 2020 at 09:50:18PM +0200, Frank Kardel wrote:
see here:
Alpine: 21:45 ~ [8] sysctl kern.module.path
kern.module.path = /stand/amd64-xen/9.99.60/modules
looks good
Alpine: 21:46 ~ [9] ll /stand/amd64-xen/9.99.60/modules/bpfjit/bpfjit.kmod
-r--r--r-- 1 root wheel 34328 May 5 16:58
/stand/amd64-xen/9.99.60/modules/bpfjit/bpfjit.kmod
Alpine: 21:46 ~ [10] size
/stand/amd64-xen/9.99.60/modules/bpfjit/bpfjit.kmod
text data bss dec hex filename
10399 0 0 10399 289f
/stand/amd64-xen/9.99.60/modules/bpfjit/bpfjit.kmod
Alpine: 21:46 ~ [11] ll
/stand/amd64-xen/9.99.60/modules/pciverbose/pciverbose.kmod
-r--r--r-- 1 root wheel 140600 May 5 16:55
/stand/amd64-xen/9.99.60/modules/pciverbose/pciverbose.kmod
Alpine: 21:47 ~ [12] size
/stand/amd64-xen/9.99.60/modules/pciverbose/pciverbose.kmod
text data bss dec hex filename
132575 16 0 132591 205ef
/stand/amd64-xen/9.99.60/modules/pciverbose/pciverbose.kmod
no problem for me, with sources from today:
xen1:/#modload bpfjit
xen1:/#modstat | grep !$รถ
modstat | grep bpfjit
bpfjit misc filesys - 0 9174 sljit
xen1:/#modload pciverbose
xen1:/#modstat | grep !$
modstat | grep pciverbose
pciverbose misc filesys - 0 218 pci