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:
Mouse could not used on win2k8 guest while via remote-viewer
Version-Release number of selected component (if applicable):
qemu-kvm-rhev-0.12.1.2-2.445.el6.x86_64
kernel-2.6.32-502.el6.x86_64
How reproducible:
3/3
Steps to Reproduce:
1.boot up guest with the following CLI
/usr/libexec/qemu-kvm -drive file=en_windows_server_2008_datacenter_enterprise_standard_sp2_x86_dvd_342333.iso,if=none,cache=unsafe,media=cdrom,format=raw,id=drive-ide0-0-0 -device ide-drive,id=ide0-0-0,drive=drive-ide0-0-0,bus=ide.0,unit=0,bootindex=1 -drive file=/usr/share/virtio-win/virtio-win-1.7.2.iso,if=none,cache=none,media=cdrom,format=raw,id=drive-ide0-0-2 -device ide-drive,id=ide0-0-2,drive=drive-ide0-0-2,bus=ide.1,unit=0 -drive file=/usr/share/virtio-win/virtio-win-1.7.2_x86.vfd,if=none,id=drive-fdc0-0-0,format=raw,cache=none -global isa-fdc.driveA=drive-fdc0-0-0 -drive file=win2k8-32.raw,if=none,cache=none,media=disk,format=raw,id=drive-ide0-0-1 -device virtio-blk-pci,id=ide1,drive=drive-ide0-0-1 -monitor stdio -vnc :3 -vga cirrus -usb -device usb-tablet,id=tablet1 -boot menu=on -chardev file,path=/root/console.log,id=serial1 -device isa-serial,chardev=serial1,id=s1 -cpu Penryn -smp 2 -m 2G -enable-kvm -device virtio-balloon-pci,id=balloon0 -device virtio-rng-pci,id=rng0 -drive file=test2832.raw,if=none,cache=none,media=disk,format=raw,id=drive-ide0-0-3 -device virtio-scsi-pci,id=scsi0 -device scsi-hd,bus=scsi0.0,drive=drive-ide0-0-3 -device virtio-serial-pci,id=virtio-serial0 -chardev socket,path=/tmp/tt2832,server,nowait,id=channel0 -device virtserialport,chardev=channel0,name=com.redhat.rhevm.vdsm,bus=virtio-serial0.0,id=port0 -netdev tap,id=hostnet0,script=/etc/qemu-ifup -device virtio-net-pci,netdev=hostnet0,id=net0,mac=54:34:4f:50:22:F1,bus=pci.0 -name win2k8-32-guest
2.user want to use mouse but it does not work,the cursor looks like frozen.
3.remove "-usb -device usb-tablet,id=tablet1",it could work.
Actual results:
The mouse could not be used by user.
Expected results:
The mouse could be used.
Additional info:
The same phenomenon could happen while use remote-viewer
Hmm, doesn't reproduce on a quick try. Different win2k8 build though (en_windows_server_2008_r2_with_sp1_x64_dvd_617601.iso), and also simply
booting the installer (/usr/libexec/qemu-kvm -vnc :9 -m 1G -cdrom $iso -usb -device usb-tablet), then wobbling the mouse, which works just fine.
qemu-kvm-0.12.1.2-2.446.el6.x86_64 here.
How do you test? Boot installer? Boot installed system? Is this a fresh install? Is this a regression?
(In reply to Gerd Hoffmann from comment #2)
> Hmm, doesn't reproduce on a quick try. Different win2k8 build though
> (en_windows_server_2008_r2_with_sp1_x64_dvd_617601.iso), and also simply
> booting the installer (/usr/libexec/qemu-kvm -vnc :9 -m 1G -cdrom $iso -usb
> -device usb-tablet), then wobbling the mouse, which works just fine.
>
> qemu-kvm-0.12.1.2-2.446.el6.x86_64 here.
>
> How do you test? Boot installer?
yes
Boot installed system?
No
Is this a fresh
yes
> install?
System install
Is this a regression?
I found it for the first time,so I could not say it was a regression.
Besides,I found you only add "-vnc :9" and can you add "-vnc :3 -vga cirrus" to your cli and have a try.Thanks
Thanks
Min
> I found it for the first time,so I could not say it was a regression.
> Besides,I found you only add "-vnc :9" and can you add "-vnc :3 -vga
> cirrus" to your cli and have a try.Thanks
That doesn't make a difference, cirrus is the default for '-vga'.
Can you try a newer win2k8 (R2) build in your setup?
This could be a guest bug, possibly newer win2k8 builds have it fixed.