Proposed title of this feature request This feature request is for NVIDIA vGPU support for Guests in RHOSP. * With regards to vGPU device definition do you expect in an initial implementation to allocate them once before activating the compute node or do be able to make (re)allocations when the compute node is active? These GPUs will go on existing Compute nodes. If there is benefit, we are open to rebuild the node to enable additional capabilities with in OSP 8. * Which guest operating systems do you intend to use with vGPU? Mostly RHEL 7 * Which display protocol(s) do you intend to use with vGPU? Protocols used in the backend by CUDA or other use cases around Machine Learning * What are y our scheduling expectations: - Do you require an initial implementation to handle NUMA locality or can they live with out? NUMA locality is needed, may be ok with out it. We need to know when we can enable same. - Do you expect homogenized environments in regards to the specific cards you will use and more importantly the types of vGPU slices you will use or will you be attempting to use different types across the environment. Will use same type of GPUs across - Will you be using NVIDIA cards? Intel cards? Both? In each case, which models. NVIDIA cards in scope right now, P100
I'm updating the title to reflect the difference, nuanced as it may be, between this and Bug # 1360442 which focuses more on technical workstation virtualization use cases. The most immediately obvious differences visible here are: * RHEL workloads (vs Windows workloads). * Lesser importance of remote display protocols. * More likely to require NUMA affinity.
NUMA locality will be treated as a stretch goal for vGPU MVP and tracked separately.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2019:0045