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.

Bug 882117

Summary: Guest doesn't let host know of open virtio console ports after resume from S3/S4
Product: Red Hat Enterprise Linux 6 Reporter: Qunfang Zhang <qzhang>
Component: virtio-winAssignee: Vadim Rozenfeld <vrozenfe>
Status: CLOSED DUPLICATE QA Contact: Virtualization Bugs <virt-bugs>
Severity: high Docs Contact:
Priority: medium    
Version: 6.4CC: acathrow, bcao, bsarathy, dyasny, flang, juzhang, michen, vrozenfe, yunzheng
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-12-06 05:20:23 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:
Attachments:
Description Flags
script for both host and guest sides none

Description Qunfang Zhang 2012-11-30 07:24:49 UTC 
Description of problem:
Boot a win7-32 guest with virtio serial bus and port, transfer data between guest and host succeed. And then do S3 or S4,but after resume, virtio serial port doesn't work any more, can not transfer data between host and guest. If I reboot guest, the virtio serial works again.

Version-Release number of selected component (if applicable):
virtio-win-prewhql-46
kernel-2.6.32-344.el6.x86_64
qemu-kvm-0.12.1.2-2.337.el6.x86_64

How reproducible:
Always

Steps to Reproduce:
1. Boot a /usr/libexec/qemu-kvm -boot menu=on -m 2G -smp 2,cores=2,sockets=1,threads=1 -M rhel6.4.0 -cpu SandyBridge -drive file=/mnt/win7-32-virtio.raw,format=raw,if=none,id=drive-ide0,cache=none,werror=stop,rerror=stop -device virtio-blk-pci,bus=pci.0,addr=0x3,drive=drive-ide0,id=test0 -netdev tap,id=hostnet1,script=/etc/qemu-ifup,downscript=no -device e1000,netdev=hostnet1,mac=00:12:1a:21:62:02,bus=pci.0,addr=0x4,id=virtio-net-pci1 -uuid ac64c74a-a8d5-4c24-9839-fcc491439493 -rtc base=localtime,clock=host,driftfix=slew -no-kvm-pit-reinjection -name win7-32 -device virtio-serial-pci,id=virtio-serial0,max_ports=16,bus=pci.0,addr=0x5  -chardev socket,id=channel0,path=/tmp/qzhang-1,server,nowait -device virtserialport,bus=virtio-serial0.0,nr=5,chardev=channel0,id=port-1,name=port-1   -chardev socket,path=/tmp/foo,server,nowait,id=foo -device virtconsole,chardev=foo,id=console0 -chardev spicevmc,id=charchannel1,name=vdagent -device virtserialport,bus=virtio-serial0.0,nr=3,chardev=charchannel1,id=channel1,name=com.redhat.spice.0 -boot c -drive if=none,werror=stop,rerror=stop,media=cdrom,id=drive-cdrom -device ide-drive,drive=drive-cdrom,id=cdrom -spice port=5930,disable-ticketing,seamless-migration=on -vga qxl -usb -device usb-tablet -monitor stdio -drive file=/usr/share/virtio-win/virtio-win-1.5.4.vfd,if=none,id=drive-fdc0-0-0,readonly=on,format=raw -global isa-fdc.driveA=drive-fdc0-0-0 -qmp tcp:0:5555,server,nowait -global PIIX4_PM.disable_s3=0 -global PIIX4_PM.disable_s4=0
guest with virtio serial


2. Transfer data from host to guest with some python scripts. (Will be attached.)
(1) On host:  # python serial-host-send.py /tmp/qzhang-1 
(2) On guest # python VirtIoChannel_guest_receive.py port-1

3. Suspend guest to memory or disk.
(Don't suspend guest *during* data transfer because there's existing bug 858145.

4. Resume guest

5. Repeat step 2.

6. Reboot guest.

7. Repeat step 2.
  
Actual results:
After step 5, virtio serial doesn't work.
After step 7, virtio serial works again.

Expected results:
Guest virtio serial should always work after s3/s4.

Additional info:
RHEL guest has no problem after fix bug 816099.
Comment 1 Mike Cao 2012-11-30 07:26:50 UTC 
Could you try w/ lastest virtio-win build 49 ?
Comment 2 Qunfang Zhang 2012-11-30 07:27:08 UTC 
Created attachment 654851 [details]
script for both host and guest sides
Comment 4 Qunfang Zhang 2012-11-30 07:35:34 UTC 
(In reply to comment #1)
> Could you try w/ lastest virtio-win build 49 ?

Issue exists in virtio-win-prewhql-49 as well.
Comment 5 Qunfang Zhang 2012-12-05 08:13:21 UTC 
Update:
I re-test again just now with a fresh install win7-32 guest and install virtio-win-prewhql-49, can not reproduce now with the steps in comment 0.
Comment 6 Mike Cao 2012-12-06 05:20:23 UTC 
I can not reproduce this issue on build 49 as well
Can reproduce this issue on build 43

Close dup of Bug 873971

*** This bug has been marked as a duplicate of bug 873971 ***