Bug 814896
Summary: | [virtio-win][serial] virtio-serial does not work after s4 in win7-32/64 bit guests | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Product: | Red Hat Enterprise Linux 6 | Reporter: | langfang <flang> | ||||||||
Component: | virtio-win | Assignee: | Yvugenfi <yvugenfi> | ||||||||
Status: | CLOSED ERRATA | QA Contact: | Virtualization Bugs <virt-bugs> | ||||||||
Severity: | medium | Docs Contact: | |||||||||
Priority: | medium | ||||||||||
Version: | 6.3 | CC: | acathrow, amit.shah, areis, bcao, bsarathy, dawu, dyasny, juzhang, michen, mkenneth, rhod, tburke, virt-maint, vrozenfe | ||||||||
Target Milestone: | rc | ||||||||||
Target Release: | --- | ||||||||||
Hardware: | Unspecified | ||||||||||
OS: | Unspecified | ||||||||||
Whiteboard: | |||||||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||||||
Doc Text: |
It was a bug in the vioserial in the power management routine, when virtio queue was not properly reinitialized during resume. As the result, a port was dis-functional and was not able to handle read and write requests properly.
The problem was fixed by adding proper virtual queue re-initialization on resume from hibernation.
|
Story Points: | --- | ||||||||
Clone Of: | Environment: | ||||||||||
Last Closed: | 2013-02-21 10:38:31 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: | |||||||||||
Bug Depends On: | |||||||||||
Bug Blocks: | 720669, 761491 | ||||||||||
Attachments: |
|
Description
langfang
2012-04-21 03:58:25 UTC
Created attachment 579147 [details]
script run on guest
Created attachment 579148 [details]
after resume S4,the error info about run guest script
Hi, langfang Could you reproduce this bug w/ vioser-test.exe (the tools is under the directory which you installed the virtio serial driver) Mike (In reply to comment #4) > Hi, langfang > > Could you reproduce this bug w/ vioser-test.exe (the tools is under the > directory which you installed the virtio serial driver) > > Mike i tried ,also have same problem,after guest S4,can not transfer data use virtio-serial driver. Too late for RHEL6.3. Postpone to 6.4. Anyhow an S4 bug In work, test again in 2-3 weeks. langfang , pls pls check whether this issue still occurs in virtio-win-prewhql30 (for 32 bit guest pls) use driver in \\install\Wxp\x86 , 64 bit guests use driver located in \\install\Wnet\amd64 ). (In reply to comment #12) > langfang , > > pls pls check whether this issue still occurs in virtio-win-prewhql30 > (for 32 bit guest pls) use driver in \\install\Wxp\x86 , 64 bit guests use > driver located in \\install\Wnet\amd64 ). hi!Mike i test this bug on the following version: host: # uname -r 2.6.32-284.el6.x86_64 # rpm -q qemu-kvm qemu-kvm-0.12.1.2-2.295.el6.x86_64 virtio-win:virtio-win-prewhql30 guest:win7-32/win7-64 results: also have the same problem. addinfo: the steps are the same as reproduce. Reproduce this bug on build virtio-win-prewhql-26, Verified this bug on build virtio-win-prewhql-41 with the same steps in comment0 CLI: /usr/libexec/qemu-kvm -cpu host -m 2G -smp 2 -boot dc -drive file=win7-32.qcow2,if=none,id=drive-ide0-0-0,werror=stop,rerror=stop,cache=none,format=qcow2,media=disk -device ide-drive,drive=drive-ide0-0-0,id=ide0-0-0 -drive file=en_windows_7_ultimate_with_sp1_x86_dvd_619077.iso,if=none,id=drive-ide0-0-1,werror=stop,rerror=stop,cache=none,format=raw,media=cdrom -device ide-drive,drive=drive-ide0-0-1,id=ide0-0-1 -netdev tap,id=hostnet0,script=/etc/qemu-ifup0 -device e1000,netdev=hostnet0,mac=00:22:5a:13:78:06,bus=pci.0,addr=0x4,id=net0 -uuid b2b6f616-0b80-4b41-af4e-985737e9ffbf -spice disable-ticketing,port=5931 -vga qxl -rtc base=localtime,clock=host,driftfix=slew -bios /usr/share/seabios/bios-pm.bin -monitor stdio -device virtio-serial-pci,id=virtio-serial0,max_ports=16,vectors=4,bus=pci.0 -chardev socket,server,host=0.0.0.0,port=12345,id=channel0,nowait -device virtserialport,chardev=channel0,nr=1,id=serialport.1,name=com.redhat.rhevm.vdsm,bus=virtio-serial0.0 Actually Results: On version virtio-win-prewhql-26, issue reproduced. On version virtio-win-prewhql-41, data can transfer successfully without any error after S4 additional info: this issue also been verified with vioser-test.exe, got the same results. Based on above, this issue has been fixed. Thanks for developer's efforts! Best Regards, Dawn Based on comment #16 ,move status to verified . Since this bug has been fixed already ,move product flag to rhel6.4.0 Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2013-0441.html |