Bug 1369633
Summary: | Virtio-gpu should be supported as secondary gpu in libvirt | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | Guo, Zhiyi <zhguo> |
Component: | libvirt | Assignee: | Pavel Hrdina <phrdina> |
Status: | CLOSED ERRATA | QA Contact: | zhe peng <zpeng> |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | 7.3 | CC: | chayang, dyuan, fjin, jdenemar, juzhang, michen, rbalakri, xfu, xuzhang, zhguo, zpeng |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | libvirt-2.5.0-1.el7 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2017-08-01 17:11:42 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: |
Description
Guo, Zhiyi
2016-08-24 03:19:29 UTC
Upstream commit: commit fb8f3b1c22c8f272bb9a47e8f8915acc3cfb47f1 Author: Pavel Hrdina <phrdina> Date: Mon Oct 10 20:19:06 2016 +0200 qemu_command: add support to use virtio as secondary video device v2.3.0-106-gfb8f3b1 verified with build: libvirt-3.1.0-2.el7.x86_64 step: 1. use description xml to create a guest 2.# virsh create virtio.xml Domain rhel7.3 created from virtio.xml check guest xml: .... <video> <model type='virtio' heads='1' primary='yes'/> <alias name='video0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/> </video> <video> <model type='virtio' heads='1'/> <alias name='video1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x09' function='0x0'/> </video> .... check qemu cmd line: ... -device virtio-vga,id=video0,bus=pci.0,addr=0x2 -device virtio-gpu-pci,id=video1,bus=pci.0,addr=0x9 ... move to verified. 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-2017:1846 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-2017:1846 |