Comment 3 for bug 1897424

The logs in c#0 are of a MessagingTimeout raised on n-api.

As I said in c#1 if we have somehow created the bdm in n-cpu and still timed out when replying to n-api then it suggests there's an issue within reserve_block_device_name. Can you please provide logs from the n-cpu process on the other side of this so we can trace why this is timing out in your env?