Bug 1949004

Summary: Bochs display is not set by default when creating new server VM with UEFI
Product: [oVirt] ovirt-engine Reporter: Nisim Simsolo <nsimsolo>
Component: BLL.VirtAssignee: Shmuel Melamud <smelamud>
Status: CLOSED CURRENTRELEASE QA Contact: Nisim Simsolo <nsimsolo>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 4.4.5.11CC: ahadas, bugs, dfodor, nsimsolo
Target Milestone: ovirt-4.5.1Flags: pm-rhel: ovirt-4.5?
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: ovirt-engine-4.5.1.2 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-06-23 05:54:58 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:
Attachments:
Description Flags
engine.log none

Description Nisim Simsolo 2021-04-13 08:46:25 UTC
Description of problem:
Although EnableBochsDisplay default_value in 4.6 is now set to 'true' by default (in engine db), when creating (from WebAdmin) new server VM with UEFI chipset, the default video type/graphics protocol is QXL/SPICE+VNC instead of bochs/VNC

Version-Release number of selected component (if applicable):
ovirt-engine-4.4.6.3-0.8.el8ev
vdsm-4.40.60.3-1.el8ev.x86_64
libvirt-daemon-7.0.0-13.module+el8.4.0+10604+5608c2b4.x86_64
qemu-kvm-5.1.0-21.module+el8.3.1+10464+8ad18d1a.x86_64

How reproducible:
100%

Steps to Reproduce:
1. From WebAdmin, Create new VM optimized for: server with Q35 UEFI chipset. 
2.
3.

Actual results:
The default video type/graphics protocol is QXL/SPICE+VNC instead bochs/VNC.

Expected results:
The default video type/graphics protocol should be set to bochs/VNC.

Additional info:
engine.log attached (VM created at: 2021-04-13 10:54:11,632+03)

Comment 1 Nisim Simsolo 2021-04-13 08:49:56 UTC
Created attachment 1771567 [details]
engine.log

Comment 2 Arik 2021-06-20 17:27:11 UTC
Also we should change 'bochs' to 'Bochs'

Comment 3 Arik 2022-06-15 13:53:22 UTC
(In reply to Nisim Simsolo from comment #0)
> Actual results:
> The default video type/graphics protocol is QXL/SPICE+VNC instead bochs/VNC.
> 
> Expected results:
> The default video type/graphics protocol should be set to bochs/VNC.

It is ok to take the initial selection of video/graphics from the blank template.
We need to make sure that when either the bios type or the compatibility level or the vm-type changes, we set Bochs/VNC for UEFI + server + CL>4.5

Comment 4 Nisim Simsolo 2022-06-20 14:26:57 UTC
Verified:
ovirt-engine-4.5.1.2-0.11.el8ev
vdsm-4.50.1.3-1.el8ev.x86_64
qemu-kvm-6.2.0-11.module+el8.6.0+15489+bc23efef.1.x86_64
libvirt-8.0.0-5.2.module+el8.6.0+15256+3a0914fe.x86_64

Verification scenario:
1. Create new DC with Compatibility version 4.5 and new Cluster with Compatibility version 4.5.
add host and storage domain.
2. Create new VM and verify that video type/graphics protocol for each chipset firmware type is:
Q35 chipset with UEFI - QXL / VNC
Q35 chipset wirh SecureBoot - QXL / VNC
Q35 chipset with BIOS - QXL / VNC
I440FX chipset with BIOS - QXL / VNC
3. Change VM compatibility version to 4.6 and verify:
Q35 chipset with UEFI - Bochs / VNC
Q35 chipset wirh SecureBoot - Bochs / VNC
Q35 chipset with BIOS - QXL / VNC
I440FX chipset with BIOS - QXL / VNC
4. repeat step 4 for 4.7 compatibility version.
5. Change cluster compatibility version to 4.6 and verify:
Q35 chipset with UEFI - Bochs / VNC
Q35 chipset wirh SecureBoot - Bochs / VNC
Q35 chipset with BIOS - QXL / VNC
I440FX chipset with BIOS - QXL / VNC
6. Repeat step 5 for cluster compatibility version 4.7
7. Run VM with Bochs/VNC and verify VM is running and consolo is showing the VM.

Comment 5 Sandro Bonazzola 2022-06-23 05:54:58 UTC
This bugzilla is included in oVirt 4.5.1 release, published on June 22nd 2022.
Since the problem described in this bug report should be resolved in oVirt 4.5.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.