The pool_pop_page() error

You can give parameters to Ramooflax modules. For the time being, only one parameter is supported pool.

Sometimes, on Intel CPU supporting very wide physical addresses (say 52 bits), Ramooflax needs a large memory pool to allocate enough page tables in order to properly reflect MTRR settings to EPT entries.

Depending on the range defined by the MTRRs a huge amount of pdpe/pde/pte can be needed.

If you experience the following debug trace while Ramooflax is booting:

------ Stack Trace [rsp: 0xXXXXX | rip 0xXXXXX]
xxxxx
xxxxx
xxxxx
xxxxx
:: EVIL :: __npg_new_pg() :: pool_pop_page()

This means that the vmm allocator needs more physical memory pages in its pool to map MTRRs to EPTs entries during setup.

Simply modify your GRUB menu entry as follows:

module /vmm.bin pool=2000

The given number to the pool parameter is the number of physical 4KB pages that will be allocated into the vmm pool.