Mismatch between available extensions

Vulkan
1

When I use vulkaninfo | grep VK_KHR_external_memory I get that this extension is supported on my device. But when I querry it in C++ through vkEnumerateInstanceExtensionProperties its not in the list. Where can be the problem?

I am using SDK from lunarG via conan package.

Output of the vulkaninfo:

ERROR: [Loader Message] Code 0 : /usr/lib/i386-linux-gnu/libvulkan_radeon.so: wrong ELF class: ELFCLASS32
ERROR: [Loader Message] Code 0 : /usr/lib/i386-linux-gnu/libvulkan_lvp.so: wrong ELF class: ELFCLASS32
ERROR: [Loader Message] Code 0 : /usr/lib/i386-linux-gnu/libvulkan_intel.so: wrong ELF class: ELFCLASS32
ERROR: [Loader Message] Code 0 : /usr/lib/i386-linux-gnu/libvulkan_intel_hasvk.so: wrong ELF class: ELFCLASS32
ERROR: [Loader Message] Code 0 : /usr/lib/i386-linux-gnu/libvulkan_virtio.so: wrong ELF class: ELFCLASS32
WARNING: [Loader Message] Code 0 : terminator_CreateInstance: Failed to CreateInstance in ICD 1.  Skipping ICD.
WARNING: [Loader Message] Code 0 : terminator_CreateInstance: Failed to CreateInstance in ICD 2.  Skipping ICD.
	VK_KHR_external_memory_capabilities    : extension revision 1
	VK_KHR_external_memory                        : extension revision 1
	VK_KHR_external_memory_fd                     : extension revision 1
	VK_KHR_external_memory                        : extension revision 1
	VK_KHR_external_memory_fd                     : extension revision 1

But instance extension is present (VK_KHR_EXTERNAL_MEMORY_CAPABILITIES_EXTENSION_NAME)

2

KHR_external_memory is a device extension, not an instance extension. VK_KHR_external_memory_capabilities is the instance extension that gives you VK_KHR_EXTERNAL_MEMORY_CAPABILITIES_EXTENSION_NAME.

3

Yes, but the device extension VK_KHR_external_memory is present in the vulkaninfo. I mentioned the instance extension hoping it might be relevant.

4

Oh I see I should use

vkEnumerateDeviceExtensionProperties

Problem is that without the check I get:
Fatal : VkResult is "ERROR_EXTENSION_NOT_PRESENT" when creating the device

Tomorrow i will update the check process and post here more relevant/fixed information