Bug 861304

Summary: [virtio-win][serial]Failed to transfer data via the first serial port on win7
Product: Red Hat Enterprise Linux 6 Reporter: Min Deng <mdeng>
Component: virtio-winAssignee: Vadim Rozenfeld <vrozenfe>
Status: CLOSED NOTABUG QA Contact: Virtualization Bugs <virt-bugs>
Severity: medium Docs Contact:
Priority: medium    
Version: 6.4CC: acathrow, bcao, bsarathy, dyasny, juzhang, michen
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-09-28 09:33:48 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:

Description Min Deng 2012-09-28 05:45:49 UTC
Description of problem:
It cannot transfer data from guest to host or host to guest via the 1st port 

Version-Release number of selected component (if applicable):
kernel-2.6.32-308.el6.x86_64
qemu-kvm-0.12.1.2-2.313.el6.x86_64
virtio-win-prewhql-0.1-35
How reproducible:
4 times failed 4 times
Steps to Reproduce:
1.boot up guest with the CLI
  /usr/libexec/qemu-kvm -m 4G -smp 4 -usb -device usb-tablet,id=tablet0 -drive file=/home/win7-32-724-active.raw,if=none,id=drive-virtio0-0-0,format=raw,werror=stop,rerror=stop,cache=none -device ide-drive,drive=drive-virtio0-0-0,id=virti0-0-0,bootindex=1 -netdev tap,id=hostnet0,vhost=on,script=/etc/qemu-ifup -device rtl8139,netdev=hostnet0,id=net0,mac=00:12:10:94:a3:f8 -uuid 8677bf9b-3cf6-47a1-b3e9-94213b801c87 -monitor stdio -spice id=on,disable-ticketing,port=5912 -vga qxl -bios /usr/share/seabios/bios-pm.bin -device virtio-serial-pci,id=virtio-serial0,max_ports=16 -chardev socket,id=channel0,path=/tmp/helloworld,server,nowait -device virtserialport,chardev=channel0,name=com.redhat.rhevm.vdsm,bus=virtio-serial0.0,id=port0
2.in cmd,
  vioser-test.exe
  c:\>vioser-test.exe

Running in non-blocking mode.

Cannot find vioserial device. \\?\{6fde7547-1b65-48ae-b628-80be62016026}#vioseri

alport#4&33f42125&1&01#{6fde7521-1b65-48ae-b628-80be62016026} , error = 5

Actual results:
It can detect the vioserial device 

Expected results:
Cannot find vioserial device.

Additional info:
1.I check the driver's status from device manager and port from Devices and Printers.All look like well,it also fails while using scripts to transfer data.
2.*Sometimes*,It also can be reproduced while the guest with multiple vioserial ports.The data cannot be transferred via the 1st port but it works for 2nd.
eg:
/usr/libexec/qemu-kvm -m 4G -smp 4 -usb -device usb-tablet,id=tablet0 -drive file=/home/win7-32-724-active.raw,if=none,id=drive-virtio0-0-0,format=raw,werror=stop,rerror=stop,cache=none -device ide-drive,drive=drive-virtio0-0-0,id=virti0-0-0,bootindex=1 -netdev tap,id=hostnet0,vhost=on,script=/etc/qemu-ifup -device rtl8139,netdev=hostnet0,id=net0,mac=00:12:10:94:a3:f8 -uuid 8677bf9b-3cf6-47a1-b3e9-94213b801c87 -chardev socket,id=111a,path=/tmp/tt,server,nowait -mon chardev=111a,mode=readline -spice id=on,disable-ticketing,port=5912 -vga qxl -bios /usr/share/seabios/bios-pm.bin -device virtio-serial-pci,id=virtio-serial0,max_ports=16 -chardev socket,id=channel0,path=/tmp/helloworld0,server,nowait -chardev socket,id=channel1,path=/tmp/helloworld1,server,nowait -device virtserialport,chardev=channel0,name=com.redhat.rhevm.vdsm1,bus=virtio-serial0.0,id=port0 -device virtserialport,chardev=channel1,name=com.redhat.rhevm.vdsm2,bus=virtio-serial0.0,id=port2 -bios /usr/share/seabios/bios-pm.bin -monitor stdio

Comment 1 Vadim Rozenfeld 2012-09-28 06:05:28 UTC
Did you open cmd with elevated (administrator) rights?
Also, please make sure that the port was not open by any other application (like vdsm agent for example).
Best regards,
Vadim.

Comment 2 Min Deng 2012-09-28 09:10:41 UTC
(In reply to comment #1)
> Did you open cmd with elevated (administrator) rights?
> Also, please make sure that the port was not open by any other application
> (like vdsm agent for example).
> Best regards,
> Vadim.

  It can be reproduced on virtio-win-1.5.4.Yes,use the administrator.

Comment 3 Min Deng 2012-09-28 09:33:48 UTC
(In reply to comment #1)
> Did you open cmd with elevated (administrator) rights?
> Also, please make sure that the port was not open by any other application
> (like vdsm agent for example).
> Best regards,
> Vadim.
  
  Hi Vadim,
     Sorry for noise,it works fine after stopping RHEV Agent.So close the bug.

  Thanks,
  Min