Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Description of problem:
Qemu-kvm-rhev supports max_outputs option for virtio video,but libvirt doesn't support.
Version-Release number of selected component:
libvirt-3.2.0-4.el7.x86_64
qemu-kvm-rhev-2.9.0-3.el7.x86_64
How reproducible:
100%
Steps to Reproduce:
1. Prepare a guest with video element as below:
# virsh dumpxml rhel7.4
...
<video>
<model type='virtio' heads='4' primary='yes'/>
<alias name='video0'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/>
</video>
2. Start guest:
# virsh start rhel7.4
3. Check qemu command line:
# ps aux|grep virtio-vga
-device virtio-vga,id=video0,bus=pci.0,addr=0x2
Actual results:
As step3, no max_outputs in qemu command line
Expected results:
In step3, there should be max_outputs in qemu command line:
-device virtio-vga,max_outputs=4,id=video0,bus=pci.0,addr=0x2
Additional info:
Qemu-kvm-rhev supports max_outputs:
# /usr/libexec/qemu-kvm -device virtio-vga,max_outputs=3
VNC server running on ::1:5900
Comment 1Martin Kletzander
2017-08-23 12:16:10 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, 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/RHEA-2018:0704
Description of problem: Qemu-kvm-rhev supports max_outputs option for virtio video,but libvirt doesn't support. Version-Release number of selected component: libvirt-3.2.0-4.el7.x86_64 qemu-kvm-rhev-2.9.0-3.el7.x86_64 How reproducible: 100% Steps to Reproduce: 1. Prepare a guest with video element as below: # virsh dumpxml rhel7.4 ... <video> <model type='virtio' heads='4' primary='yes'/> <alias name='video0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/> </video> 2. Start guest: # virsh start rhel7.4 3. Check qemu command line: # ps aux|grep virtio-vga -device virtio-vga,id=video0,bus=pci.0,addr=0x2 Actual results: As step3, no max_outputs in qemu command line Expected results: In step3, there should be max_outputs in qemu command line: -device virtio-vga,max_outputs=4,id=video0,bus=pci.0,addr=0x2 Additional info: Qemu-kvm-rhev supports max_outputs: # /usr/libexec/qemu-kvm -device virtio-vga,max_outputs=3 VNC server running on ::1:5900