-
Notifications
You must be signed in to change notification settings - Fork 176
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
HostDev Option Unresponsive in Child Nodes #2035
Comments
Nice report. Host devices in nodes development was started a few months ago in the branch feat/hostdev_nodes. We will keep working from there. Thanks @rajpatel-msstate |
Thank you so much! I am excited to use this feature in my environment. |
frankiejol
added a commit
that referenced
this issue
May 6, 2024
frankiejol
added a commit
that referenced
this issue
May 6, 2024
frankiejol
added a commit
that referenced
this issue
May 6, 2024
frankiejol
added a commit
that referenced
this issue
May 9, 2024
frankiejol
added a commit
that referenced
this issue
May 10, 2024
frankiejol
added a commit
that referenced
this issue
May 27, 2024
Completely refactored the host devices in v2.3. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
I have several child nodes in the environment. In the left-hand option for the child node, you will see an option for "hostdev". This option will allow to add the host device present on your child node to be added to the VM. I wanted to test out the functionality of "GPU Mediated Device" to vGPU instances that are already present on one of the child node. When clicking to "Add Host Device", I see no response/device being created under any of the child nodes. I have tested this functionality under the "master" node, and it works just fine there.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
These are the same steps that I followed on the "master" node, and I see the devices being created. My guess is that it's only becomes unresponsive for the child nodes.
Screenshots







Please let me know if I can provide any other information to provide more insight on this bug report!
The text was updated successfully, but these errors were encountered: