Description of problem: Currently, when using WebAdmin - manage vGPU dialog, there is an option for adding only one vGPU mdev_type to VM while manually it is possible to add more than one vGPU mdev_type to VM. It would be nice to have the same functionality in manage vGPU dialog. For example: Using Nvidia Tesla M60 card, mdev_type nvidia-11 is supporting max_instance=16, so manage vGPU dialog should support up to 16 instances for nvidia-11: mdev_type: nvidia-11 --- description: num_heads=2, frl_config=45, framebuffer=512M, max_resolution=2560x1600, max_instance=16 --- name: GRID M60-0B Also, in manage vGPU dialog, the first column name should be changed from "card name" to "mdev type" Version-Release number of selected component (if applicable): ovirt-engine-4.4.1.8-0.7.el8ev Steps to Reproduce: 1. Browse WebAdmin -> Compute -> Virtual machines -> click on VM name -> host devices -> click on manage vGPU button 2. 3. Actual results: There is an option for assigning only 1 mdev_type instance to VM. Expected results: It should be possible to assign max_instance of mdev_type to VM. Additional info: Screenshot attached.
Created attachment 1702423 [details] scrrenshot of manage vGPU dialog
Verified: ovirt-engine-4.4.7.6-0.11.el8ev vdsm-4.40.70.6-1.el8ev.x86_64 libvirt-daemon-7.0.0-14.1.module+el8.4.0+11095+d46acebf.x86_64 qemu-kvm-5.2.0-16.module+el8.4.0+11536+725e25d9.2.x86_64 NVIDIA-vGPU-rhel-8.4-460.73.02.x86_64 Verification scenario: 1. From manage vGPU dialog, Verify it is possible to add multiple vGPU instances to the same VM. 2. Run VM. 3. Verify VM is running and all vGPU instances are listed under VM nvidia-smi shell command.
This bugzilla is included in oVirt 4.4.7 release, published on July 6th 2021. Since the problem described in this bug report should be resolved in oVirt 4.4.7 release, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report.