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:

After a guest is resumed from s3 or s4, an open port in the guest stops receiving data from host.

For example:

(host) nc -U /tmp/foo
(guest) cat /dev/vport0p1
(host) send some data; they will appear in guest terminal

<enter s4 state>

(host) send some data, they will not appear in guest terminal

Expected case is for data to start appearing in guest terminal after restore.

This behaviour will be exhibited only after bug 787974 is fixed.  That is because qemu wrongly marked all guest-side connections open before that bug was fixed.  With that bug fixed, this is exposed.

This request was evaluated by Red Hat Product Management for inclusion
in a Red Hat Enterprise Linux maintenance release. Product Management has 
requested further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed 
products. This request is not yet committed for inclusion in an Update release.

Patch(es) available on kernel-2.6.32-269.el6

I have reproduced this issue on kernel-2.6.32-268.el6, qemu-kvm-292.

Reproduction:
-------------
Steps: Exactly the same as in Description. Both S3 and S4 have this issue on vport0p1 and vport0p2. After resume, guest cannot receive data sent by host.

Verification:
-------------
Verified on kernel-2.6.32-270.el6, qemu-kvm-292. After resume from S3 and S4, guest can receive data sent by host.

Conclusion:
----------
As per above, this issue has been fixed correctly.

According to comment6,set this issue as verified.

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/RHSA-2012-0862.html