RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1876297 - Setting "ramfb='on'" in the mdev device does not save in the guest xml and only works once
Summary: Setting "ramfb='on'" in the mdev device does not save in the guest xml and on...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: libvirt
Version: 8.3
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: rc
: 8.0
Assignee: Jonathon Jongsma
QA Contact: yafu
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-09-07 03:08 UTC by Fangge Jin
Modified: 2021-05-18 15:22 UTC (History)
11 users (show)

Fixed In Version: libvirt-6.0.0-31.el8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1847791
Environment:
Last Closed: 2021-05-18 15:21:44 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Comment 4 Jonathon Jongsma 2020-11-09 19:31:06 UTC 
Here's the upstream commit that would need to be backported to fix the bug.

commit c5815b31976f3982d18c7f6c1367ab6e403eb7eb
Author: Jonathon Jongsma <jjongsma>
Date:   Tue Jun 23 13:29:56 2020 -0500

    qemu: format 'ramfb' attribute for mediated devices
    
    It's possible to use ramfb as the boot display of an assigned vgpu
    device. This was introduced in 4b95738c, but unfortunately the attribute
    was not formatted into the xml output for such a device. This patch
    fixes that oversight and adds a xml2xml test to verify proper behavior.
    
    https://bugzilla.redhat.com/show_bug.cgi?id=1847791
    
    Signed-off-by: Jonathon Jongsma <jjongsma>
    Reviewed-by: Daniel Henrique Barboza <danielhb413>
    Signed-off-by: Ján Tomko <jtomko>
    Reviewed-by: Ján Tomko <jtomko>
Comment 8 yafu 2020-12-24 03:20:22 UTC 
Verified with libvirt-daemon-6.0.0-32.module+el8.4.0+9172+b707c649.x86_64.

Test steps:
1.Edit guest xml to set mdev device with "ramfb='on'":
#virsh edit vm1
...
 <hostdev mode='subsystem' type='mdev' managed='no' model='vfio-pci' display='on' ramfb='on'>
      <source>
        <address uuid='49bf2346-6747-4ad6-be5a-adc2f0a10b5c'/>  
    </source>
    <alias name='ua-0febf033-9953-40e1-b803-2df42b0bac4e'/>
</hostdev>
...

2.Check the guest xml, there is 'ramfb' setting in the mdev device:
# virsh dumpxml vm1 | grep -A7 mdev
    <hostdev mode='subsystem' type='mdev' managed='no' model='vfio-pci' display='on' ramfb='on'>
      <source>
        <address uuid='49bf2346-6747-4ad6-be5a-adc2f0a10b5c'/>
      </source>
      <alias name='ua-0febf033-9953-40e1-b803-2df42b0bac4e'/>
      <address type='pci' domain='0x0000' bus='0x07' slot='0x00' function='0x0'/>
    </hostdev>

3.Start the guest again:
# virsh start vm1
Domain vm1 started

4.Check the guest xml, 'ramfb' setting still in the mdev device:
# virsh dumpxml vm1 | grep -A7 mdev
  <hostdev mode='subsystem' type='mdev' managed='no' model='vfio-pci' display='on' ramfb='on'>
      <source>
        <address uuid='49bf2346-6747-4ad6-be5a-adc2f0a10b5c'/>
      </source>
      <alias name='ua-0febf033-9953-40e1-b803-2df42b0bac4e'/>
      <address type='pci' domain='0x0000' bus='0x07' slot='0x00' function='0x0'/>
    </hostdev>

5.Check the qemu cmd line, can see the 'ramfb' setting:
#ps aux | grep -i ramfb
...-device vfio-pci-nohotplug,id=ua-0febf033-9953-40e1-b803-2df42b0bac4e,sysfsdev=/sys/bus/mdev/devices/49bf2346-6747-4ad6-be5a-adc2f0a10b5c,display=on,bus=pci.7,addr=0x0,ramfb=on...

6.Destroy the guest:
#virsh destroy vm1

7.Start the guest:
#virsh start vm1

8.Check the qemu cmd line:
#ps aux | grep -i ramfb
...-device vfio-pci-nohotplug,id=ua-0febf033-9953-40e1-b803-2df42b0bac4e,sysfsdev=/sys/bus/mdev/devices/49bf2346-6747-4ad6-be5a-adc2f0a10b5c,display=on,bus=pci.7,addr=0x0,ramfb=on...
Comment 10 errata-xmlrpc 2021-05-18 15:21:44 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Moderate: virt:rhel and virt-devel:rhel security, bug fix, and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2021:1762
Note You need to log in before you can comment on or make changes to this bug.