Bug 1729424 - improve handling of unmanaged/missing video devices
Summary: improve handling of unmanaged/missing video devices
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: BLL.Virt
Version: 4.3.5
Hardware: Unspecified
OS: Unspecified
Target Milestone: ovirt-4.4.1
: ---
Assignee: Tomasz Barański
QA Contact: Nisim Simsolo
Depends On:
TreeView+ depends on / blocked
Reported: 2019-07-12 08:50 UTC by Michal Skrivanek
Modified: 2020-07-08 08:25 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
Last Closed: 2020-07-08 08:25:52 UTC
oVirt Team: Virt
pm-rhel: ovirt-4.4+
pm-rhel: ovirt-4.5?

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
oVirt gerrit 101777 0 master MERGED core: Ensure video device exists 2020-07-10 14:11:22 UTC

Description Michal Skrivanek 2019-07-12 08:50:20 UTC
better to always send video model=none when there's no managed video device. Otherwise libvirt adds cirrus which we no longer support

Comment 1 Nisim Simsolo 2019-09-26 10:27:57 UTC
2 X Nvidia Tesla M60 under the same host with Nvidia Grid 9.1 GA drivers.

Verification scenario:
1. Prepare the next VMs:
RHEL 7 VM with mdev-type nvidia-18
Windows 10 VM with 3 mdev_type of nvidia-22
2. Run VMs.
For each of the next steps:
Verify VMs are running with Video model type="none" (observe vdsm.log VM XML or using virsh dumpxml command)
Verify VNC console is showing VMs display.
Verify Nvidia instances are assigned to VMs properly.
3. Power off -> run VMs 10 times.
4. Shutdown -> run VMs 10 times.
5. Reboot VMs 10 times.
6. Remove mdev_type instances from the VM and run VMs.
Verify QXL device is now listed in VM XML video section.
Verify VNC console is showing VM display.
7. Power off VMs, add mdev_type to VMs, run VMs and verify VMs Video model type is "none".

Comment 2 Sandro Bonazzola 2020-07-08 08:25:52 UTC
This bugzilla is included in oVirt 4.4.1 release, published on July 8th 2020.

Since the problem described in this bug report should be resolved in oVirt 4.4.1 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.

Note You need to log in before you can comment on or make changes to this bug.