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 prompt "qxl_cursor: not implemented: type 1" when boot Win2008R2 guest

Version-Release number of selected component (if applicable):
kerne-3.10.0-931.el7.x86_64
qemu-kvm-rhev-2.12.0-9.el7.x86_64
virtio-win:virtio-win-1.9.4-2.el7

How reproducible:
3/3

Steps to Reproduce:
1. Boot up Win2008R2 guest with qemu command line[1]


Actual results:
(qemu) qxl_cursor: not implemented: type 1
qxl_cursor: not implemented: type 1
qxl_cursor: not implemented: type 1


Expected results:
No qxl message output

Additional info:

It's SPICE_CURSOR_TYPE_MONO.  /me looks surprised that windows actually used that.  These days SPICE_CURSOR_TYPE_ALPHA is common ...

Message comes from local renderer, used for screendumps and vnc server.  screendumps have no cursor anyway.  So this only has a visible effect in case one runs qxl with vnc, which is not recommended anyway.  Also not a regression.

Setting to low priority, moving to 7.7.

I ran into this as well, not just with VNC but also GTK. The AND mask ('mask') and XOR mask ('image') respectively for the affected cursor:
//////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////8=
AAAAAAAAAAAB3AAAACAAAAAgAAAAIAAAACAAAAAgAAAAIAAAACAAAAAgAAAAIAAAACAAAAAgAAAAIAAAACAAAAAgAAAB3AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA=

I'll post a patch to the qemu-devel list.

https://patchwork.ozlabs.org/patch/965487/

upstream commit 36ffc122dcd69ab66db4afab3a13cfca46bfc323 (qemu 3.1)

Given this is a low priority with minimal impact, I'm closing this as NEXTRELEASE. It'll be included after a rebase in RHEL8, soon enough.

Peter Wu: thanks for the upstream patch.