API remoting using the `onnx_dump` or `cudart` fails because the cuda program on the guest calls the API `cuGetExportTable` which is not implemented. about ava

[yuhc]

Hi- Sorry for the late reply. This is a known issue. We haven't supported cuGetExportTable, because it's a non-public API and we don't yet understand its syntax. cuGetExportTable is usually called by some cudnn, cublas APIs, iirc, but it looks odd to me that your sample program also triggers the call.

[Abhishekghosh1998]

@yuhc Thanks for your reply.

I figured out the issue that I was facing with cuGetExportTable​. It was caused by a setup configuration actually. I was compiling the programs with the nvcc​​ command simply as follows:

nvcc -o toy toy.cu​

The above command statically linked the libcudart​ with the executable. As a result, the interception happened at the CUDA driver API (the calls made to the driver API by the runtime API). So, I changed the option accordingly:

​nvcc -o toy toy.cu --cudart shared​

Some runtime API functions might be internally calling that cuGetExportTable​​ function. If the interception is done at the runtime API level, it does not pose an issue because this cuGetExportTable call then gets executed on the host, and the result of the runtime API that makes this call is sent back to the guest.

I would like to thank @hfingler for his guidance, that the issue had something to do with the setup. It gave me the confidence to fine-tune the area to twig accordingly.