PPisz commented on issue #5405: URL: https://github.com/apache/cloudstack/issues/5405#issuecomment-924626952
Very good idea. - The installation of NVIDIA software on the KVM side should be on the Administrator side. - GPU Offering should allow you to define NVIDIA vGPU profile, (this information can be easily retrieved from the appropriate path) e.g .: nvidia-355 - CUDA - num_heads=4, frl_config=60, framebuffer=1024M, max_resolution=5120x2880, max_instance=32 nvidia-356 - CUDA - num_heads=4, frl_config=60, framebuffer=2048M, max_resolution=7680x4320, max_instance=16 nvidia-357 - CUDA - num_heads=4, frl_config=60, framebuffer=4096M, max_resolution=7680x4320, max_instance=8 nvidia-358 - CUDA - num_heads=4, frl_config=60, framebuffer=8192M, max_resolution=7680x4320, max_instance=4 nvidia-359 - CUDA - num_heads=4, frl_config=60, framebuffer=16384M, max_resolution=7680x4320, max_instance=2 nvidia-360 - CUDA - num_heads=4, frl_config=60, framebuffer=32768M, max_resolution=7680x4320, max_instance=1 - The list of generated UUIDs for the vGPU can be passed to the CS or the CS can generate the vGPU - The whole process should allow you to connect a vGPU device as offering (compute type), not as extraconfig. - The dasboard should show the amount of used / max vGPU The manual vGPU connection process is described here: https://lab.piszki.pl/cloudstack-kvm-and-running-vm-with-vgpu/ Automation should allow you to use GPU Offering instead of extraconfig, that's enough. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
