Node Option Not Available in version 2.2.0 about ravada

[rajpatel-msstate]

Thank you very much @rajpatel-msstate for your accurate bug report. We provided test and fix for this problem just released on v2.2.1.

You're welcome! Thank you for your work on this Project and making it available to all of us.

[frankiejol]

Thank you very much @rajpatel-msstate for your accurate bug report. We provided test and fix for this problem just released on v2.2.1.

[rajpatel-msstate]

May I enquire about one more thing? I see the option for "GPU Mediated Device". Is this feature available in version 2.2.1 or will it be implemented in the next release?

[frankiejol]

Glad you noticed !
GPU mediated devices are supported in this release. We have not provided documentation nor announced this feature because we want to test it and document it properly. Notice you need NVIDIA hardware that supports grid. Also you have to manage the GPU and partition the devices manually from the OS using mdevctl.
Feel free to try it, feedback is appreciated.

[rajpatel-msstate]

Thank you so much for the information! I will gladly give it a try and will let you know if I am not able to make it work. We do have all the pre-requisites you mentioned in our environment.

[frankiejol]

The packages uploaded were not correct. We just put the correct v2.2.1 final release. Sorry for the inconvenience.

[rajpatel-msstate]

No worries at all! I will get the latest v2.2.1 installed and give it a try again. Thank you again.

[rajpatel-msstate]

May I please contact you via your university email? It seems that I am not able to use any of the "hostdev" functionality on any of my "child" nodes except of the "master" node.

[frankiejol]

Please contact me directly if you have my email. We have yet to test this feature with nodes, so it is likely you spotted a problem already. Anyway, please open a new issue and we can add more official comments.

[rajpatel-msstate]

Please contact me directly if you have my email. We have yet to test this feature with nodes, so it is likely you spotted a problem already. Anyway, please open a new issue and we can add more official comments.

I do have your email, but I think you are right that I should submit this in the GitHub issue. Please see the newly submitted bug report at: #2035 (comment)