This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
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.
Bug 1983860 - [viogpudo] There are two cursor after installing viogpudo driver for virtio-vga&virtio-gpu-pci
Summary: [viogpudo] There are two cursor after installing viogpudo driver for virtio-v...
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: virtio-win
Version: 9.0
Hardware: x86_64
OS: Windows
low
low
Target Milestone: rc
: 9.0
Assignee: Vadim Rozenfeld
QA Contact: dehanmeng
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-07-20 03:41 UTC by dehanmeng
Modified: 2023-08-24 05:14 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-08-15 15:28:30 UTC
Type: ---
Target Upstream Version:
Embargoed:
pm-rhel: mirror+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker   RHEL-1293 0 None Migrated None 2023-08-24 05:13:44 UTC

Description dehanmeng 2021-07-20 03:41:06 UTC 
Description of problem:
After installing viogpudo driver for virtio-vga&virtio-gpu-PCI devices, there are two cursors in the guest. after discussion with the manager, this issue should be opened because this issue causes the user experience to be particularly poor, and customers are easy to report the bug. 

Version-Release number of selected component (if applicable):


How reproducible:
100%

Steps to Reproduce:
1.bootup guest with following qemu command line
/usr/libexec/qemu-kvm -name 204GPU103235RNZ -enable-kvm -m 4G -smp 4 -uuid a21544d0-f972-4f86-a65f-8e45139d3e28 -nodefaults -cpu Skylake-Server,hv_stimer,hv_synic,hv_time,hv_vpindex,hv_relaxed,hv_spinlocks=0x1fff,hv_vapic,hv_frequencies,hv_runtime,hv_tlbflush,hv_reenlightenment,hv_stimer_direct,hv_ipi -chardev socket,id=charmonitor,path=/tmp/204GPU103235RNZ,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=localtime,driftfix=slew -boot order=cd,menu=on -device piix3-usb-uhci,id=usb -blockdev driver=file,cache.direct=off,cache.no-flush=on,filename=204GPU103235RNZ,node-name=my_file -blockdev driver=raw,node-name=my,file=my_file -device ide-hd,drive=my,id=ide0-0-0,bus=ide.0,unit=0 -blockdev driver=file,cache.direct=off,cache.no-flush=on,filename=/home/kvm_autotest_root/iso/ISO/Win10/en_windows_10_business_editions_version_21h1_x86_dvd_1495793c.iso,node-name=my_cd,read-only=on -blockdev driver=raw,node-name=mycd,file=my_cd,read-only=on -device ide-cd,drive=mycd,id=ide0-1-0,bus=ide.1,unit=0 -blockdev driver=file,cache.direct=off,cache.no-flush=on,filename=204GPU103235RNZ.iso,node-name=my_iso,read-only=on -blockdev driver=raw,node-name=myiso,file=my_iso,read-only=on -device ide-cd,drive=myiso,id=ide0-1-1 -device usb-tablet,id=input0 -vnc 0.0.0.0:0 -M q35 -device pcie-root-port,bus=pcie.0,id=root1.0,multifunction=on,port=0x10,chassis=1,addr=0x7 -device pcie-root-port,bus=pcie.0,id=root2.0,port=0x11,chassis=2,addr=0x7.0x1 -netdev tap,script=/etc/qemu-ifup,downscript=no,id=hostnet0 -device e1000e,bus=root1.0,netdev=hostnet0,id=net0,mac=00:52:2e:72:7a:3e -device virtio-vga,id=video0,edid=off -device virtio-gpu-pci,id=gpu0,bus=root2.0 -global ICH9-LPC.disable_s3=1 -global ICH9-LPC.disable_s4=1
2. install virtio-win-prewhql-203/204.iso viogpudo driver
3. do some basic interactions with guest. 

Actual results:
Two cursors are really inconvenient.
Expected results:
Just one cursor in guest.

Additional info:
Comment 1 Vadim Rozenfeld 2021-07-20 03:59:46 UTC 
That's probably mean that you see a local cursor pointer rendered by viewer (usually black) and another one rendered by VM itself.
Do you see the seams problem on VM running locally ( no VNC session) ?

Vadim.
Comment 6 dehanmeng 2023-03-27 11:29:37 UTC 
Hi Vadim,
What you wanna set is DTM 15 right?  if so, please change it. thanks
Comment 7 RHEL Program Management 2023-05-01 07:28:14 UTC 
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.
Comment 9 RHEL Program Management 2023-08-15 11:23:48 UTC 
Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.
Comment 10 RHEL Program Management 2023-08-15 15:28:30 UTC 
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues.
Note You need to log in before you can comment on or make changes to this bug.