what does yours cover? Mine is lavapipe behind vulkan.hidd plus Venus (Mesa's remote driver with an AROS shared-memory transport) and virglrenderer's vkr as venusrenderer.library, so a client in a separate address space can submit to a renderer on a native driver. Venus needed two interface changes: CreateInstance with the full VkInstanceCreateInfo, and a lookup by driver class so the renderer never picks Venus itself. If your lavapipe is already on 26.2.5 and works with interface 2 as is, send yours and I will rebase on it: the interface bump, Venus and the renderer come on top, plus the runtime bits lavapipe needed on my side (acceleration structure builds with their glslang-compiled shaders, memory trace exporter) and a malloc fix (the exec override ignores free() on stdc blocks, llvmpipe lost ~6 MiB per context) if you hit the same. If yours is still on 26.0.0 like mine, I can send lavapipe first and you check it against your native setup. Either way I have VulkanTriangle, a test that checks all 4096 pixels of a quarter-pixel-offset triangle, fence and timeline semaphore, three cycles without leaks; useful for comparing both. Which Mesa and which interface version are you on?