Minor page faults - cryptocurrencies need "Gitian building" to work on LXC?

All these (popular) cryptocurrencies have a guide for LXC setup

It involves gitian build

I have tried to run them (without gitian, by just using the pre-made release binaries) and I experience lots of “minor page faults”

Minor page faults?
There is also a special case scenario called a minor page fault which occurs when the code (or data) needed is actually already in memory, but it isn’t allocated to that process. For example, if a user is running a web browser then the memory pages with the browser executable code can be shared across multiple users (since the binary is read-only and can’t change). If a second user starts the same web browser then Linux won’t load all the binary again from disk, it will map the shareable pages from the first user and give the second process access to them. In other words, a minor page fault occurs only when the page list is updated (and the MMU configured) without actually needing to access the disk. A minor page fault is your friend requesting to read your checked out copy of The Two Towers and you saying “hey, lets just make a copy of mine!” OR you returning a book, but then immediately checking it out again before the book was even returned to a shelf. source: Understanding page faults and memory swap-in/outs: when should you worry? | Scout APM Blog

You can see them in top when you press f navigate to nMin = Minor Page Faults and press space to activate then esc to go back to top

With this enabled in top I see nMin always rising and rising and rising along with VIRT = Virtual Image (KiB) to the point that VERT gets huge (GB) and also keeps rising
up to the point that the daemon process hangs

LXD should be able to run processes just as well as any system does (without needing special building) so is this as simple as allowing allocation by adding the process to the lxc cgroup or something?

Gitian is a mess to get working and I would think that it was needed in the early days of LXC but surely not after all these years of improvements.

PS: I had all these minor page faults with a 10GB Swapfile configured

sounds like this kvm issue OSDev.org • View topic - KVM page fault exceptions

lxc-checkconfig
LXC version 5.0.0~git2209-g5a7b9ce67
Kernel configuration not found at /proc/config.gz; searching…
Kernel configuration found at /boot/config-5.15.0-47-generic
— Namespaces —
Namespaces: enabled
Utsname namespace: enabled
Ipc namespace: enabled
Pid namespace: enabled
User namespace: enabled
Network namespace: enabled

— Control groups —
Cgroups: enabled
Cgroup namespace: enabled

Cgroup v1 mount points:

Cgroup v2 mount points:
/sys/fs/cgroup

Cgroup v1 systemd controller: missing
Cgroup v1 freezer controller: missing
Cgroup ns_cgroup: required
Cgroup device: enabled
Cgroup sched: enabled
Cgroup cpu account: enabled
Cgroup memory controller: enabled
Cgroup cpuset: enabled

— Misc —
Veth pair device: enabled, loaded
Macvlan: enabled, not loaded
Vlan: enabled, not loaded
Bridges: enabled, loaded
Advanced netfilter: enabled, loaded
CONFIG_IP_NF_TARGET_MASQUERADE: enabled, not loaded
CONFIG_IP6_NF_TARGET_MASQUERADE: enabled, not loaded
CONFIG_NETFILTER_XT_TARGET_CHECKSUM: enabled, not loaded
CONFIG_NETFILTER_XT_MATCH_COMMENT: enabled, not loaded
FUSE (for use with lxcfs): enabled, not loaded

— Checkpoint/Restore —
checkpoint restore: enabled
CONFIG_FHANDLE: enabled
CONFIG_EVENTFD: enabled
CONFIG_EPOLL: enabled
CONFIG_UNIX_DIAG: enabled
CONFIG_INET_DIAG: enabled
CONFIG_PACKET_DIAG: enabled
CONFIG_NETLINK_DIAG: enabled
File capabilities:

Note : Before booting a new kernel, you can check its configuration
usage : CONFIG=/path/to/config /usr/bin/lxc-checkconfig

snap --version
snap    2.56.2+22.04ubuntu1
snapd   2.56.2+22.04ubuntu1
series  16
ubuntu  22.04
kernel  5.15.0-47-generic

am I suppose to add systemd.unified_cgroup_hierarchy=1 to grub? @stgraber