Bug 1958081

Summary:	[RFE] Enable ramfb for mdev with display=on
Product:	[oVirt] ovirt-engine	Reporter:	Arik <ahadas>
Component:	BLL.Virt	Assignee:	Milan Zamazal <mzamazal>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Nisim Simsolo <nsimsolo>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	4.4.0	CC:	bugs, gveitmic, mavital, nsimsolo
Target Milestone:	ovirt-4.4.7	Keywords:	FutureFeature, ZStream
Target Release:	4.4.7	Flags:	sbonazzo: 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	Doc Type:	Enhancement
Doc Text:	When a vGPU is used and nodisplay is not specified, an additional framebuffer display device is added to the VM now, allowing to display the VM console before the vGPU is initialized. This allows display console access during boot, instead of having just a blank screen there as before this change. This works only on cluster levels >= 4.5. It is possible to disable the feature by setting VgpuFramebufferSupported Engine config value to false.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-07-06 07:28:28 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:	1679680
Bug Blocks:

Description Arik 2021-05-07 06:57:49 UTC

By enabling ramfb when using vgpu with display=on we can prevent getting blank consoles when the vgpu driver is not loaded [1].

The idea here is that when 'nodisplay' is not specified (i.e., display=on) to also enable ramfb. The video device would remain with model.type=none as we do already.

Need to pay attention to the cluster levels in which we can do this (compatibility versions 4.5 and 4.6 - see bz 1679680).

The handling of the 'nodisplay' argument should stay as is (as fallback).

[1] https://www.kraxel.org/blog/2019/02/ramfb-display-in-qemu/

Comment 1 Nisim Simsolo 2021-06-16 13:44:30 UTC

Verification builds:
ovirt-engine-4.4.7.1-0.9.el8ev
vdsm-4.40.70.2-1.el8ev.x86_64
qemu-kvm-5.2.0-16.module+el8.4.0+10806+b7d97207.x86_64
libvirt-daemon-7.0.0-14.module+el8.4.0+10886+79296686.x86_64
NVIDIA-vGPU-rhel-8.4-460.73.02.x86_64

Verification scenario:
Polarion test case added to links section.

Comment 2 Sandro Bonazzola 2021-07-06 07:28:28 UTC

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.