Bug 1860646
| Summary: | [RFE] Manage vGPU dialog, add option for assigning more than one vGPU instance to VM | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [oVirt] ovirt-engine | Reporter: | Nisim Simsolo <nsimsolo> | ||||
| Component: | BLL.Virt | Assignee: | Lucia Jelinkova <ljelinko> | ||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Nisim Simsolo <nsimsolo> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 4.4.1.2 | CC: | ahadas, bugs, dfodor, nsimsolo | ||||
| Target Milestone: | ovirt-4.4.7 | Keywords: | FutureFeature | ||||
| Target Release: | --- | Flags: | pm-rhel:
ovirt-4.4?
pm-rhel: planning_ack? pm-rhel: devel_ack+ pm-rhel: testing_ack+ |
||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | ovirt-engine-4.4.7.5 | Doc Type: | If docs needed, set a value | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2021-07-08 14:15:39 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | Virt | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Bug Depends On: | |||||||
| Bug Blocks: | 1963714 | ||||||
| Attachments: |
|
||||||
|
Description
Nisim Simsolo
2020-07-26 07:30:58 UTC
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. |