Bug 1958081 - [RFE] Enable ramfb for mdev with display=on
Summary: [RFE] Enable ramfb for mdev with display=on
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: BLL.Virt
Version: 4.4.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ovirt-4.4.7
: 4.4.7
Assignee: Milan Zamazal
QA Contact: Nisim Simsolo
URL:
Whiteboard:
Depends On: 1679680
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-05-07 06:57 UTC by Arik
Modified: 2021-07-06 07:28 UTC (History)
4 users (show)

Fixed In Version: ovirt-engine-4.4.7
Clone Of:
Environment:
Last Closed: 2021-07-06 07:28:28 UTC
oVirt Team: Virt
Embargoed:
sbonazzo: ovirt-4.4?
pm-rhel: planning_ack?
pm-rhel: devel_ack+
pm-rhel: testing_ack+


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 5133771 0 None None None 2021-05-07 07:43:06 UTC
oVirt gerrit 114876 0 master MERGED core: Set ramfb=on for vGPUs with display=on 2021-05-25 13:16:36 UTC

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.


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