NE_ERR_VCPU_ALREADY_USED(9)

🦋 NE_ERR_VCPU_ALREADY_USED(9) 🦋

okay so bestie, this is a page from the Kernel API Manual, and it's here to explain the NE_ERR_VCPU_ALREADY_USED error code. No cap, it's a short one, but it still ate. 💅

🌸 NAME 🌸

NE_ERR_VCPU_ALREADY_USED — The provided vCPU is already used.</p> Like, you showed up with a vCPU and it's already clocked in somewhere else 😭 that's the whole vibe.

✨ SYNOPSIS ✨

NE_ERR_VCPU_ALREADY_USED

Literally just the constant, bestie. 🫶

🎀 SEE ALSO 🎀

these are the related pages and references, all lined up and looking iconic:

• 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_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_FULL_CORES_NOT_USED(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)

sign-off time: this page comes from the source/version path ./include/uapi/linux, dated October 2026, and the page name is NE_ERR_VCPU_ALREADY_USED(9). mwah 💋✨