So as the title stays, i compiled a pretty large kernel with lots of added drives. Problem is when i try to post it say that it is out of memory and goes back to the grub menu.

Tried with both initramfs and without. Not using kernel modules....

Not sure why this is happening i have 256GB of ram so i know its not that. I think there is a timeout iam hitting our a memory limit for the kernel to use during boot.

Does anyone know how to fix this?

Not finding anything clear on Google. So as usually, i figured id ask the smartest Linux community out there.

Smart or not, I guess they'll request way more specific info...

Ya in general not the smartest for everyday use but iam working on a project and i need lots of built in kernel drivers without an initramfs at the end of the day.

Long story...

Mainly need the Ethernet and raid cards, just happened to find something on vm.oom-kill = 0. Just added it to my sysctl.conf gonna recompile and try again.

Guessing it wont work, but who knows.

Ive also seen other issues when allocating alot of memory to QEMU like 100+GB to a VM. It times out when allocating memory to the VM.

Like i can watch the memory slowly go up to past 100GB in HTOP than QEMU times out. Anyway i know its not as the message says and can be fixed, just need to figure out how.

Hugepages solved my issue for that though..... But this is different.

Another OP that forgets to mention that they have problems with a VM, not bare metal.
I don't use QEMU but in virtualbox there's a setting how much resources of the host system the vm may use.

Either way, we still need way more info.

Its strictly kernel related with some of the drivers that are being built in. I think i have bypassed some software memory limit in the kernel.

This is without any VM software running and its a message that comes directly on the kernel booting screen prior to init fully running.