Bug 1849409

Summary: video device is missing
Product: [oVirt] ovirt-engine Reporter: Liran Rotenberg <lrotenbe>
Component: BLL.VirtAssignee: Liran Rotenberg <lrotenbe>
Status: CLOSED CURRENTRELEASE QA Contact: Qin Yuan <qiyuan>
Severity: high Docs Contact:
Priority: unspecified    
Version: 4.4.1.4CC: ahadas, bugs, lsvaty
Target Milestone: ovirt-4.4.1Flags: pm-rhel: ovirt-4.4+
Target Release: 4.4.1.5   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: ovirt-engine-4.4.1.5 Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-07-08 08:25:00 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:

Description Liran Rotenberg 2020-06-21 13:28:35 UTC
When a VM starts it will be with:
    <video>
      <model type='none'/>
      <alias name='ua-5be74569-9474-4259-8b97-9dc4322c5993'/>
    </video>
Making the console unusable, even when it's set with graphics(vnc/spice) and the qxl/vnc device is set (also in the VM device DB).

Reproduce:
1. Create a VM with graphics(spice+vnc) and QXL.
2. Start the VM.
3. Trigger console to the VM

You won't see the VM console, also in the domxml the video device set with type='none'.


Additional info:
When we create a VM we check the custom properties of that VM.
If it includes 'mdev_type' we set boolean for further logic, making the type='none' if mdev is in use.
Currently we are getting this boolean as true even when there is no mdev_type custom property.

Comment 1 Qin Yuan 2020-07-07 15:00:44 UTC
Verified with:
ovirt-engine-4.4.1.7-0.3.el8ev.noarch

Steps:
1. Create a VM with graphics(spice+vnc) and QXL.
2. Start the VM.
3. Trigger console to the VM

Results:
1. The video type in domxml is qxl:
    <video>
      <model type='qxl' ram='65536' vram='8192' vgamem='16384' heads='1' primary='yes'/>
      <alias name='ua-5a136d30-0da9-4549-892f-6949c0cf05e8'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x0'/>
    </video>
2. The VM console works normally.

Comment 2 Sandro Bonazzola 2020-07-08 08:25:00 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.