Bug 966908
Summary: | [virtio-win][serial]The original terminal can not receive data after S4 | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | guo jiang <jguo> |
Component: | virtio-win | Assignee: | Gal Hammer <ghammer> |
Status: | CLOSED WORKSFORME | QA Contact: | Virtualization Bugs <virt-bugs> |
Severity: | medium | Docs Contact: | |
Priority: | unspecified | ||
Version: | 7.0 | CC: | acathrow, bcao, bsarathy, jguo, kzhang, lijin, michen, qzhang, rhod, virt-maint |
Target Milestone: | rc | Keywords: | Reopened |
Target Release: | 7.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2014-03-13 14:46:50 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
guo jiang
2013-05-24 09:02:53 UTC
Today, I try five times, only 4 times have be reproduced. I'm unable to reproduce with build 64. Can you please confirm? Thanks. BTW: You might see an error message which say "The systen cannot message text for message number 0x13d in the message file for System.". It is probably caused by an error code returned by the driver which doesn't have an error string in Windows XP. It probably won't be fixed and is not considered as an error. Hi,Gal I only encountered in winxp, resuming after s4, the guest's original terminal stop there and no error report. After killing it and restart another script, could receive data again. Thanks, Guo Jiang (In reply to guo jiang from comment #4) > Hi,Gal > > I only encountered in winxp, resuming after s4, the guest's original > terminal stop there and no error report. After killing it and restart > another script, could receive data again. This didn't answer my question. I was unable to reproduce it on Windows XP with build 64. Can you please confirm? Thanks, Gal. > Thanks, > Guo Jiang Can you please reply to my previous comment #5? And another question. Were you able to reproduce it with other version of Windows, or is it just a Windows XP issue? Hi, Gal QE could only reproduce it on windows-XP guest. Win7, Win8 and Win2012 don't hit this issue. Thanks, Jiang. Closing as Windows XP support for S3/S4 is at low priority. reopen this bug as win2012R2 hit the same issue. package info: qemu-kvm-rhev-0.12.1.2-2.415.el6_5.3.x86_64 kernel-2.6.32-433.el6.x86_64 seabios-0.6.1.2-28.el6.x86_64 virtio-win-prewhql-74 steps to reproduce: 1./usr/libexec/qemu-kvm -drive file=win2k12R2.qcow2,if=none,cache=none,media=disk,format=qcow2,id=drive-ide0-0-1 -device ide-drive,id=ide0-0-1,drive=drive-ide0-0-1,bootindex=0 -usb -device usb-tablet -spice disable-ticketing,port=5901 -vga qxl -global qxl-vga.revision=3 -global PIIX4_PM.disable_s3=0 -global PIIX4_PM.disable_s4=0 -netdev tap,id=hostnet0 -device e1000,netdev=hostnet0,id=net0,mac=52:54:00:7f:f9:F6,bus=pci.0 -chardev file,path=/root/console.log,id=serial1 -device isa-serial,chardev=serial1,id=s1 -cpu Penryn -M rhel6.5.0 -monitor stdio -name win2012R2-balloon-74 -smp 4,maxcpus=4,cores=2,threads=2,sockets=1 -m 4G -enable-kvm -cdrom /usr/share/rhev-guest-tools-iso/rhev-tools-setup.iso -device virtio-serial-pci,id=virtio-serial0,max_ports=16 -chardev socket,path=/tmp/tt0,server,nowait,id=chardev0 -device virtserialport,chardev=chardev0,name=com.redhat.rhevm.vdsm,bus=virtio-serial0.0,id=port0 -chardev socket,path=/tmp/tt1,server,nowait,id=chardev1 -device virtserialport,chardev=chardev1,name=com.redhat.rhevm.vdsm1,bus=virtio-serial0.0,id=port1 2.Transfering data from host to guest via port1 in a loop eg:in the guest # for ((;;)) ;do python VirtIOChannel_guest_reieve.py com.redhat.rhevm.vdsm; done on the host # for ((;;)) ;do python serial-host-send.py /tmp/tt0 ; done 3.hibernate Guest 4.resume the guest w/ the same commandline in step1 After step4,the original cmd terminal in guest froze,and cannot receive any data from,ctrl+C also deosn't work; After close the original terminal,then reopen a new one and run the script,serialport works nornally. Excepted result: the original terminal should keep receiving data without reopen a new cmd. This request was not resolved in time for the current release. Red Hat invites you to ask your support representative to propose this request, if still desired, for consideration in the next release of Red Hat Enterprise Linux. (In reply to lijin from comment #9) > reopen this bug as win2012R2 hit the same issue. > > package info: > qemu-kvm-rhev-0.12.1.2-2.415.el6_5.3.x86_64 > kernel-2.6.32-433.el6.x86_64 > seabios-0.6.1.2-28.el6.x86_64 > virtio-win-prewhql-74 I was unable to reproduce it. > steps to reproduce: > 1./usr/libexec/qemu-kvm -drive > file=win2k12R2.qcow2,if=none,cache=none,media=disk,format=qcow2,id=drive- > ide0-0-1 -device ide-drive,id=ide0-0-1,drive=drive-ide0-0-1,bootindex=0 -usb > -device usb-tablet -spice disable-ticketing,port=5901 -vga qxl -global > qxl-vga.revision=3 -global PIIX4_PM.disable_s3=0 -global > PIIX4_PM.disable_s4=0 -netdev tap,id=hostnet0 -device > e1000,netdev=hostnet0,id=net0,mac=52:54:00:7f:f9:F6,bus=pci.0 -chardev > file,path=/root/console.log,id=serial1 -device > isa-serial,chardev=serial1,id=s1 -cpu Penryn -M rhel6.5.0 -monitor stdio > -name win2012R2-balloon-74 -smp 4,maxcpus=4,cores=2,threads=2,sockets=1 -m > 4G -enable-kvm -cdrom /usr/share/rhev-guest-tools-iso/rhev-tools-setup.iso > -device virtio-serial-pci,id=virtio-serial0,max_ports=16 -chardev > socket,path=/tmp/tt0,server,nowait,id=chardev0 -device > virtserialport,chardev=chardev0,name=com.redhat.rhevm.vdsm,bus=virtio- > serial0.0,id=port0 -chardev socket,path=/tmp/tt1,server,nowait,id=chardev1 > -device > virtserialport,chardev=chardev1,name=com.redhat.rhevm.vdsm1,bus=virtio- > serial0.0,id=port1 > 2.Transfering data from host to guest via port1 in a loop > eg:in the guest # for ((;;)) ;do python VirtIOChannel_guest_reieve.py > com.redhat.rhevm.vdsm; done > on the host # for ((;;)) ;do python serial-host-send.py /tmp/tt0 ; done > 3.hibernate Guest How did you put the guest into hibernate? Did you install QXL driver? > 4.resume the guest w/ the same commandline in step1 > > After step4,the original cmd terminal in guest froze,and cannot receive any > data from,ctrl+C also deosn't work; > After close the original terminal,then reopen a new one and run the > script,serialport works nornally. > > Excepted result: > the original terminal should keep receiving data without reopen a new cmd. (In reply to Gal Hammer from comment #11) > (In reply to lijin from comment #9) > > reopen this bug as win2012R2 hit the same issue. > > > > package info: > > qemu-kvm-rhev-0.12.1.2-2.415.el6_5.3.x86_64 > > kernel-2.6.32-433.el6.x86_64 > > seabios-0.6.1.2-28.el6.x86_64 > > virtio-win-prewhql-74 > > I was unable to reproduce it. > > > steps to reproduce: > > 1./usr/libexec/qemu-kvm -drive > > file=win2k12R2.qcow2,if=none,cache=none,media=disk,format=qcow2,id=drive- > > ide0-0-1 -device ide-drive,id=ide0-0-1,drive=drive-ide0-0-1,bootindex=0 -usb > > -device usb-tablet -spice disable-ticketing,port=5901 -vga qxl -global > > qxl-vga.revision=3 -global PIIX4_PM.disable_s3=0 -global > > PIIX4_PM.disable_s4=0 -netdev tap,id=hostnet0 -device > > e1000,netdev=hostnet0,id=net0,mac=52:54:00:7f:f9:F6,bus=pci.0 -chardev > > file,path=/root/console.log,id=serial1 -device > > isa-serial,chardev=serial1,id=s1 -cpu Penryn -M rhel6.5.0 -monitor stdio > > -name win2012R2-balloon-74 -smp 4,maxcpus=4,cores=2,threads=2,sockets=1 -m > > 4G -enable-kvm -cdrom /usr/share/rhev-guest-tools-iso/rhev-tools-setup.iso > > -device virtio-serial-pci,id=virtio-serial0,max_ports=16 -chardev > > socket,path=/tmp/tt0,server,nowait,id=chardev0 -device > > virtserialport,chardev=chardev0,name=com.redhat.rhevm.vdsm,bus=virtio- > > serial0.0,id=port0 -chardev socket,path=/tmp/tt1,server,nowait,id=chardev1 > > -device > > virtserialport,chardev=chardev1,name=com.redhat.rhevm.vdsm1,bus=virtio- > > serial0.0,id=port1 > > 2.Transfering data from host to guest via port1 in a loop > > eg:in the guest # for ((;;)) ;do python VirtIOChannel_guest_reieve.py > > com.redhat.rhevm.vdsm; done > > on the host # for ((;;)) ;do python serial-host-send.py /tmp/tt0 ; done > > 3.hibernate Guest > > How did you put the guest into hibernate? Did you install QXL driver? > > > 4.resume the guest w/ the same commandline in step1 > > > > After step4,the original cmd terminal in guest froze,and cannot receive any > > data from,ctrl+C also deosn't work; > > After close the original terminal,then reopen a new one and run the > > script,serialport works nornally. > > > > Excepted result: > > the original terminal should keep receiving data without reopen a new cmd. Yes,I installed the qxl driver. Actually I found this issue also happened on other OS,at least I tried win2k8-64,win2012,win7-32.Most occur after resume from s4,sometimes after resume from s3. It's easy to reproduce it for me,the terminal is not totally froze,I can scroll the cmd terminal in guest,but the receive script didn't work,it kept still,and cannot use ctrl+c to stop the script.Close the terminal and rerun the script,it works again. I can reproduce this issue as well on win8-64 with VNC steps same as comment #9 ,the terminal I use is cygwin (In reply to Mike Cao from comment #13) > I can reproduce this issue as well on win8-64 with VNC steps same as comment > #9 ,the terminal I use is cygwin win7-32 w/spice works for me. Are you using qemu-kvm-0.12.1.2-2.415.el6.x86_64 or qemu-kvm-rhev-0.12.1.2-2.415.el6_5.3.x86_64? (In reply to Gal Hammer from comment #14) > (In reply to Mike Cao from comment #13) > > I can reproduce this issue as well on win8-64 with VNC steps same as comment > > #9 ,the terminal I use is cygwin > > win7-32 w/spice works for me. > > Are you using qemu-kvm-0.12.1.2-2.415.el6.x86_64 or > qemu-kvm-rhev-0.12.1.2-2.415.el6_5.3.x86_64? Sorry ,I am using RHEL7 host with 3.10.0-50.el7.x86_64 qemu-kvm-rhev-1.5.3-19.el7.x86_64 (In reply to Mike Cao from comment #15) > (In reply to Gal Hammer from comment #14) > > (In reply to Mike Cao from comment #13) > > > I can reproduce this issue as well on win8-64 with VNC steps same as comment > > > #9 ,the terminal I use is cygwin > > > > win7-32 w/spice works for me. > > > > Are you using qemu-kvm-0.12.1.2-2.415.el6.x86_64 or > > qemu-kvm-rhev-0.12.1.2-2.415.el6_5.3.x86_64? > > Sorry ,I am using RHEL7 host with 3.10.0-50.el7.x86_64 > qemu-kvm-rhev-1.5.3-19.el7.x86_64 I was unable to reproduce on a RHEL-7 host (kernel-3.10.0-64.el7.x86_64) with qemu-kvm-1.5.3-30.el7.x86_64 and a Windows 7 32-bit guest (virtio-win build 74). Can you please update your qemu-kvm package and test again? lijin, pls retest it on latest virtio-win /qemu-kvm/seabios according to commen t#9 ? (In reply to Mike Cao from comment #18) > lijin, pls retest it on latest virtio-win /qemu-kvm/seabios according to > commen t#9 ? win7-32 guest still hit this issue with the latest package. package info: qemu-kvm-rhev-1.5.3-50.el7.x86_64 kernel-3.10.0-98.el7.x86_64 seabios-1.7.2.2-11.el7.x86_64 virtio-win-1.6.8-4.el6.noarch 1.boot guest with qemu command: /usr/libexec/qemu-kvm \ -M pc -m 2G -smp 2,cores=2 \ -drive file=big.qcow2,format=qcow2,media=disk,if=none,cache=none,id=drive-scsi,serial=scsi1 \ -device ide-drive,drive=drive-scsi,id=ide-scsi-pci1,bootindex=1 \ -rtc base=localtime,clock=host,driftfix=slew -no-kvm-pit-reinjection \ -name win7-32 \ -global PIIX4_PM.disable_s3=0 -global PIIX4_PM.disable_s4=0 \ -usb -device usb-tablet \ -monitor stdio \ -spice disable-ticketing,port=5902 -vga qxl -global qxl-vga.revision=3 \ -netdev tap,id=hostnet1,script=/etc/qemu-ifup,downscript=no -device e1000,netdev=hostnet1,id=net1,mac=00:52:22:16:54:48,bus=pci.0 \ -cdrom /usr/share/virtio-win/virtio-win.iso \ -fda /usr/share/virtio-win/virtio-win_x86.vfd \ -device virtio-serial-pci,id=virtio-serial0,max_ports=16 -chardev socket,path=/tmp/tt0,server,nowait,id=chardev0 -device virtserialport,chardev=chardev0,name=com.redhat.rhevm.vdsm,bus=virtio-serial0.0,id=port0,nr=1 -chardev socket,path=/tmp/tt1,server,nowait,id=chardev1 -device virtserialport,chardev=chardev1,name=com.redhat.rhevm.vdsm1,bus=virtio-serial0.0,id=port1 2.Transfering data from host to guest via port1 in a loop on the guest # for /l %i in (1.1.1000) do python VirtIOChannel_guest_reieve.py com.redhat.rhevm.vdsm on the host # for ((j=1;j<=1000;j++)); do python serial-host-send.py /tmp/tt0; sleep 1; done; 3.hibernate Guest 4.resume the guest w/ the same commandline in step1 actual result: guest stop receiving data,the script running in cmd window hang,"ctrl+c" does not work. close this cmd window and open a new one,then run the receive script,guest can receive data again. excepted result: guest can receive data without closing the original cmd window. Closing after failing to reproduce w/qemu-kvm-1.5.3-52.el7.x86_64 on a RHEL-7 host. |