NE_ERR_FULL_CORES_NOT_USED(9)

hey bestie 💖 welcome to the NE_ERR_FULL_CORES_NOT_USED(9) page in the Kernel API Manual — it's short, it's iconic, and it's literally here to explain this one Nitro Enclaves error code. no cap.

✨ NAME ✨

NE_ERR_FULL_CORES_NOT_USED — the command to start an enclave is triggered and full CPU cores are not set.

🌸 SYNOPSIS 🌸

NE_ERR_FULL_CORES_NOT_USED

that's the whole synopsis, bestie. one constant, zero extra drama. periodt. 💅

🦋 SEE ALSO 🦋

okay this is the see-also squad, and every single one is exactly as written:

• Kernel file ./include/uapi/linux/nitro_enclaves.h
• Nitro Enclaves (NE) Kernel Driver Interface(9)
• NE_CREATE_VM(9)
• NE_ADD_VCPU(9)
• NE_GET_IMAGE_LOAD_INFO(9)
• NE_SET_USER_MEMORY_REGION(9)
• NE_START_ENCLAVE(9)
• NE specific error codes(9)
• NE_ERR_VCPU_ALREADY_USED(9)
• NE_ERR_VCPU_NOT_IN_CPU_POOL(9)
• NE_ERR_VCPU_INVALID_CPU_CORE(9)
• NE_ERR_INVALID_MEM_REGION_SIZE(9)
• NE_ERR_INVALID_MEM_REGION_ADDR(9)
• NE_ERR_UNALIGNED_MEM_REGION_ADDR(9)
• NE_ERR_MEM_REGION_ALREADY_USED(9)
• NE_ERR_MEM_NOT_HUGE_PAGE(9)
• NE_ERR_MEM_DIFFERENT_NUMA_NODE(9)
• NE_ERR_MEM_MAX_REGIONS(9)
• NE_ERR_NO_MEM_REGIONS_ADDED(9)
• NE_ERR_NO_VCPUS_ADDED(9)
• NE_ERR_ENCLAVE_MEM_MIN_SIZE(9)
• NE_ERR_NOT_IN_INIT_STATE(9)
• NE_ERR_INVALID_VCPU(9)
• NE_ERR_NO_CPUS_AVAIL_IN_POOL(9)
• NE_ERR_INVALID_PAGE_SIZE(9)
• NE_ERR_INVALID_FLAG_VALUE(9)
• NE_ERR_INVALID_ENCLAVE_CID(9)
• Image load info flags(9)
• NE_EIF_IMAGE(9)
• struct ne_image_load_info(9)
• User memory region flags(9)
• NE_DEFAULT_MEMORY_REGION(9)
• struct ne_user_memory_region(9)
• Enclave start info flags(9)
• NE_ENCLAVE_PRODUCTION_MODE(9)
• NE_ENCLAVE_DEBUG_MODE(9)
• struct ne_enclave_start_info(9)

mwah 💋 this page lives at ./include/uapi/linux, dated October 2026, and yes it's still NE_ERR_FULL_CORES_NOT_USED(9) — stay hydrated and go read the rest of the squad, bestie 🫶✨