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:
Version-Release number of selected component (if applicable):
# uname -r
2.6.32-252.el6.x86_64
[root@amd-2376-32-1 ~]# rpm -q qemu-kvm
qemu-kvm-0.12.1.2-2.248.el6rhev.x86_64
virtio-win-prewhql-24 guests
How reproducible:
100%
Steps to Reproduce:
1.start guest with virtio-serial-pci
CLI:/usr/libexec/qemu-kvm -M rhel6.3.0 -enable-kvm -m 8192 -smp 4,sockets=4,cores=1,threads=1 -name win2k8-R2 -uuid e2eaca3e-e764-f57b-22f0-74f4ab8c4965 -monitor stdio -rtc base=localtime,driftfix=slew -drive file=/test/win2k8r2,if=none,id=drive-ide0-0-0,format=raw,cache=none -device ide-drive,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0,bootindex=1 -drive file=/root/en_windows_server_2008_r2_standard_enterprise_datacenter_and_web_with_sp1_x64_dvd_617601.iso,if=none,media=cdrom,id=drive-ide0-1-0,readonly=on,format=raw -device ide-drive,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0 -netdev tap,script=/etc/qemu-ifup,downscript=no,id=hostnet0 -device rtl8139,netdev=hostnet0,id=net0,mac=52:54:00:15:af:6a,bus=pci.0,addr=0x3 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -spice port=5910,disable-ticketing -vga qxl -device intel-hda,id=sound0,bus=pci.0,addr=0x4 -device hda-duplex,id=sound0-codec0,bus=sound0.0,cad=0 -bios /bios-tttt.bin -device virtio-serial-pci,id=virtio-serial0,max_ports=16,bus=pci.0,addr=0x5 -chardev socket,id=charchannel0,path=/tmp/channel0,server,nowait -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,name=com.redhat.rhevm.vdsm -device virtio-serial-pci,id=virtio-serial1,max_ports=16 -chardev spicevmc,id=charchannel1,name=vdagent -device virtserialport,bus=virtio-serial1.0,nr=1,chardev=charchannel1,id=channel1,name=com.redhat.spice.0
2.in the guest disable VirtIO Serial Driver in device manager
3.in the guest #vioser-test.exe
4.press `r` in order to receive data in a loop
5.Try to click sth in the guest via mouse
Actual results:
after step4 every time press 'r' guest will receive a strange symbols amd sometimes the apps hang after "r" ,
After step 5 ,mouse is can not be used in the guest
Expected results:
every time press 'r' ,the app will show No
whenever the mouse should work in the guest
Additional info:
1.(qemu)info mice
* Mouse #0: QEMU PS/2 Mouse
2. after close the vioserial-test apps ,the mouse could use again.
Hi Mike,
vioser-test is a simple, probably even too simple application for a very
brief vioserial device driver testing. It was not designed to work simultaneously with other vioserial connected applications. It doesn't have
any serious error handling and error recovery mechanism inside.
I'm going to remove this application from virtio-win build and create
a new, more serious test application sometime in the future.
BTW, vioser-test gets strange symbols because at that moment qemu still has
some unread data.
Closing this bug, because I'm not going to fix it.
Best regards,
Vadim.