Bug 1876297
Summary: | Setting "ramfb='on'" in the mdev device does not save in the guest xml and only works once | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 8 | Reporter: | Fangge Jin <fjin> |
Component: | libvirt | Assignee: | Jonathon Jongsma <jjongsma> |
Status: | CLOSED ERRATA | QA Contact: | yafu <yafu> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 8.3 | CC: | chhu, dyuan, hhan, jdenemar, jjongsma, jsuchane, lmen, virt-maint, xuzhang, yafu, yalzhang |
Target Milestone: | rc | Keywords: | Triaged |
Target Release: | 8.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | libvirt-6.0.0-31.el8 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | 1847791 | Environment: | |
Last Closed: | 2021-05-18 15:21:44 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Comment 4
Jonathon Jongsma
2020-11-09 19:31:06 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... 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 |