Bug 1368406
| Summary: | Virtual display of virtio-gpu should behave like qxl device when using rhel7.3 guest | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Guo, Zhiyi <zhguo> |
| Component: | qemu-kvm-rhev | Assignee: | Gerd Hoffmann <kraxel> |
| Status: | CLOSED ERRATA | QA Contact: | Guo, Zhiyi <zhguo> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 7.3 | CC: | chayang, jinzhao, juzhang, knoel, kraxel, michen, mrezanin, virt-maint |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | qemu-kvm-rhev-2.9.0-1.el7 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2017-08-01 23:34: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: | |||
multihead + multiseat is beyond the scope for 7.3, moving to 7.4. (In reply to Gerd Hoffmann from comment #2) > multihead + multiseat is beyond the scope for 7.3, moving to 7.4. host side: qemu 2.8 needed. guest side: kernel with drm driver rebase needed (will probably happen late in the devel cycle). With those multihead should work fine. (In reply to Gerd Hoffmann from comment #3) > (In reply to Gerd Hoffmann from comment #2) > > multihead + multiseat is beyond the scope for 7.3, moving to 7.4. > > host side: qemu 2.8 needed. > guest side: kernel with drm driver rebase needed (will probably happen late > in the devel cycle). > > With those multihead should work fine. Please retest with qemu-2.9 and a fresh up to date RHEL-7.4 kernel. For virtio-vga multiheads support, it has been verified in 1368406 Virtual display of virtio-gpu should behave like qxl device when using rhel7.3 guest. For this bug, if use default options of virtio-gpu, the behavior is same as original report. But landing to qemu-kvm-rhev 2.9，I can override the default options of virtio-gpu to make virtio-gpu behave like qxl:
-device virtio-gpu,max_outputs=0
The default max_outputs of qxl is 0:
dev: qxl, id ""
ram_size = 67108864 (0x4000000)
vram_size = 67108864 (0x4000000)
revision = 4 (0x4)
debug = 0 (0x0)
guestdebug = 0 (0x0)
cmdlog = 0 (0x0)
ram_size_mb = 4294967295 (0xffffffff)
vram_size_mb = 4294967295 (0xffffffff)
vram64_size_mb = 4294967295 (0xffffffff)
vgamem_mb = 16 (0x10)
surfaces = 1024 (0x400)
max_outputs = 0 (0x0)
addr = 03.0
romfile = ""
rombar = 1 (0x1)
multifunction = false
command_serr_enable = true
x-pcie-lnksta-dllla = true
x-pcie-extcap-init = true
class Display controller, addr 00:03.0, pci id 1b36:0100 (sub 1af4:1100)
bar 0: mem at 0xffffffffffffffff [0x3fffffe]
bar 1: mem at 0xffffffffffffffff [0x3fffffe]
bar 2: mem at 0xffffffffffffffff [0x1ffe]
bar 3: i/o at 0xffffffffffffffff [0x1e]
The default max_outputs of virtio-gpu is 1 but can be overrided to 0:
dev: virtio-gpu-pci, id ""
ioeventfd = false
vectors = 3 (0x3)
virtio-pci-bus-master-bug-migration = false
disable-legacy = "on"
disable-modern = false
migrate-extra = true
modern-pio-notify = false
x-disable-pcie = false
page-per-vq = false
x-ignore-backend-features = false
ats = false
x-pcie-deverr-init = true
x-pcie-lnkctl-init = true
x-pcie-pm-init = true
addr = 03.0
romfile = ""
rombar = 1 (0x1)
multifunction = false
command_serr_enable = true
x-pcie-lnksta-dllla = true
x-pcie-extcap-init = true
class Display controller, addr 00:03.0, pci id 1af4:1050 (sub 1af4:1100)
bar 1: mem at 0xffffffffffffffff [0xffe]
bar 4: mem at 0xffffffffffffffff [0x3ffe]
bus: virtio-bus
type virtio-pci-bus
dev: virtio-gpu-device, id ""
max_outputs = 1 (0x1)
max_hostmem = 268435456 (256 MiB)
indirect_desc = true
event_idx = true
notify_on_empty = true
any_layout = true
iommu_platform = false
__com.redhat_rhel6_ctrl_guest_workaround = false
So the bug is verified now
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/RHSA-2017:2392 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/RHSA-2017:2392 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/RHSA-2017:2392 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/RHSA-2017:2392 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/RHSA-2017:2392 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/RHSA-2017:2392 |
Description of problem: Virtual display of virtio-gpu should behave like qxl device when using rhel7.3 guest Version-Release number of selected component (if applicable): qemu-kvm-rhev package:qemu-kvm-rhev-2.6.0-21.el7.x86_64 host & guest kernel: 3.10.0-489.el7.x86_64 virt-viewer: virt-viewer-2.0-11.el7.x86_64 How reproducible: 100% Steps to Reproduce: 1.Boot rhel7.3 guest use qemu cli: /usr/libexec/qemu-kvm -name rhel7.3 -m 2048 \ -cpu Haswell-noTSX \ -smp 6,threads=2,cores=1,sockets=3,maxcpus=6 \ -device virtio-vga\ -device virtio-gpu\ -spice port=5901,disable-ticketing \ -device virtio-serial -chardev spicevmc,id=vdagent,debug=0,name=vdagent \ -serial unix:/tmp/m,server,nowait \ -device virtserialport,chardev=vdagent,name=com.redhat.spice.0 \ -drive file=rhel73.qcow2,if=none,id=drive-scsi-disk0,format=qcow2,cache=none,werror=stop,rerror=stop -device virtio-scsi-pci,id=scsi0,disable-modern=off,disable-legacy=off -device scsi-hd,drive=drive-scsi-disk0,bus=scsi0.0,scsi-id=0,lun=0,id=scsi-disk0,bootindex=1 \ -monitor stdio \ -usb -device usb-kbd,id=input0 \ -netdev tap,id=idinWyYp -device virtio-net-pci,mac=42:ce:a9:d2:4d:d7,id=idlbq7eA,netdev=idinWyYp \ -qmp tcp:localhost:4444,server,nowait \ -device ich9-intel-hda -device hda-duplex \ 2.remote-viewer spice://127.0.0.1:5901 3. Actual results: Guest have two displays after remote-viewer connected and guest cannot use virtio-gpu display to display desktop Expected results: Guest have one display after remote-viewer connected Additional info: Test aginst qxl-vga with multiple qxl devices, only one display present. Attach screenshot to show phenomenon of virtio-vga with virtio-gpu device.