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:

guest can't access guest agent after S3/S4

Version-Release number of selected component (if applicable):

libvirt-1.1.1-29.el7.x86_64
qemu-kvm-rhev-1.5.3-45.el7.x86_64
qemu-guest-agent-1.5.3-53.el7.x86_64

How reproducible:

100%

Steps to Reproduce:

1.Prepare a win 2003 guest with the virtio-serial and spice+qxl driver installed

2.install qemu-guest-agent on host and install qemu-ga on guest and keep it autostart

3.start guest, start qemu-ga service on guest

4.do S3/S4 on guest

#virsh dompmsuspend win2003 --target mem
Domain win2003 successfully woken up

#virsh dompmwakeup win2003
Domain win2003 successfully woken up

5.re-do step 4
#virsh dompmsuspend win2003 --target mem
error: Domain win2003 could not be suspended
error: Guest agent is not responding: Guest agent not available for now


Actual results:

as above

Expected results:

should can do S3/S4 in step 5

Additional info:

can't reproduce it on win7 guest.

Could you attach debug logs from libvirtd showing our communication with qemu?

(In reply to Jiri Denemark from comment #1)
> Could you attach debug logs from libvirtd showing our communication with
> qemu?

Hi Jiri,

Sorry for the mistake. After I update driver virtio-serial with the latest package virtio-win-prewhql-0.1-79 in guest, I can't reproduce this bug.

Created attachment 886770 [details]
libvirtd log

Hi Jiri,

The libvirtd log is attached. And I can reproduce it with virtio-win-1.7.0-1.el7, can't reproduce it with virtio-win-prewhql-0.1-79. So, this should be a virtio-win bug. Should we change the Component from libvirt to virtio-win?
 
Thanks

Yes.

Summary 

This issue is related to virtio-serial on winxp 
Reporter can reproduce this issue on virtio-win-1.7.0-1(virtio-win-prewhql-49),
Can not reproduce this issue on virtio-win-prewhql-79
We stopped respin drivers for winxp and win2k3 since RHEL6.5 so customer may hit this issue 

Ronen ,time to respin winxp&win2k3 vioserial driver to build 75 ?

Thanks,
Mike