Hi Andrija, I'm writing because you've previously sent patches for virt-v2v, and also because of your (positive, thanks!) comments about nbdkit in The Register[1]. You may not have seen it, but after VMware dropped VDDK I proposed deprecating the nbdkit vddk plugin: https://gitlab.com/nbdkit/nbdkit/-/commit/b8284518411a54bfc0f5ac54d7346ed259... This decision is not final, and it was made before OpenVDDK was open sourced. But also we are considering dropping VDDK support in RHEL 11 (but we are _not_ dropping it upstream in virt-v2v), so there would be less commercial interest from our end. Anyway ... my question is whether you would like to take over maintenance of this plugin *out of tree* (ie in your own git repo). Nbdkit offers a stable API & ABI, and since the plugin uses this API/ABI, out of tree plugins are well supported. Of course there would still be the general burden of looking the plugin itself. You might be able to adapt the plugin to work better with OpenVDDK, since I suppose that in the long term OpenVDDK might be the only consumer. Anyway let me know if this is something you'd like to do. In practical terms it would mean deleting the plugin from the nbdkit tree during the next stable release, and replacing it with a link to the out of tree repository. If you don't want to do this, no problem at all also. Rich. [1] https://www.theregister.com/virtualization/2026/11/03/architect-creates-open...